Thanks, I'll let you know if this version works for me.
/update:
Sorry, the BSOD still appears...
STOP: c000021a {Fatal System Error}
The Windows SubSystem system process terminated unexpectedly with a status of 0xc0000005 (0x76f832d0 0x0270de70).
The system has been shut down.
That's what it says since version 4.0.
Last edited by mischa1981; 07-26-2011 at 04:59 AM.
I looked up a bit on Google about that specific bluescreen error and reportedly it is mostly caused by bad RAM modules. Are you absolutely certain your RAM is good?
Alternatively....
This occurs when Windows switches into kernel mode and a user-mode subsystem, such as Winlogon or the Client Server Runtime Subsystem (CSRSS), is compromised. Security can no longer be guaranteed. Because Windows can’t run without Winlogon or CSRSS, this is one of the few situations where the failure of a user-mode service can cause the system to stop responding. This Stop message also can occur as a result of malware infestation or when the computer is restarted after a system administrator has modified permissions so that the SYSTEM account no longer has adequate permissions to access system files and folders.
Well, I also checked the problem about the RAM. I have 4 modules of 2 GB installed. I ran tests with memtest86+ with each time only one module installed, no error occured but SystemInfo still causes an BSOD.
I also read about the kernel mode, but I have no idea what to do about it.
Well, in short it is a suspicion that your windows installation is somehow corrupt and doesn't have all the required permissions properly set.Originally Posted by mischa1981
I've forwarded this to the programmer but it'll be next week before he can take a look.
OK, so I guess I should give Windows reinstall a try? I also thought so.
But thank you so far :)
Ugh, I typed a really long response to this thread, and then I think I hit preview, and closed the window without posting. So here it goes again.
I have EXACTLY the same problem as the OP.
I'm assuming it has to do with system info as it is shared between the different versions of 3DMark. For me the problem affects:
3DMark11 (purchased advanced license): Menu loads, BSOD's upon clicking "start benchmark"
3DMark Vantage (free license): Menu loads, BSOD's upon clicking "start benchmark"
3DMark06 (Free License): BSOD's before menu pops up.
All other programs are 100% stable on the machine, including memtest86+, 24+ hours of Prime95, several hours of Intel Burn Test and many intensive 3D applications and games.
Just to make sure that it wasn't the fault of overclocking, I downclocked everything to stock settings, and the BSOD's still occur.
All three applications worked just fine, until I ran the 1.0.2 patch to upgrade 3DMark11. Ever since all three bluescreen. I have tried uninstalling and reinstalling all three benchmarks without avail.
System specs are as follows:
AMD Phenom II X6 1090T BE
MSI 990FXA-GD80
16GB Corsair Dominator GT DDR3-2000
120GB OCZ Agility SSD
Sound Blaster X-Fi Titanium HD
2x Asus EAH6970 DirectCU II's in Crossfire
See the full DxDiag here.
Upgrading to the beta version of system info in this thread did not help.
I'd appreciate any help I can get. As it stands I paid for the advanced version of 3DMark11 and I can't use it :(
and I should apologize. I didn't realize there was a post hold on new members, so I accidentally created a separate thread for this issue in addition to posting here while trying to figure out why my posts weren't showing up. :p
My thread is here. Maybe this should be merged somehow as it covers the same issue?
Well, I got a new system now:
Asus P8Z68-V Pro
4GB DDR3 1333
Intel Core i5 2500K
and installed Windows 7 64bit with all patches and updates and also installed SystemInfo 4.1 and now it works just fine for me :)
So I can only say that there maybe was an error in the old system.
We have 4.2 available through Game-o-Meter now so I suggest running GoM once to update to the latest one. All FM benchmarks support it.
Assuming no new issues turn up, we expect to roll it out to all benchmark users through update notification in the coming weeks.
Hi, I know this thread is a bit old, but I just wanted to see if my new hardware still worked.
So I installed 3DMark11 again, updated to version 1.03 and also SystemInfo to 4.6.
Guess what? It's happening again, stop c000021a...
My new hardware:
Intel corei5 2500k (not overclocked)
12GB RAM 1333MHz
GTX570 Phantom (not overclocked)
Windows 7 64bit (Ultimate)
Posting Permissions
Reply With Quote
