Sign in with
Sign up | Sign in
Your question

Need Help with Constant BSODs

Tags:
  • Windows XP
Last response: in Windows XP
Share
August 15, 2011 12:53:54 PM

Hi all,

Praying that someone can help this newbie. :help: My Dell Vostro 220 has been working fine until 8/6 - when I started getting these BSODs. I haven't installed any new hardware or software. But I'm still running Win XP Pro SP-3, and I think my problems began after running the last Windows Update. I've tried: deleting my NAV and any unecessary programs; updating the drivers that I could - at Windows Update & Dell; total check with TuneUp Utilities; trying to system restore. Still, my PC crashes every time it goes into sleep mode.

I did see an error message in Device Manager for the DVD/CD-ROM drive (that I don't even use). I couldn't install the driver (which seems to be very old) from Dell.com. Uninstalling the driver didn't work. The Even Viewer shows warnings about Microsoft Fax failure, but I don't have an internal fax.

The last time I called Dell, I got someone in India who didn't seem to know much more than I did. I'm totally confused at this point, but I am attaching the WhoCrashed report in hopes that someone can tell my specifically what is wrong. Thank you!!!!

Here is my system info:
Tech Support Guy System Info Utility version 1.0.0.1
OS Version: Microsoft Windows XP Professional, Service Pack 3, 32 bit
Processor: Intel(R) Pentium(R) Dual CPU E2200 @ 2.20GHz, x86 Family 6 Model 15 Stepping 13
Processor Count: 2
RAM: 2012 Mb
Graphics Card: Intel(R) G45/G43 Express Chipset, 1024 Mb
Hard Drives: C: Total - 238378 MB, Free - 192662 MB;
Motherboard: Dell Inc., 0P301D, A00, ..CN736048AE02MA.
Antivirus: Microsoft Security Essentials, Updated: Yes, On-Demand Scanner: Enabled

Here are my WhoCrashed results:
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: D32K5JC1
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel(R) Pentium(R) Dual CPU E2200 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2110693376 total
VM: 2147352576, free: 2025656320

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 8/15/2011 10:00:05 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini081511-01.dmp
This was probably caused by the following module: iastor.sys (iaStor+0x43220)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF88729E67, 0xFFFFFFFF8872A667, 0xB000500)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\iastor.sys
product: Intel Matrix Storage Manager driver
company: Intel Corporation
description: Intel Matrix Storage Manager driver - ia32
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iastor.sys (Intel Matrix Storage Manager driver - ia32, Intel Corporation).
Google query: iastor.sys Intel Corporation BAD_POOL_HEADER

On Sun 8/14/2011 11:44:44 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini081411-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1192CA)
Bugcheck code: 0x10000050 (0xFFFFFFFFE543545A, 0x0, 0xFFFFFFFF805F02CA, 0x1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Sun 8/14/2011 1:32:30 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini081311-02.dmp
This was probably caused by the following module: hal.dll (hal+0x2EF2)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF8896FA37, 0xFFFFFFFF88970237, 0x1B000300)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Sat 8/13/2011 11:22:06 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini081311-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x6BB)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF88F56F37, 0xFFFFFFFF88F57737, 0x1B000300)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Fri 8/12/2011 7:43:53 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini081211-01.dmp
This was probably caused by the following module: hal.dll (hal+0x2EF2)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF88D8DC7F, 0xFFFFFFFF88D8E47F, 0x1B000163)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Thu 8/11/2011 4:30:43 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini081111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1192CA)
Bugcheck code: 0x10000050 (0xFFFFFFFFE5935835, 0x0, 0xFFFFFFFF805F02CA, 0x1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Wed 8/10/2011 12:36:08 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini080911-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1192CA)
Bugcheck code: 0x10000050 (0xFFFFFFFFE8155B5D, 0x0, 0xFFFFFFFF805F02CA, 0x1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Tue 8/9/2011 7:26:29 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini080911-01.dmp
This was probably caused by the following module: idsxpx86.sys (IDSxpx86+0x24FB0)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF885DFCC7, 0xFFFFFFFF885E04C7, 0xB0003E5)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: idsxpx86.sys .
Google query: idsxpx86.sys BAD_POOL_HEADER

On Sun 8/7/2011 1:10:10 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini080611-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1192CA)
Bugcheck code: 0x10000050 (0xFFFFFFFFE88E6B60, 0x0, 0xFFFFFFFF805F02CA, 0x1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Sat 8/6/2011 9:09:44 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini080611-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x638C)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF87BBA3D7, 0xFFFFFFFF87BBABD7, 0xB000143)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Fri 2/25/2011 5:10:30 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini022511-01.dmp
This was probably caused by the following module: rtkhdaud.sys (RtkHDAud+0x4FA74)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000093, 0xFFFFFFFFA850CA71, 0xFFFFFFFFA6CBBA50, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\rtkhdaud.sys
product: Realtek(r) High Definition Audio Function Driver (HRTF data Copyright 1994 by MIT Media Lab)
company: Realtek Semiconductor Corp.
description: Realtek(r) High Definition Audio Function Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rtkhdaud.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.).
Google query: rtkhdaud.sys Realtek Semiconductor Corp. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
11 crash dumps have been found and analyzed. 3 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

rtkhdaud.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.)

iastor.sys (Intel Matrix Storage Manager driver - ia32, Intel Corporation)

idsxpx86.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

More about : constant bsods

August 18, 2011 8:38:47 AM

mspm said:
Hi all,

Praying that someone can help this newbie. :help: My Dell Vostro 220 has been working fine until 8/6 - when I started getting these BSODs. I haven't installed any new hardware or software. But I'm still running Win XP Pro SP-3, and I think my problems began after running the last Windows Update. I've tried: deleting my NAV and any unecessary programs; updating the drivers that I could - at Windows Update & Dell; total check with TuneUp Utilities; trying to system restore. Still, my PC crashes every time it goes into sleep mode.

I did see an error message in Device Manager for the DVD/CD-ROM drive (that I don't even use). I couldn't install the driver (which seems to be very old) from Dell.com. Uninstalling the driver didn't work. The Even Viewer shows warnings about Microsoft Fax failure, but I don't have an internal fax.

The last time I called Dell, I got someone in India who didn't seem to know much more than I did. I'm totally confused at this point, but I am attaching the WhoCrashed report in hopes that someone can tell my specifically what is wrong. Thank you!!!!

Here is my system info:
Tech Support Guy System Info Utility version 1.0.0.1
OS Version: Microsoft Windows XP Professional, Service Pack 3, 32 bit
Processor: Intel(R) Pentium(R) Dual CPU E2200 @ 2.20GHz, x86 Family 6 Model 15 Stepping 13
Processor Count: 2
RAM: 2012 Mb
Graphics Card: Intel(R) G45/G43 Express Chipset, 1024 Mb
Hard Drives: C: Total - 238378 MB, Free - 192662 MB;
Motherboard: Dell Inc., 0P301D, A00, ..CN736048AE02MA.
Antivirus: Microsoft Security Essentials, Updated: Yes, On-Demand Scanner: Enabled

Here are my WhoCrashed results:
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: D32K5JC1
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel(R) Pentium(R) Dual CPU E2200 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2110693376 total
VM: 2147352576, free: 2025656320

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 8/15/2011 10:00:05 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini081511-01.dmp
This was probably caused by the following module: iastor.sys (iaStor+0x43220)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF88729E67, 0xFFFFFFFF8872A667, 0xB000500)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\iastor.sys
product: Intel Matrix Storage Manager driver
company: Intel Corporation
description: Intel Matrix Storage Manager driver - ia32
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iastor.sys (Intel Matrix Storage Manager driver - ia32, Intel Corporation).
Google query: iastor.sys Intel Corporation BAD_POOL_HEADER

On Sun 8/14/2011 11:44:44 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini081411-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1192CA)
Bugcheck code: 0x10000050 (0xFFFFFFFFE543545A, 0x0, 0xFFFFFFFF805F02CA, 0x1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Sun 8/14/2011 1:32:30 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini081311-02.dmp
This was probably caused by the following module: hal.dll (hal+0x2EF2)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF8896FA37, 0xFFFFFFFF88970237, 0x1B000300)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Sat 8/13/2011 11:22:06 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini081311-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x6BB)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF88F56F37, 0xFFFFFFFF88F57737, 0x1B000300)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Fri 8/12/2011 7:43:53 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini081211-01.dmp
This was probably caused by the following module: hal.dll (hal+0x2EF2)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF88D8DC7F, 0xFFFFFFFF88D8E47F, 0x1B000163)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Thu 8/11/2011 4:30:43 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini081111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1192CA)
Bugcheck code: 0x10000050 (0xFFFFFFFFE5935835, 0x0, 0xFFFFFFFF805F02CA, 0x1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Wed 8/10/2011 12:36:08 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini080911-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1192CA)
Bugcheck code: 0x10000050 (0xFFFFFFFFE8155B5D, 0x0, 0xFFFFFFFF805F02CA, 0x1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Tue 8/9/2011 7:26:29 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini080911-01.dmp
This was probably caused by the following module: idsxpx86.sys (IDSxpx86+0x24FB0)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF885DFCC7, 0xFFFFFFFF885E04C7, 0xB0003E5)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: idsxpx86.sys .
Google query: idsxpx86.sys BAD_POOL_HEADER

On Sun 8/7/2011 1:10:10 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini080611-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1192CA)
Bugcheck code: 0x10000050 (0xFFFFFFFFE88E6B60, 0x0, 0xFFFFFFFF805F02CA, 0x1)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Sat 8/6/2011 9:09:44 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini080611-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x638C)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF87BBA3D7, 0xFFFFFFFF87BBABD7, 0xB000143)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

On Fri 2/25/2011 5:10:30 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini022511-01.dmp
This was probably caused by the following module: rtkhdaud.sys (RtkHDAud+0x4FA74)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000093, 0xFFFFFFFFA850CA71, 0xFFFFFFFFA6CBBA50, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\rtkhdaud.sys
product: Realtek(r) High Definition Audio Function Driver (HRTF data Copyright 1994 by MIT Media Lab)
company: Realtek Semiconductor Corp.
description: Realtek(r) High Definition Audio Function Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rtkhdaud.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.).
Google query: rtkhdaud.sys Realtek Semiconductor Corp. KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
11 crash dumps have been found and analyzed. 3 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

rtkhdaud.sys (Realtek(r) High Definition Audio Function Driver, Realtek Semiconductor Corp.)

iastor.sys (Intel Matrix Storage Manager driver - ia32, Intel Corporation)

idsxpx86.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

m
0
l
August 18, 2011 8:42:41 AM

Suggest you do a search for blue screen analyzer and see if any of those will help you.
m
0
l
!