Solved Random BSODs (mainly 0x3B)

[Tenhi]

Hello Guys,

first my Hardware/OS:

Win 7 Prof 64-bit
Asus Striker Extreme
E6850
Gforce 8800 Ultra
2x2gig Kingston Hyper X PC-6400 CL4
500gig Samsung HD501LJ

The random BSODs started after I upgraded my RAM so my first guess was that the RAM is damaged... but after running MemTest for 10 passes w/o errors I dont know what else could be the cause :/ I tried to debug with WinDbg but I couldnt really find the problem. The BSODs are completely random, sometimes while playing, sometimes while surfing. Most Drivers should be up to date. So I would be glad if someone could lend me a hand


PS: sfc /scannow and memtest run with no errors, same goes for chkdsk

Edit: sorry for the bad English... Im from Germany oh and, if I dont answer quickly its probably because the time diffrence :/

Edit 2: I added the dumpfiles + the perfmon and scan thing from the faq (first file where only the minidumps). Oh and the Anti-Virus wasnt recognized but its Sophos Antivirus.

 

[reventon]

Hi,

Most of the BSODs mention graphics type crashes - could be caused by faulty RAM.

The random BSODs started after I upgraded my RAM so my first guess was that the RAM is damaged... but after running MemTest for 10 passes w/o errors I dont know what else could be the cause :/ I

Memtest is not 100% reliable, the RAM could be faulty and it could still pass. Can you swap back to your old sticks of RAM?

You should also update this driver, I don't think it is the cause but it really should be updated

[font=lucida console][B]ASACPI.sys[/B]   Mon Mar 28 15:30:36[COLOR=Red][B] 2005[/B][/COLOR] (42476C4C)[/font]

ASACPI.sys - ASUS ACPI Driver; the 2005 version is almost guaranteed to cause BSODs on Windows 7 systems. Update link here, update instructions (slideshow) here (note that in the last step you select the ATK0110 driver in the list instead of the one mentioned)

Regards,
Reventon

BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov  5 11:21:57.706 2010 (GMT+13)
System Uptime: 0 days 14:34:22.267
Probably caused by : win32k.sys ( win32k!NtUserGetForegroundWindow+17 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  mpc-hc.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 00000000`00000000 fffff880`09363210 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  2 03:57:01.962 2010 (GMT+13)
System Uptime: 0 days 5:17:11.647
Probably caused by : hardware ( win32k!SURFACE::bDeleteSurface+371 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  ICQ.exe
Bugcheck code 00000050
Arguments fffff960`74ecd90f 00000000`00000000 fffff960`00115409 00000000`00000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov  1 06:24:11.100 2010 (GMT+13)
System Uptime: 0 days 3:12:53.785
Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgkWaitForVerticalBlankEvent+399 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 00000000`00000000 fffff880`06e87150 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct 27 13:05:04.339 2010 (GMT+13)
System Uptime: 0 days 11:20:45.040
Probably caused by : win32k.sys ( win32k!zzzUpdateCursorImage+1be )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`000e3b8e fffff880`038ee030 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Oct 24 13:37:19.372 2010 (GMT+13)
System Uptime: 0 days 9:54:37.158
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )
BUGCHECK_STR:  0x1a_41287
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  javaw.exe
Bugcheck code 0000001A
Arguments 00000000`00041287 00000000`00190100 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/font]

 

[Tenhi]

Thank you for the answer reventon. I updated the driver you mentioned (I found it via WinDbg but couldnt figure out what it was/ how to update...). Should I wait and see if the updated driver stoped the BSODs or should I swap the RAM right now?

 

[reventon]

Wait a day or two if possible, as soon as you get another BSOD swap the RAM.

 

[Tenhi]

Ok, thanks for the help. I will wait and see if the bsods happen again.

Tenhi

 

[Tenhi]

Ok, I just got a BSOD. 0x3B again, so the driver didnt solve the problem. I changed the RAM back to my old sticks. Now Im waiting to see if the BSODs keep poping up or not, if they stop the RAM was at fault.

Here the last crashdump (with the new RAM still installed)

 

[reventon]

Hi,

The dump is the same kind as a few of your previous ones. Nothing of too much interest.

Let us know how the system runs with the older RAM in place.

Regards

BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov  6 05:30:35.160 2010 (GMT+13)
System Uptime: 0 days 5:06:05.845
Probably caused by : cdd.dll ( cdd!DrvBitBlt+278 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  MediaMonkey.ex
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`0074a228 fffff880`0924c280 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/font]

 

[Tenhi]

System is up for about a day without bsods... I will give a new Edit if it runs for 2-3 days without one. Strange thing is, when I switched to my old RAM my Internet lost its connection randomly, but it looks like I fixed that through changing the powersettings of the Network Card, like suggested in this Forum *sigh*

 

[reventon]

Please - make a new post instead of just editing that one (so that an "new reply" email is sent out). Because with up to 50 threads 'active' here and on other forums at any given time I really don't have time to check back to see if this one was solved (however I do like to know if it was solved).

 

[Tenhi]

Hello reventon,

System runs up untill now without new bsods, so I would guess the RAM was really at fault. Will send it back to the shop and get new sticks, if the bsods happen again I think there is a compatibility problem with the RAM Sticks and my system. Anyway a big thanks for the help reventon

Regards
Tenhi

 

[reventon]

Good to hear it! Thanks for letting us know.