Solved BSOD Bad Pool Header (Driver at fault- audiodg.exe)

[sbhardwaj]

Hello everybody, while I was playing music on my computer I had a BSOD. This BSOD(Bad Pool Header)has affected me when gaming too.

I do not know what to do I really would appreciate all the help I could get.

Here you will find my dmp file uploaded to my skydrive.

https://onedrive.live.com/redir?res...2170&authkey=!AJ11i3jvbrJbMEg&ithint=file,dmp

 

[Golden]

Additional information is required.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

 

[sbhardwaj]

Additional information is required.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

Here you go.

 

[Golden]

There aren't any .dmp file in your attachment. These are required to analyse the BSOD.

Follow these steps:

1. Configure Windows to create minidumps:
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

2. Set the paging file on C: to be the same size as the physically installed RAM:
Virtual Memory Paging File - Change

3. Set the Windows Error Reporting service to MANUAL:
http://www.sevenforums.com/tutorials/2495-services-start-disable.html

Now follow this:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

 

[sbhardwaj]

There aren't any .dmp file in your attachment. These are required to analyse the BSOD.

Follow these steps:

1. Configure Windows to create minidumps:
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

2. Set the paging file on C: to be the same size as the physically installed RAM:
Virtual Memory Paging File - Change

3. Set the Windows Error Reporting service to MANUAL:
http://www.sevenforums.com/tutorials/2495-services-start-disable.html

Now follow this:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

Hold on, I cut my dmp. files out of my minidump folder to upload them easier and that may the reason why no files have turned out in the attachment. I will just restore them to the folder and re-upload the attachment.


Here done. Checked and there is the most recent dmp file popping up.

 

[Golden]

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

Use !analyze -v to get detailed debugging information.

BugCheck 19, {21, fffffa8014470000, 1e10, 1a0012001a1e25}

*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
Probably caused by : [B][COLOR="Red"]RTKVHD64.sys[/COLOR][/B] ( RTKVHD64+2042c )

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

0: kd> lmvm RTKVHD64
start             end                 module name
fffff880`08022000 fffff880`083d7780   RTKVHD64 T (no symbols)           
    Loaded symbol image file: RTKVHD64.sys
    Image path: \SystemRoot\system32\drivers\RTKVHD64.sys
    Image name: RTKVHD64.sys
    Timestamp:        Fri [B][COLOR="red"]Mar 14[/COLOR][/B] 21:33:23 [B][COLOR="Red"]2014[/COLOR][/B] (5322E1FB)
    CheckSum:         003C3207
    ImageSize:        003B5780
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Check for an update for the Realtek HD audio driver here:
Realtek

 

[sbhardwaj]

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

Use !analyze -v to get detailed debugging information.

BugCheck 19, {21, fffffa8014470000, 1e10, 1a0012001a1e25}

*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
Probably caused by : [B][COLOR="Red"]RTKVHD64.sys[/COLOR][/B] ( RTKVHD64+2042c )

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

0: kd> lmvm RTKVHD64
start             end                 module name
fffff880`08022000 fffff880`083d7780   RTKVHD64 T (no symbols)           
    Loaded symbol image file: RTKVHD64.sys
    Image path: \SystemRoot\system32\drivers\RTKVHD64.sys
    Image name: RTKVHD64.sys
    Timestamp:        Fri [B][COLOR="red"]Mar 14[/COLOR][/B] 21:33:23 [B][COLOR="Red"]2014[/COLOR][/B] (5322E1FB)
    CheckSum:         003C3207
    ImageSize:        003B5780
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Check for an update for the Realtek HD audio driver here:
Realtek

An update under High Definition Audio Codecs (Software)?

 

[sbhardwaj]

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

Use !analyze -v to get detailed debugging information.

BugCheck 19, {21, fffffa8014470000, 1e10, 1a0012001a1e25}

*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
Probably caused by : [B][COLOR="Red"]RTKVHD64.sys[/COLOR][/B] ( RTKVHD64+2042c )

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

0: kd> lmvm RTKVHD64
start             end                 module name
fffff880`08022000 fffff880`083d7780   RTKVHD64 T (no symbols)           
    Loaded symbol image file: RTKVHD64.sys
    Image path: \SystemRoot\system32\drivers\RTKVHD64.sys
    Image name: RTKVHD64.sys
    Timestamp:        Fri [B][COLOR="red"]Mar 14[/COLOR][/B] 21:33:23 [B][COLOR="Red"]2014[/COLOR][/B] (5322E1FB)
    CheckSum:         003C3207
    ImageSize:        003B5780
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Check for an update for the Realtek HD audio driver here:
Realtek

Okay, the installation for the new audio drivers appears to be a success. The new drivers are a couple months ahead of the old drivers. Hopefully this is the last of this type of BSOD I will see.

 

[Golden]

Keep us updated please - its nice to hear if the suggestion solved the problem.