Solved BSOD starting recently bought games -

[Nectanebus]

I am getting a BSOD every time I start a newly purchased game. The games are :-

WarHammer
COD Blackops II
Aliens Colonial Marines

I suspect it is a driver issue - probably a video driver. I have the AMD Radeon HD 6800 card. I have tried removing the Catalyst software (rebooted) and installed the latest version but still BSODs.

The BSOD info is below:

*** STOP: 0x00000101 (0x0000000000000021, 0x0000000000000000, 0xfffff880009b3180,
0x0000000000000004)
*** ntoskrnl.exe - Address 0xfffff800032cbfc0 base at 0xfffff8000324d000 DateStamp
0x503f82be

I have attached the following zips:

Diag tool (grab all)
Latest dmp zipped from minidump folder

SFC /scannow did not find any violations

I have not installed any new hardare recently.

Please help

 

[Nectanebus]

...

 

[Dsprague]

I really really hate to be the bearer of bad news but it seems that you have a 0x124 stop which indicates a hardware level problem:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80084615f8, 0, 0}

Probably caused by : AuthenticAMD

Followup: MachineOwner
---------

had a look at the error record for these crashes and it looks like something is causing a time out that shouldnt be happening but doesn't point very well to what it is:

kd> !errrec fffffa80084bb038
===============================================================================
Common Platform Error Record @ fffffa80084bb038
-------------------------------------------------------------------------------
Record Id     : 01ce091c4e660c48
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 2/12/2013 12:27:36 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80084bb0b8
Section       @ fffffa80084bb190
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
[COLOR=Red]Error Type    : BUS error[/COLOR]
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000600f12
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80084bb100
Section       @ fffffa80084bb250
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : 12 0f 60 00 00 08 06 00 - 0b 22 98 1e ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa80084bb250

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80084bb148
Section       @ fffffa80084bb2d0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

[COLOR=Red]Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 0)[/COLOR]
  Status      : 0xb880000000020f0f

See this thread for more information:
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

you also have two BSODs dealing with your network card driver:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {21, 0, fffff880009b3180, 4}

*** [COLOR=Red]WARNING: Unable to verify timestamp for Rt64win7.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

you can update the drivers from here:

Realtek

 

[Nectanebus]

Many thanks for the quick reply.

I will look into your reply and do some harware tests. I am not yet convinced of a hardware fault as the BSODs only happen with recently purchased games. Already installed games do not reproduce the error.

The BSODs only occur during installation of the games mentioned, one of which is a Steam game (all other Steam games work OK).

It is possible that the installation process is accessing hardware in a way that is not usual. I have updated the NIC driver which was 2 years old and can still recreate the fault. I will upload the two most recent dumps after the nic driver update.

 

[Nectanebus]

Most recent dumps zipped

 

[Dsprague]

sorry misread your last post, If the driver in question is not the problem here please do the following:
run driver verifier and allow it to crash your computer, when it crashes please disable driver verifier and then post your new dump files here for analysis:

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Tip: if you cant boot normally into windows boot into safe mode and then disable driver verifier.

 

[Nectanebus]

I still get the BSODs in the same manner... sometime into the installation of these games. I am wondering what the installer is attempting at the time of the crash. Sometimes on the BSOD i get a graphics glitch just prior to the BSOD as if a vidoe or something is about to play like an advert or trailer.

I also noticed that my attached file did not have all files attached from SF diags so here are the missing reports

EDIT:

I just noticed this on an event system log

The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_GENERIC-&PROD_COMPACT_FLASH&REV_1.01#7&1C4905A4&0&058F63646476&1#.

 

[Dsprague]

Please run the following programs to rule out malware infection:

Windows Defender Offline

http://support.kaspersky.com/5350

also please do as i instructed in my previous post and enable driver verifier

 

[Nectanebus]

Attached verifier dump zipped - This is the file in minidump while running verifier.

 

[Dsprague]

Its another 0x124 BSOD:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80093de038, 0, 0}

Probably caused by : AuthenticAMD

Followup: MachineOwner
---------

I'm really not sure what else to tell you than start testing your hardware there are very few things that cause false positives of the 0x124 stop.

 

[Nectanebus]

Well... Fingers crossed but I did a BIOS flash upgrade guessing that new games are using some new process (and working through a logical check of all updateable systems and drivers).

I tested for BSODs after each updated driver and the BSODs stpooed after the bios upgrade.

I have yet to test fully but suspect this is the cure,

Thanks for the support.

 

[Dsprague]

Glad we could help.