[SOLVED] ATI HD Series Random Blue Screen error: BugCheck 0x0000007e ntoskrnl kb965494

[Related Problems]
Solves random BSOD Blue Screen of Death ATI HD Series cards - Spontaneous random BSOD with different error codes each time
Solves problems with SoundBlaster X-FI sound (on board and add on card) extreme gamer - Sound would sound severely choppy or cut off abruptly
Solves random system delays - system randomly pauses for no apparent reason
Solves Steam Disconnect problems - Quite noticeable in Call of Duty 4 Modern Warfare 2
Solves Call of Duty 4 Modern Warfare 2 in game random delays or dropping out of game while your playing. Usually when first starting up the game. Not having NAT enable may cause a similar delay as well.

[Source of problem]
The problem is with Microsoft loading an old driver for new hardware when you first load the OS. Shame on you Microsoft.  6 weeks to figure this one out and it is CLEARLY Microsoft's fault. Sorry but no NDA's here.

Its a simple fix, yet almost impossible to find. Catalyst Install Manager - ATI HDMI Audio Device will add an Audio device rather than replace the HDMI Audio Device driver Microsoft loads at OS install time. Or the driver is ignored all together because Microsoft already loaded a driver at install time for that device.

[Clean install FIX]
When installing the ATI 10.6 Catalyst, use custom install and exclude the HDMI Audio by unchecking the box next to the HDMI Audio. The drivers still end up in the ATI Catalyst installation directory so you may want to note the ATI installation path. The problem here is ATI will add a HDMI High Definition Aduio Device, NOT replace the Windows device already loaded. Or it may not load a second device. Either way, it will use the Microsoft device driver.

Update Driver Software with the ATI driver- Microsoft High Definition Audio Device driver manually following the instructions below. 

[Windows OS Already loaded FIX]
-Device Manager-
Updated driver using computer -> right click manage -> devices -> sound -> right click HDMI High Definition Audio Device -> Update driver and browse to ATI directory (check the include sub-folders).

Also noticed default BIOS settings cause problems with NB and DRAM. Overclocked to get voltage up on the system. Even though I adjusted BIOS settings, I still got plenty of BSOD until I updated the Microsoft High Definition Audio Device driver with the ATI driver. 

Ran Ubuntu without a single issue prior to making any changes to accommodate the Windows 7 OS. For some reason Windows is fussy over certain settings where as Ubuntu 10.04 LTS loads and runs without a single problem.

I have the memory.dmp and mini.dmp logs. Any help and all help appreciated :D

After running through the steps listed below, the problem here is the ntoskrnl.exe causing multiple bugchecks (BSOD). Even though this was a problem with Vista, this exact problem occurs with Windows 7.

  • eventID: 1001 Source: BugCheck
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff88000e34294, 0xfffff880031bda18, 0xfffff880031bd280). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052310-17316-01.

    The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000109 (0xa3a039d898a4a950, 0xb3b7465eeb217b7e, 0xfffff80002d18cc0, 0x0000000000000001). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052110-23197-01.

    OS: Microsoft Windows 7 Ultimate 64bit
    Antivirus: Microsoft Windows Security Essentials
    Motherboard: Gigabyte GA-890FXA-UD5
    Video: Diamond ATI Radeon HD5850 1GB DDR5
    CPU: AMD X4 965BE
    HD: Hitachi 1TB HDE721010SLA330 S/N MS03G16K
    PS: Antec EarthWatt 750W V2.3 PSU
    KB: Logitech G15
    Mouse: Razer Deathadder 3.5G
    Game Pad: Belkin n52te

    First attempt to resolve this problem:
    Fresh OS loaded and BSOD immediately after reboot. Reason or details is unknown due to immediate reboot without a kernel dump. No events recorded in Windows Event Logs with bugcheck information.

    Ran Windows Update for current patches. BSOD random on restarts. 
    Load ATI Catalyst 10.4 Suite for Windows 7 (64 bit). BSOD random on restarts.
    Problem reproduced when system is shutdown and booted. Odds are BSOD will occur without kernel or mini dump being written.
    Run Verifier - 90% chance of BSOD

    Ran Check Disk - Seems to be stuck on stage 4 "Verifying file data" 57531 of 63472 files processed. 1:05: PM 05/21/2010 FAIL stopped here 1:44 PM

    Second attempt to solve this problem (low level format):
    Using Hitachi Tools - http://www.hitachigst.com/hdd/support/download.htm Drive Fitness Test - Switch BIOS from AHCI to IDE to access SATA Drive.
        Quick Test results - HDE721010SLA330 Operation completed successfully / Disposition Code = 0X00
        Erase Boot Record result - 0x00
        Erase Disk (clean disk takes some time ~3.5 hours for 1TB) / Analysing media 5:07 PM / done 8:20 PM 6 hours and change result - successful 0x00  

    Update BIOS to F2 05/14/2010 (Improve CPU compatibility)
        Press Del to go into BIOS F8 to enter Q-Flash Insert USB Thumb Drive (Drive A if no floppy is in system) Select File

    Change BIOS settings -
        Integrated Peripherals -
            OnChip SATA Type [Native IDE] Change to [AHCI]

    (No Option for this) F6 for drivers to load into Pre-OS Windows 7 64 bit

    Install Windows 7 Ultimate 64 bit 9:02 PM / Installer Reboot 9:14 PM / completing installation reboot 9:18 PM / Finalized 9:21 PM- result - GOOD
    Install NEC USB 3.0 driver 9:22 PM - result - GOOD

    Autoupdate added KB978601 (pending reboot) and KB979309 - result - GOOD

    Install Lan_win7 Realtek network drivers - result - GOOD
    Install win7_chipset (Installs ATI Catalyst install manager 03.00.0765) 9:30 PM - result - BSOD KERNEL DUMP RENAMED MEMORY.DMP TO 5212010935PMMEMORY.DMP

    Hitachi drive configured requires reboot (shutdown instead for cold boot) - 9:37 PM - result  - logged in

    Install Microsoft Windows Security Essentials 64 bit 9:43 PM d/l latest and scan  / done 9:49 PM- results - GOOD
    Shutdown - 9:51 PM
    Power on - result - GOOD

    Install ATI 10-4_vista64_win7_64_dd_ccc_wdm_enu (from ATI AMD Website) 9:59 PM start / 10:01 PM requires reboot (shutting down) - result - GOOD
    Windows Install wants to make changes - C:\window\SysWOW64\msiexec.exe /x {72736F5F-520D-472A-88C-7B0 ERRRR it went away on its own. Shutting down - 10:05 PM /qn REBOOT=Really Suppress <---- Came up again after cold start. Think it had something to do with ATI registration window.

    Install Google Chrome - result - GOOD

    Install Fusion - 
    Install AMD OverDrive Utility - Enable AMD Smart Profiles -
    Power up - result - GOOD

    Install G15 - result - GOOD

    Install Ventrilo 3.0.5 Windows x64 - GOOD

    Install Steam Client
    Install COD4MW2

    Change Power Saving settings for the computer to never sleep.
    Install gtalk, gApps

    Up until 8:57 AM 5/22/2010 BSOD Mini dump.
    Kernel dmp renamed to 5222010857AMMEMORY.DMP

    2 more BSOD's over 2 days.

Question Info

Last updated November 8, 2018 Views 40,607 Applies to:


Check this thread for information on using BlueScreenView, MyEventViewer and other methods to
troubleshoot BlueScreens - top two answers.



Hardware is very suspect!

Since you reformatted and reloaded Windows this indicates the problem is either hardware or a
very basic driver which was reloaded - Video/Display, Network/WiFi, Sound, possibly 3rd party
mouse and/or keyboard, BIOS, low level chipset drivers and others.

This error is usually a driver issue and display adapter (video) driver is the most suspect though it
could be others. Antivirus/antispyware/security programs, hardware (heat) and major software issues
can also cause the error. When you get to the driver section of the troubleshooter use my generic
methods in the next message and then return to the troubleshooter if needed.

Have you added hardware recently or updated drivers? Be sure to look in Control Panel - Windows
Updates to see if any drivers were updated there. Other lessor possibilities include antivirus/anti-
spyware/security programs.

When you get to the driver and memory sections of the troubleshooter refer to the next message to
update drivers and test memory and then refer back to the troubleshooter if needed.


Even though you have tried some of these here a fairly complete troubleshooter just in case.

BCCode: 7E      0x0000007E


The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check is a very common bug check. To interpret it, you must identify which exception was generated.

Common exception codes include the following:

  • 0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.


For a complete list of exception codes, see the Ntstatus.h file that is located in theinc directory of the Microsoft Windows Driver Kit (WDK).

Resolving the Problem

If you are not equipped to debug this problem, you should use some basic troubleshooting techniques.

  • Make sure you have enough disk space.
  • If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
  • Try changing video adapters.
  • Check with your hardware vendor for any BIOS updates.
  • Disable BIOS memory options such as caching or shadowing.

If you plan to debug this problem, you might find it difficult to obtain a stack trace. Parameter 2 (the exception address) should identify the driver or function that caused this problem.

If exception code 0x80000003 occurs, a hard-coded breakpoint or assertion was hit, but the system was started with the/NODEBUG switch. This problem should rarely occur. If it occurs repeatedly, make sure that a kernel debugger is connected and the system is started with the/DEBUG switch.

If exception code 0x80000002 occurs, the trap frame supplies additional information.

If you do not know the specific cause of the exception, consider the following issues:

  • Hardware incompatibility. Make sure that any new hardware that is installed is listed in the Microsoft Windows Marketplace Tested Products List.
  • Faulty device driver or system service. A faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.

If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you must start the computer by using the Recovery Console to access the file.

If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, you can remove the service by starting the computer by using the Recovery Console and then deleting the offending system service file.

Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x7E.

You can also disable memory caching of the BIOS might to try to resolve the error. You should also run hardware diagnostics, especially the memory scanner, that the system manufacturer supplies. For more information about these procedures, see the owner's manual for your computer.

The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is lack of disk space for installation and system BIOS incompatibilities. For problems during Windows installation that are associated with lack of disk space, reduce the number of files on the target hard disk drive. Check for and delete any temporary files that you do not have to have, Internet cache files, application backup files, and.chkfiles that contain saved file fragments from disk scans. You can also use another hard disk drive with more free space for the installation. You can resolve BIOS problems by upgrading the system BIOS version.

BCCode: 7E      0x0000007E  <-- read this


BCCode: 109  0x00000109


There are generally three different causes for this bug check:

  1. A driver has inadvertently, or deliberately, modified critical kernel code or data. Microsoft Windows Server 2003 with Service Pack 1 (SP1) and later versions of Windows for x64-based computers do not allow the kernel to be patched except through authorized Microsoft-originated hot patches. For more information, see Patching Policy for x64-based Systems.

  2. A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was started. Normal breakpoints (bp) can only be set if the debugger is attached at start time. Processor breakpoints (ba) can be set at any time.

  3. A hardware corruption occurred. For example, the kernel code or data could have been stored in memory that failed. 

BCCode: 109  0x00000109  <-- read this


Look in the Event Viewer to see if anything is reported about those.

MyEventViewer - Free - a simple alternative to the standard event viewer of Windows.
TIP - Options - Advanced Filter allows you to see a time frame instead of the whole file.



Here are some methods to possibly fix the blue screen issue. If you could give the Blue Screen
info that would help. Such as the BCC and the other 4 entries on the lower left. And any other
error information such as STOP codes and info such as IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.

As examples :

BCCode: 116
BCP1: 87BC9510
BCP2: 8C013D80
BCP3: 00000000
BCP4: 00000002

or in this format :

Stop: 0x00000000 (oxoooooooo oxoooooooo oxooooooooo oxoooooooo)
tcpip.sys - Address 0x00000000 base at 0x000000000 DateStamp 0x000000000

This is an excellent tool for posting Blue Screen Error Information

BlueScreenView scans all your minidump files created during 'blue screen of death'
crashes, and displays the information about all crashes in one table - Free


Many BlueScreens are caused by old or corrupted drivers, especially video drivers however
there are other causes.

You can do these in Safe Mode if needed or from Command Prompt from Vista DVD or
Recovery Options if your system has that installed by the maker.

How to Boot to the System Recovery Options in Windows 7

You can try a System Restore back to a point before the problem started if there is one.

How to Do a System Restore in Windows 7


Do these :

Start - type this in Search Box ->  COMMAND   find at top and RIGHT CLICK  -  RUN AS ADMIN

Enter this at the prompt - sfc /scannow

How to Repair Windows 7 System Files with System File Checker

How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program
generates in Windows Vista cbs.log (and Windows 7)

The log might give you the answer if there was a corrupted driver. (Does not tell all the possible
driver issues).

Also run CheckDisk so we can rule out corruption as much as possible.

How to Run Check Disk at Startup in Windows 7


Often updating drivers will help, usually Video, Sound, Network Card  (NIC), WiFi, 3rd party
keyboard and mouse, as well as other major device drivers.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.

Installing and updating drivers in 7 (updating drivers manually using the methods above is preferred to ensure the latest drivers from System maker and Device makers are found)

How To Disable Automatic Driver Installation In Windows Vista - Drivers


How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart

Troubleshooting Vista Blue Screen, STOP Errors (and Windows 7)

Understanding and Decoding BSOD (blue screen of death) Messages

Windows - Troubleshooting Blue Screen Errors


In some cases this might be required.

StartUp Repair from Recovery Options or Windows 7 disk

How to Run a Startup Repair in Windows 7

How to Boot to the System Recovery Options in Windows 7

How to Create a Windows 7 System Repair Disc

How to Do a Repair Install to Fix Windows 7

Hope this helps.

Rob Brown - MS MVP - Windows Desktop Experience : Bicycle - Mark Twain said it right.


Rob Brown - Microsoft MVP - Windows and Devices for IT 2010 - current
Windows Insider MVP 2016 - current

1 person was helped by this reply


Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.