BSOD new build

[thalo]

BSOD on a new system

Win7
Win Home Prem. 64bit
Win7 original OS
OEM version disk, installed by me

system and OS about 1 mo. old

ASUS M4A89TD PRO
AMD Phenom II X6 1090T 3.20GHz
ASUS EAH6870 DC/2DI2S/1GD5 Radeon HD 6870
G.SKILL Ripjaws 16GB 240-Pin DDR3 SDRAM

please let me know if further hardware info is required.

 

[mgorman87]

A lot of the BSODs are blaming the DirectX driver. I've also seen problems before with the ASUS branded video cards. It installs some drivers that cause conflicts.

Fist download the latest ATI drivers - ATI Radeon
Next, go into device manager and uninstall your video card. Make sure to choose the option to remove the drivers if one is available. After it's removed reboot the computer and install the latest drivers you just downloaded.

Also remove any ASUS software that you have installed that you don't use.

If the crashes continue then enable driver verifier - http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Please run these tests and report back the results
1. Memtest86 - Run for 7-8 passes - http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
2. Prime95 - Run all three tests for 3-4 hours each or until fail - http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html
3. Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests


BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu May 26 21:18:20.297 2011 (UTC - 4:00)
System Uptime: 2 days 4:17:33.030
Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+139 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  plugin-contain
FAILURE_BUCKET_ID:  X64_0x3B_nt!KeSetEvent+139
BiosReleaseDate = 11/17/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu May 19 13:05:58.688 2011 (UTC - 4:00)
System Uptime: 3 days 20:48:17.420
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+204 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+204
BiosReleaseDate = 11/17/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu May 12 20:14:57.687 2011 (UTC - 4:00)
System Uptime: 4 days 9:06:50.420
Probably caused by : win32k.sys ( win32k!HmgShareLockCheck+73 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Photoshop.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!HmgShareLockCheck+73
BiosReleaseDate = 11/17/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sat May  7 18:07:29.476 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:16.584
Probably caused by : ntkrnlmp.exe ( nt!IovUtilMarkDeviceObject+9 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_VRF_nt!IovUtilMarkDeviceObject+9
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sat May  7 10:18:38.609 2011 (UTC - 4:00)
System Uptime: 1 days 10:43:46.718
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+204 )
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+204
BiosReleaseDate = 11/17/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu May  5 23:33:38.051 2011 (UTC - 4:00)
System Uptime: 1 days 21:34:56.542
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+204 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+204
BiosReleaseDate = 11/17/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu Apr 28 16:25:35.484 2011 (UTC - 4:00)
System Uptime: 0 days 4:47:54.577
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+204 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+204
BiosReleaseDate = 11/17/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu Apr 28 11:36:25.405 2011 (UTC - 4:00)
System Uptime: 0 days 0:17:06.138
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+204 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+204
BiosReleaseDate = 11/17/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Tue Apr 26 23:00:53.308 2011 (UTC - 4:00)
System Uptime: 1 days 12:49:05.210
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+204 )
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+204
BiosReleaseDate = 11/17/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sun Apr 10 19:20:29.430 2011 (UTC - 4:00)
System Uptime: 0 days 3:02:05.948
Probably caused by : ntkrnlmp.exe ( nt!ObDereferenceSecurityDescriptor+20 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ObDereferenceSecurityDescriptor+20
BiosReleaseDate = 11/17/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[thalo]

a couple questions before i start:

1. will any of these tests incapacitate the computer afterwards. i ask this because i am going out of town for the weekend and if i start things tonight i need to make sure that the computer will run after. this computer is my wife's, she uses for work and has a bunch to finish during the weekend.

2. can i run 1 or 2 tests now (tonight) and then finish next week, or should the all be run (consecutively) at the same time?

i will start with the GPU and wait for your response with my questions.

thanks and cheers.

 

[mgorman87]

a couple questions before i start:

1. will any of these tests incapacitate the computer afterwards. i ask this because i am going out of town for the weekend and if i start things tonight i need to make sure that the computer will run after. this computer is my wife's, she uses for work and has a bunch to finish during the weekend.

2. can i run 1 or 2 tests now (tonight) and then finish next week, or should the all be run (consecutively) at the same time?

i will start with the GPU and wait for your response with my questions.

thanks and cheers.

The tests shouldn't incapacitate the computer. You don't need to run the tests all at once. Just run them when you can and report back the results after a test finishes.

 

[thalo]

so far i have done the following:

** ran driver verifier and it would BSOD at startup of windows with and error with usbfilter.sys. ran verifier again but did not select usbfilter as one of the drivers. i removed this from registry editor. havent have any issues since.
** ran memtest, but not for very long, maybe an hour. will run more thorough test shortly. didnt have any errors when i did run, though
** ran the small FFT test with prime95 for about 5 hours with no error reports (result posted). will run the other tests shortly.

i think that the usbfilter.sys was causing other issues (would get reboot when plugging into front usb) but i think there may be some video card issues as well. will finish my testing and post my results.

thanks for the help.
to be continued...

 

[thalo]

another BSOD

It has been a while, but I have had a couple more incidents recently. Getting rid of the usbfilter.sys file seemed to help things.

Attached is the most recent dump files and sysHealth report.

Thanks

 

[mgorman87]

Did you end up running memtest for 7-8 passes?

Have you ran the rest of the prime95 tests?

If you have what were the results? If you haven't then run them now.

atikmdag.sys Tue Apr 19 21:53:29 2011 (4DAE3C99)

Update your video card -
AMD.com | Support & Downloads

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jul  8 18:43:57.253 2011 (UTC - 4:00)
System Uptime: 2 days 8:02:22.346
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+5db6a )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_atikmdag+5db6a
BiosReleaseDate = 11/17/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jun 20 23:57:41.295 2011 (UTC - 4:00)
System Uptime: 0 days 21:15:20.388
Probably caused by : tdx.sys ( tdx!TdxReceiveConnection+1f5 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  AvastSvc.exe
FAILURE_BUCKET_ID:  X64_0xD1_tdx!TdxReceiveConnection+1f5
BiosReleaseDate = 11/17/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jun 20 02:41:22.543 2011 (UTC - 4:00)
System Uptime: 0 days 7:09:29.260
Probably caused by : fileinfo.sys ( fileinfo!FIPfInterfaceClose+48 )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_fileinfo!FIPfInterfaceClose+48
BiosReleaseDate = 11/17/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jun 19 02:09:44.431 2011 (UTC - 4:00)
System Uptime: 0 days 13:44:03.163
Probably caused by : win32k.sys ( win32k!SURFREF::vAltCheckLockIgnoreStockBit+7e )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x3B
PROCESS_NAME:  AdobeARM.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!SURFREF::vAltCheckLockIgnoreStockBit+7e
BiosReleaseDate = 11/17/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu Jun 16 23:07:47.663 2011 (UTC - 4:00)
System Uptime: 2 days 3:21:19.590
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+204 )
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR:  0x3B
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+204
BiosReleaseDate = 11/17/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon Jun  6 02:00:42.410 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:18.158
*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
Probably caused by : usbfilter.sys ( usbfilter+41aa )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xD5
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD5_VRF_usbfilter+41aa
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[Maguscreed]

Just to clarify the above post this is the exact driver and catalyst package you want
ATI Radeon

 

[thalo]

**I ran SeaTools GenericLong and GenericShort tests, both passed.

**I am still running Memtest (running 7:05 now, and only on 3rd pass (pass 2)). Have 9 errors from tests 7 and 8. Err-Bits show mostly 00010000 and one 00080000 codes. See attached image for results so far. I am going to let it run overnight for more passes, it is taking a long time. Will advise more tomorrow.

**Please advise which specific tests I should run with prime95. I ran what I thought I should according to the tutorial link you provided earlier, my posted results were from this one test.

**I updated my GPU drivers just a few hours before my last dump file posting. I uninstalled the driver through the device manager. re-booted then re-installed the most current drivers.

thanks

 

[thalo]

Here is another screen shot after almost 5 passes (pass4). Had to stop the test so the computer could be used again.

 

[Maguscreed]

Yeah it definitely looks like you have a problem there. One common enough to be causing most if not all your crashes here.

The only way to be more specific is actually to pull a memory stick and retest them one at a time.

 

[thalo]

I am back, after about 2 months. I havent had the time to make any proper tests due to the computer being in constant use and me being out of town for 3 weeks. anyway, i ran the memtest again today to try and find the memory stick culprit.

i tested two sticks at a time (i have 4 sticks of 4gb each) in DIMM_A1 and DIMM_B1. ran just one pass because in my previous tests the errors came up pretty quickly. put in the second set of two, in the same slots, ran one pass. both sets passes.

i decided to try and put one set in DIMM_A2 and DIMM_B2, but the computer wouldnt boot. it shows in the MoBo manual that this is an acceptable configuration. the other consideration is that the sticks wernt seated properly (more on that in a bit).

after a couple unsuccessful tries at that i just put all four sticks in and ran the test again. i let it go for two passes and only got one error message.


i was thinking that either the mem sticks wernt seated well initially, or that there are issues with the slots on the MoBo??? i will let the test run again over the weekend for more passes and see what happens.