BSOD after closing games - Windows 7 x64

[WhiteMoon]

Hi guys, i need some help about this. Im having BSOD after closing games or alt tabbing out, it happens 5/10 times.
Following this thread im uploading two files, perfmon.zip and SysnativeFileCollectionApp.zip.
I saw a lot of warning about a failure disk in the perfmon file but im not using that disk, Windows and everything else is installed in a new disk.

Hardware/Software information:
Windows 7
64 bits
I installed this after my old disk reported me that he was dying, 3 months ago more or less. (The BSOD started way before this)
AMD Phenom II 920
HD 4870 1GB
M4A78-EM
Cooler Master Extreme Power Plus 550w
Desktop

If you guys needs more info please let me know.

Thanks in advice!

 

[Patrick]

Hi,

Varying bug checks.

SYSTEM_SERVICE_EXCEPTION (3b)

This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

BugCheck 3B, {[COLOR=#ff0000]c0000005[/COLOR], [COLOR=#0000ff]fffff960000c4283[/COLOR], [COLOR=#006400]fffff88008cbf060[/COLOR], 0}

0: kd> ln fffff960000c4283
(fffff960`000c41e0)   win32k!HmgLockEx+0xa3   |  (fffff960`000c432c)   win32k!RGNOBJ::vSet

win32k!HmgLockEx+0xa3 caused the access violation.

0: kd> .cxr 0xfffff88008cbf060;r
rax=fffff900c0200000 rbx=0000000000000000 rcx=fffffa8006d198a0
rdx=fffff900c0200000 rsi=0000000000000000 rdi=fffff900c0200000
rip=fffff960000c4283 rsp=fffff88008cbfa40 rbp=0000000000000000
 r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
r11=fffff88008cbfaa8 r12=0000000002cebf00 r13=0000000000000000
r14=0000000000000001 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
[COLOR=#ff0000]win32k!HmgLockEx+0xa3[/COLOR]:
fffff960`000c4283 0fb7430c        [COLOR=#0000ff]movzx   [/COLOR][COLOR=#008000]eax[/COLOR],word ptr [[COLOR=#800080]rbx+0Ch[/COLOR]] ds:002b:00000000`0000000c=????

On the faulting instruction, we were copying the contents of the memory at address rbx+0C to eax and zero extending it. rbx is volatile therefore we cannot check it, and eax is inaccessible with only a minidump. In any case, this is likely being caused by a driver.

---

1. AODDriver2.sys is listed and loaded in your modules list which is AMD Overdrive; also in EasyTune6 for Gigabyte motherboard. Known BSOD issues in Win7 & 8.

Please uninstall either software ASAP! If you cannot find either software to uninstall, or it's not installed, please navigate to the following filepath:

C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys and rename AODDriver2.sys to AODDriver.2old and then Restart.

2. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

3. Install Service Pack 1 ASAP - Learn how to install Windows 7 Service Pack 1 (SP1)

4.

0: kd> lmvm xusb21
start             end                 module name
fffff880`069df000 fffff880`069f1100   xusb21     (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\xusb21.sys
    Image name: xusb21.sys
    Timestamp:        Thu Aug 13 18:10:17 [COLOR=#ff0000]2009[/COLOR]

Win7 Xbox controler driver dated from 2009. 2009 version is known to cause crashes, so please update to 2012 version or uninstall drivers + controller ASAP - Software Downloads | Microsoft Hardware

Regards,

Patrick

 

[WhiteMoon]

First of all thanks for your help Patrick!

1. AODDriver2.sys is listed and loaded in your modules list which is AMD Overdrive; also in EasyTune6 for Gigabyte motherboard. Known BSOD issues in Win7 & 8.

Please uninstall either software ASAP! If you cannot find either software to uninstall, or it's not installed, please navigate to the following filepath:

C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys and rename AODDriver2.sys to AODDriver.2old and then Restart.

Done, renamed.

2. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

Done.

3. Install Service Pack 1 ASAP - Learn how to install Windows 7 Service Pack 1 (SP1)

Updating.

4.

0: kd> lmvm xusb21
start             end                 module name
fffff880`069df000 fffff880`069f1100   xusb21     (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\xusb21.sys
    Image name: xusb21.sys
    Timestamp:        Thu Aug 13 18:10:17 [COLOR=#ff0000]2009[/COLOR]

Win7 Xbox controler driver dated from 2009. 2009 version is known to cause crashes, so please update to 2012 version or uninstall drivers + controller ASAP - Software Downloads | Microsoft Hardware

I downloaded the lastest driver from that link and is the same version =/. 2.1.0.1349 from 2009. There is no 2012 version on Microsoft website.

Ill keep you updated.

Thanks again!

 

[Patrick]

Great work.

There is no 2012 version on Microsoft website.

Might just have to bite the bullet and uninstall the driver + remove the controller if the issue persists. If not, don't worry about it.

Keep me updated.

Regards,

Patrick

 

[WhiteMoon]

Hi again, this BSOD is gone, but im having a new one. Should i start a new thread?

This started a few days ago while i was playing a game, the screen started showing this. I can only start in safe mode and after a few restart the BSOD is gone for the rest of the uptime. But when turn on the computer the next day its happens again.
I havent made any changes recently.

Thanks!

 

[Patrick]

No, that's fine, we can use this thread.

My least favorite bug check :thud:

VIDEO_TDR_FAILURE (116)

Attempt to reset the display driver and recover from timeout failed.

3: kd> k
Child-SP          RetAddr           Call Site
fffff880`05bec9c8 fffff880`040c5000 nt!KeBugCheckEx
fffff880`05bec9d0 fffff880`040c4d0a dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05beca10 fffff880`0416bf07 dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`05beca40 fffff880`04195b75 dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05becb20 fffff880`041942bb dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`05becb50 fffff880`041672c6 dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`05becbf0 fffff880`04193e7a dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`05becd00 fffff800`0332832e dxgmms1!VidSchiWorkerThread+0xba
fffff880`05becd40 fffff800`0307d666 nt!PspSystemThreadStartup+0x5a
fffff880`05becd80 00000000`00000000 nt!KxStartSystemThread+0x16

The DirectX MMS video scheduler scheduled a worker thread, scheduled command to run, sent a wait for scheduler events, sent the render command to the execution queue with a wait timer, checked the progress of the display driver communicating with the hardware, it was reported that the display driver is hanging.

At this point, the DirectX Kernel then came in and noted that Timeout Detection Recovery is required (TDR) to reset the display driver, but it then failed to recover in the allotted recovery period, so the box bug checked.

3: kd> lmvm atikmpag
start             end                 module name
fffff880`0158f000 fffff880`015ee000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Mon Apr 29 22:48:15 2013

Driver is over a year old, update your video drivers ASAP.

 

[WhiteMoon]

Driver is over a year old, update your video drivers ASAP.

Thats the last driver package, anyway i performed a clean uninstall/install.

Now when i try to start Catalyst Center its gave me a new error that says "Could not load file or assembly 'CLI.Implementation' or one of its dependencies. The system cannot find the file specified."
Its doesnt seems to be affecting anything at all, beyond that i cant start Catalyst Center. But i made a research about this and its seems that it have something to do with .NET Framework version. I could try to fix it if you say that it have something to do with the BSOD but i dont think so. You are the expert here so its your call.

Ill keep you updated Patrick.

Thanks!

 

[Patrick]

Is .NET up to date? If so, try repairing it. It may have nothing to do with .NET, and it may have just been a bad install. I'd uninstall the drivers and reinstall again.

 

[WhiteMoon]

Is .NET up to date? If so, try repairing it. It may have nothing to do with .NET, and it may have just been a bad install. I'd uninstall the drivers and reinstall again.

I just did it again and when its finish its says "Installation completed, with warnings. Click here to view the report log." I opened the log and i dont see any fails or warnings, all i see is "Success".
I attach the log file.

Anyway, i remember to have this error years ago and i fixed it following a guide i found and it had something to do with .NET. Ill try to fix it.

So far no BSOD, but the lats 2 BSOD that i had (yesterday and today) was when i turned on the computer in the morning after a few hours off.

Ill keep you updated.

Thanks.

 

[Patrick]

I don't see any errors within the XML either, strange.

Well, keep me updated regarding that .NET fix.

 

[WhiteMoon]

I don't see any errors within the XML either, strange.

Well, keep me updated regarding that .NET fix.

Its fixed.

And no BSOD for the last 24 hours. Anyway, i dont think that this have anything to do with the .NET or Catalyst problem, because when i had the BSOD Catalyst was working good.

Ill keep you updated,
Thanks again.

 

[Patrick]

Sounds good.