Windows 7: BSOD running graphic intensive applications

hammerstrong · 24 May 2011

Hello,

my pc specs are:
windows 7 professional x64
ASUS M4A890GTD PRO/USB3 mobo
AMD 1090T @ stock clock
2x2GB GSkill ddr3 @ 1600Mhz 1.6V
nVidia GTX 460 @ (heavily overclocked in that past, currently at stock)
2x SATA IDE HDDs
Corsair 850TX 850W PSU

For the last couple of weeks I have been having BSODs when running 3d graphics intensive apps. The crash occurs most when running dx10-11 apps and almost never when running OpenGL apps (like furmark).

I have tried multiple troubleshooting solutions generally used in this scenario.
reset mobo to stock voltages (CPU was moderately overclocked earlier).
went all the way from 100 level forceware graphics drivers to the 275 beta drivers.
ran memtest86+ (stable) and prime95 (stable) for a few hours.
ran furmark for about 30 mins (stable).
reinstalled windows.
reseated RAM, tried the other channel.
updated every driver i could

The problem started after Dragon Age 2 spazzed out on me a couple of weeks ago. running the game in dx9 mode fixed the issue.
Then i started playing Assassin's Creed Brotherhood which ran smoothly for a while, then started BSODing frequently (now i can play for maybe 3 minutes before a crash). I was still able to play Call of Duty Black Ops without crashes, but after some of the latest crashes (after running Unigine heaven bench), even that seems to cause a crash.

I think I have done enough to isolate the problem to either mobo or gfx card. It would be very nice if i could get an expert opinion on the matter before starting any RMA.

mgorman87 · 24 May 2011

Code:

ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)

A known BSOD maker in Windows 7. The 2005 version of this driver is known to cause BSOD on Windows 7 systems.
Download the ATK0110 utility from here - ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE.
After you install it browse to C:\windows\system32\drivers and check the properties of ASACPI.sys and make sure it now says 2009.

There were more USB bugchecks then video card errors. What type of USB devices do you have hooked up to the computer?

I see the driver RTCore64.sys in your unloaded drivers. Do you have RivaTuner/EVGA Precision/MSI Afterburner (known issues w/Windows 7) installed? If you do, uninstall it.

Please run these tests and report back the results
1. Memtest86 - Run for 7-8 passes - RAM - Test with Memtest86+
2. Prime95 - Run all three tests (Small FFTs, Large FFTs, Blend) for 3-4 hours each or until fail - http://www.sevenforums.com/tutorials...t-prime95.html
3. Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue May 24 10:44:55.355 2011 (UTC - 4:00)
System Uptime: 0 days 0:10:15.259
Probably caused by : ntkrnlmp.exe ( nt!KiQueueReadyThread+a5 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiQueueReadyThread+a5
BiosReleaseDate = 11/16/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue May 24 02:04:43.688 2011 (UTC - 4:00)
System Uptime: 0 days 0:11:44.968
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+7e4970 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
BiosReleaseDate = 11/16/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue May 24 01:52:10.354 2011 (UTC - 4:00)
System Uptime: 0 days 0:24:51.634
Probably caused by : usbohci.sys ( usbohci!OHCI_PollAsyncEndpoint+99 )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbohci!OHCI_PollAsyncEndpoint+99
BiosReleaseDate = 11/16/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue May 24 01:21:53.486 2011 (UTC - 4:00)
System Uptime: 0 days 0:09:10.797
Probably caused by : usbohci.sys ( usbohci!OHCI_PollAsyncEndpoint+99 )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  taskmgr.exe
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbohci!OHCI_PollAsyncEndpoint+99
BiosReleaseDate = 11/16/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue May 24 01:09:23.648 2011 (UTC - 4:00)
System Uptime: 0 days 0:09:04.599
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+7e4970 )
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
BiosReleaseDate = 11/16/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue May 24 00:59:39.228 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:34.540
Probably caused by : rdyboost.sys ( rdyboost!SmFpAllocate+4f )
BUGCHECK_STR:  0xDA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xDA_rdyboost!SmFpAllocate+4f
BiosReleaseDate = 11/16/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon May 23 17:56:07.920 2011 (UTC - 4:00)
System Uptime: 0 days 0:13:38.138
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab
BiosReleaseDate = 11/16/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon May 23 02:40:56.101 2011 (UTC - 4:00)
System Uptime: 0 days 0:24:40.318
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
BiosReleaseDate = 11/16/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon May 23 01:56:03.026 2011 (UTC - 4:00)
System Uptime: 0 days 1:49:25.260
Probably caused by : usbohci.sys ( usbohci!OHCI_PollIsoEndpoint+5d )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  BlackOpsMP.exe
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbohci!OHCI_PollIsoEndpoint+5d
BiosReleaseDate = 11/16/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Sun May 22 19:17:52.627 2011 (UTC - 4:00)
System Uptime: 0 days 1:47:08.001
Probably caused by : Unknown_Module_fffff880`00e9a490 ( Unknown_Module_fffff880`00e9a490>+2f8e254 )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_Unknown_Module_fffff880_00e9a490_+2f8e254
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon May 23 23:33:49.698 2011 (UTC - 4:00)
System Uptime: 0 days 0:06:47.978
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0xD1
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

hammerstrong · 24 May 2011

Thanks for the quick detailed response. I just installed the new ASACPI driver. And I did have RivaTuner installed. uninstalled it.

As for usb, I have had everything except my mouse unplugged. the mouse is a Microsoft Sidewinder.

I have had an xbox 360 controller, a vx-1000 cam, an iPod (minus itunes in this install) and a usb stick connected previously in this install.

the keyboard is of a PS/2 connector type.

running the stress tests now.

hammerstrong · 24 May 2011

SeaTools short test was clean. I dont see the long DST option but I ran the Long Generic which timed out after 5 hours (there was a prompt saying that the test was taking too long because of multiple tests/large volume/large overhead etc. I will run it one at a time later.

I also ran prime95 blend test for 2 hours without any errors. but right after i stopped all the workers, the screen went blank and computer rebooted (without creating a dmp file). While restarting after the crash, there was another BSOD which I could not read and which also did not leave a dump file.

Kind of clue less right now. Also noticed some artifacts on the screen during the transition from windows loading screen to user login screen. strange.

hammerstrong · 25 May 2011

ok. doing everything suggested in mgorman87's post above and doing things listed below seems to have fixed the issue (hopefully permanently).

I moved my GTX 460 from its original PCI-e slot (bottom one for the M4A89GTD mobos) to the top one and removed the PCIe switch card from the top one. So now i have my graphics card running at pcie 8x, which is no biggie.

I ran unigine heaven 2.5 bench for 30 mins without crash/artifacts/freezes. running some overnight tests to ascertain the fate of my RAM.

It seems either the switch card supplied for this mobo (which enables the bottom pcie bus to run at 16x) or the PCI-e bus may have been faulty. I will run some more tests to determine which one and post here in-case there are others out there with similar problems.

Windows 7: BSOD running graphic intensive applications

BSOD running graphic intensive applications problems?