W7 random BSOD`s

theraz · 06 Mar 2010

I started getting these in December 2009 and from then I have reinstalled windows 7 over and over again / switched memories / downgraded drivers / restored my system /updated drivers / ran a driver scanner and so on I am currently on a rather fresh install and in need of help.Keep getting these randomly when playing games or browsing or just idling:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
IRQL_NOT_LESS_OR_EQUAL
BAD_POOL_HEADER
MEMORY MANAGEMENT

Here are some minidumps:
RapidShare: 1-CLICK Web hosting - Easy Filehosting
or
minidump.rar

Thanks in advance !

usasma · 06 Mar 2010

12 memory dumps - from 27 Feb 10 to 06 Mar 10
2 STOP 0xA - more info on this error message here: BSOD Index
1 STOP 0x1A - more info on this error message here: BSOD Index
2 STOP 0x50 - more info on this error message here: BSOD Index
2 STOP 0xC5 - more info on this error message here: BSOD Index
2 STOP 0xD1 - more info on this error message here: BSOD Index
2 STOP 0x7E - more info on this error message here: BSOD Index
1 STOP 0x8E - more info on this error message here: BSOD Index

1 blames NETIO.SYS for the crash (a component of Windows networking), 1 blames peauth.sys (a core Windows component), 1 ntkrpamp.exe (kernel of the Windows Operating System), 6 ntkrnlpa.exe (kernel of the Windows Operating System, 1 Unknown_Image, 1 tcpip.sys, 1 hidusb.sys

This sort of pattern usually indicates a hardware problem (but see the note about ASACPI.SYS below). Based on the errors above, the most probably suspect is a USB networking device (but that's just a guess). If you have one of these, please remove it to see if that stops the BSOD's. If it's your only way of connecting to the web, please post back immediately with the make and model of it.

If that isn't the case, then please start with these free, bootable diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:

Code:

Rtnicxp.sys  Fri May 30 11:12:11 2008 - Realtek 10/100/1000 NDIS 5.1 Driver - http://www.carrona.org/dvrref.html#Rtnicxp.sys
ASACPI.sys   Thu Aug 12 22:52:52 2004 - NOTE:  This is a definite BSOD concern.  It's the Asus ATK0110 ACPI Utility driver and MUST be updated IMMEDIATELY - http://www.carrona.org/dvrref.html#ASACPI.sys

Also, there was a change to your system between 27 Feb 10 and 05 Mar 10.

27 Feb 10: Built by: 7600.16385.x86fre.win7_rtm.090713-1255
05 Mar 10: Built by: 7600.16481.x86fre.win7_gdr.091207-1941

This change was in the core operating system files and, as such, the Windows Debugging Tools aren't able to access symbols for your operating system files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.

Please do the following:
- activate/validate the Windows installation at Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds

Summary of the BSOD's:

Code:

Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat Feb 27 11:08:32.573 2010 (GMT-5)
System Uptime: 0 days 1:04:36.243
BugCheck C5, {a5886002, 2, 1, 82924581}
Probably caused by : NETIO.SYS ( NETIO!NetioDereferenceNetBufferListChain+ad )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat Feb 27 09:17:39.808 2010 (GMT-5)
System Uptime: 0 days 1:47:46.120
*** WARNING: Unable to verify timestamp for peauth.sys
*** ERROR: Module load completed but symbols could not be loaded for peauth.sys
BugCheck 1000008E, {c0000005, 8267c0f0, 8f144ae4, 0}
Probably caused by : peauth.sys ( peauth+4f1f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  audiodg.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat Feb 27 09:46:39.813 2010 (GMT-5)
System Uptime: 0 days 0:26:33.483
BugCheck A, {0, 2, 1, 828cc9de}
Probably caused by : ntkrpamp.exe ( nt!KiSetSystemAffinityThread+ff )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  opera.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Fri Mar  5 15:51:25.834 2010 (GMT-5)
System Uptime: 0 days 3:14:59.520
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Fri Mar  5 16:17:59.157 2010 (GMT-5)
System Uptime: 0 days 0:25:29.452
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck A, {14, 2, 0, 82ad56d1}
Probably caused by : ntkrnlpa.exe ( nt+946d1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Thu Mar  4 17:15:08.571 2010 (GMT-5)
System Uptime: 0 days 0:11:51.867
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck C5, {4, 2, 1, 82921067}
Probably caused by : ntkrnlpa.exe ( nt+120067 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Thu Mar  4 17:02:19.889 2010 (GMT-5)
System Uptime: 0 days 4:45:24.559
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck 1000007E, {c0000005, 0, 8db8be08, 8db8b9e0}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Sat Mar  6 06:06:50.201 2010 (GMT-5)
System Uptime: 0 days 2:55:18.887
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Sat Mar  6 13:19:12.159 2010 (GMT-5)
System Uptime: 0 days 1:00:05.455
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck D1, {89662049, 2, 1, 8c08b745}
Probably caused by : tcpip.sys ( tcpip!WfpAleFindRemoteEndpoint+b8 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Sat Mar  6 12:10:51.929 2010 (GMT-5)
System Uptime: 0 days 0:04:48.225
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Sat Mar  6 12:10:51.929 2010 (GMT-5)
System Uptime: 0 days 0:04:48.225
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Sat Mar  6 11:58:35.961 2010 (GMT-5)
System Uptime: 0 days 0:03:33.257
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BugCheck D1, {ff530000, 2, 8, ff530000}
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : hidusb.sys ( hidusb!HumReadReport+ef )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

theraz · 07 Mar 2010

Thanks a lot for replying to my post.Here`s what I`ve done so far:
*I have updated the drivers that you suggested along with everythink i could think of without using windows update.
*I ran HD diagnostic for my WDC WD2500KS-00 hard drive and it failed at the cable test so I went and checked the cables they were all good.
*I ran the memtest86 from a bootable cd and for some odd reason it didn`t start.
I am using this dual channel kit: Corsair Dominator 2 x2gb DDR2
*I ran the sfc /scannow and :Windows Resource Protection did not find any integrity violations.
*Also i ran a scan with my licensed NOD32 and it found nothing.
Since I`ve started my PC ( 2 hours ago ) I haven`t gotten any BSOD`s but for some months i keep getting corrupted archives and .cab errors when installing something or extracting so I suspect my hard drive for being faulty here and since I`m quite short on money I can`t afford a new one yet so if i keep getting BSOD`s I can gladly assume it`s from my hard drive and hopefully it will be replaced soon also what`s your personal opinion on Samsung hard drives ?