Blue Screen (BSOD) when running 3DMark Vantage
-
Wednesday, June 15, 2011 5:05 PM
I have fresh Windows 7 64bit installation on my laptop with Intel i7 2630QM (Intel HD Graphics 3000) and nVidia GeForce 525M. First I had the following HD Graphics driver Intel HD Graphics 3000, v.15.21.13.64.2342 , A02 and latest GeForce driver nVidia GeForce GT 525M v.8.17.12.6683, A01.
When I tested system performance with 3DMark Vantage it said that system performance is too low considering the specs, this seemed strange because in nVidia Control Panel I specified to use the discrete graphics card. Then I updated to latest HD Graphics driver Intel HD Graphics 3000, v.8.15.10.2361, A03 and also installed 3DMark 11 for DirectX 11. When I ran 3DMark 11 I got BSOD and after the restart I tried 3DMark Vantage and also got BSOD.
Then I tried many things... system restore and uninstalling and reinstalling Intel HD Graphics drivers but I had this problem even with previous A02 HD Graphics drivers which worked initially.
Here's the minidump and full memory dump of the crash when A02 HD Graphics driver was used:
Can you help me to understand what is causing the blue screen?
Below is what I got from minidump using WinDbg. As far I understand it's a driver problem.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Valdis\Desktop\bsod\061411-21668-01 - old driver.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`03068000 PsLoadedModuleList = 0xfffff800`032ad650
Debug session time: Tue Jun 14 22:22:01.295 2011 (UTC + 3:00)
System Uptime: 0 days 0:02:20.356
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa80062cbb30, fffffa80062cbe10, fffff800033eaf40}
Probably caused by : csrss.exe
Followup: MachineOwner
---------
0: kd> !analuze -v
No export analuze found
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa80062cbb30, Terminating object
Arg3: fffffa80062cbe10, Process image file name
Arg4: fffff800033eaf40, Explanatory message (ascii)
Debugging Details:
------------------
PROCESS_OBJECT: fffffa80062cbb30
IMAGE_NAME: csrss.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: csrss
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: csrss.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000374 - A heap has been corrupted.
BUGCHECK_STR: 0xF4_C0000374
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`03dfa9c8 fffff800`0346f7d2 : 00000000`000000f4 00000000`00000003 fffffa80`062cbb30 fffffa80`062cbe10 : nt!KeBugCheckEx
fffff880`03dfa9d0 fffff800`0341dbdb : ffffffff`ffffffff fffffa80`06f1bb60 fffffa80`062cbb30 fffffa80`062cbb30 : nt!PspCatchCriticalBreak+0x92
fffff880`03dfaa10 fffff800`033a0838 : ffffffff`ffffffff 00000000`00000001 fffffa80`062cbb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x179e6
fffff880`03dfaa60 fffff800`030e6f93 : fffffa80`062cbb30 fffff880`c0000374 fffffa80`06f1bb60 fffffa80`039fd230 : nt!NtTerminateProcess+0xf4
fffff880`03dfaae0 00000000`76ec15da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00c8e358 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ec15da
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0xF4_C0000374_IMAGE_csrss.exe
BUCKET_ID: X64_0xF4_C0000374_IMAGE_csrss.exe
Followup: MachineOwner
All Replies
-
Wednesday, June 15, 2011 7:56 PM
Bug Check Code 0xF4: http://msdn.microsoft.com/en-us/library/ff560372(VS.85).aspx
It will be better to upload the dump file using Microsoft Skydrive. Once done post a link here.
Start updating all possible drivers.
You can also contact Microsoft CSS.
This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.Microsoft Student Partner 2010 / 2011
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows 7, Configuring
Microsoft Certified IT Professional: Enterprise Administrator -
Friday, June 17, 2011 11:57 AM
What's the difference where I upload the dump file? SkyDrive has 50 MB limit and I didn't want to bother with splitting the archive in two.
Minidump:
http://cid-a017635c84146074.office.live.com/self.aspx/BSOD/061411-21668-01%20-%20old%20driver.dmp
Full dump:
http://cid-a017635c84146074.office.live.com/self.aspx/BSOD/MEMORY2%20-%20old%20driver.zip.001
http://cid-a017635c84146074.office.live.com/self.aspx/BSOD/MEMORY2%20-%20old%20driver.zip.002
By the way it is a Dell Inspiron N5110 laptop, when I bought it it had no OS. I have tried the latest drivers. 8.15.10.2361 is the latest version of Intel HD Graphics driver and is published in the Dell driver downloads. nVidia GeForce GT 525M v.8.17.12.6683, A01 mentioned above and downloadable from Dell support is a driver with nVidia driver number 266.84. I also tried downloading the latest version 273.54 directly from nVidia. By the way Dell is not modifying nVidia drivers, don't know about Intel drivers, but the latest one at least is provided by Dell.
Update:
By the way I found out that both 3DMark Vantage and 3DMark 11 work when I log into administrator account. When I run them simply as an administrator while logged in normal user account they crash. Probably that's a bug in the 3DMark software, but I cannot find anybody else having the same problem.
-
Monday, January 21, 2013 7:58 PMDid you run 3DMark as admin? 3DMark seems to has a bug, that it works only when launched with admin previliges? I just spend entire evening with 3DMark first scan crashing and ending up with BSODs, before I realized that the program must be launched in Admin session.
-
Monday, January 21, 2013 8:16 PM
Did you read the last 2 lines of the previous post?
I had topics about this in techsupportforum and futermark forum. Didn't eventually figure the reason for this.
Some software could be conflicting with 3DMark and causing the crash, for example Avast antivirus causes crashes. You can find the list of conflicting software somewhere on futuremark's site.

