Error Code 0x0000009F BSOD

[fatwalrus]

Hi, I recently upgraded from XP to Windows 7 Pro 32-bit. I have been getting many BSOD for a while now, and particularly when I have been surfing the internet. The system shuts off and reboots at random times. I also installed some RAM when I upgraded, so this may be the problem, but I am not sure. I have my minidump folder attached to my post. If anyone could help me diagnose my problem that would help very much.

ECCode: 0x0000009F

Thanks in advance!

EDIT: I cannot upload my .zip file, any help on this?

 

[usasma]

STOP 0x9F error info: BSOD Index

If the minidump folder is too large, you can zip up the last 10 to 20 minidumps and then upload them here.
Or, you can upload the entire batch to a free file hosting site and post the link to it here so we can download it.

 

[fatwalrus]

Here are the files attached below. Thanks for the help.

 

[usasma]

Looks like a problem with your Avast program. Please do the following:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Avast from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Avast using this free tool: http://www.avast.com/eng/avast-uninstall-utility.html
- IMMEDIATELY install and update the free antivirus
- check to see if this fixes the BSOD's

Summary of the BSOD's:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 23 19:41:12.783 2010 (GMT-4)
System Uptime: 0 days 0:00:09.812
BugCheck 124, {0, fffffa8004aff8f8, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 23 19:37:42.190 2010 (GMT-4)
System Uptime: 0 days 0:00:09.829
BugCheck 124, {0, fffffa8004e07468, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 21 23:14:55.604 2010 (GMT-4)
System Uptime: 0 days 0:00:14.648
BugCheck C9, {23b, fffff88001802818, fffff980090c8dc0, 0}
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )
BUGCHECK_STR:  0xc9_23b
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 21 19:54:31.487 2010 (GMT-4)
System Uptime: 0 days 0:00:09.500
BugCheck 124, {0, fffffa80049548f8, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu May 20 16:47:33.662 2010 (GMT-4)
System Uptime: 0 days 0:00:07.675
BugCheck 124, {0, fffffa800497c8f8, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 17 10:12:05.551 2010 (GMT-4)
System Uptime: 0 days 0:00:09.190
BugCheck 124, {0, fffffa8004e1f038, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May 15 18:06:44.206 2010 (GMT-4)
System Uptime: 0 days 0:00:09.860
BugCheck 124, {0, fffffa800515c268, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 14 20:40:53.582 2010 (GMT-4)
System Uptime: 0 days 0:00:08.626
BugCheck 124, {0, fffffa8005137038, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 14 16:31:37.270 2010 (GMT-4)
System Uptime: 0 days 0:00:08.314
BugCheck 124, {0, fffffa8004c958f8, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 14 15:57:07.144 2010 (GMT-4)
System Uptime: 0 days 0:00:09.798
BugCheck 124, {0, fffffa800509b8f8, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 14 11:34:36.535 2010 (GMT-4)
System Uptime: 0 days 0:00:08.580
BugCheck 124, {0, fffffa8004c5b8f8, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Apr 22 15:33:33.034 2010 (GMT-4)
System Uptime: 0 days 0:00:09.079
BugCheck 124, {0, fffffa8004c528f8, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Apr 16 19:54:55.740 2010 (GMT-4)
System Uptime: 0 days 0:00:07.784
BugCheck 124, {0, fffffa8004ca08f8, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Apr 12 22:23:33.348 2010 (GMT-4)
System Uptime: 0 days 0:00:08.392
BugCheck A, {0, 2, 1, fffff800032d1a13}
*** WARNING: Unable to verify timestamp for aswNdis2.sys
*** ERROR: Module load completed but symbols could not be loaded for aswNdis2.sys
Probably caused by : aswNdis2.sys ( aswNdis2+62aa )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Apr  1 18:19:23.332 2010 (GMT-4)
System Uptime: 0 days 0:00:08.987
BugCheck 124, {0, fffffa8004c848f8, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Apr  1 17:36:53.083 2010 (GMT-4)
System Uptime: 0 days 0:00:08.127
BugCheck 124, {0, fffffa8004cbe8f8, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Apr  1 17:29:20.849 2010 (GMT-4)
System Uptime: 0 days 0:00:08.503
BugCheck 124, {0, fffffa8004cbe8f8, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Mar 26 22:45:44.662 2010 (GMT-4)
System Uptime: 0 days 0:00:08.316
BugCheck 124, {0, fffffa8004c958f8, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Mar 26 22:38:17.490 2010 (GMT-4)
System Uptime: 0 days 0:00:07.534
BugCheck 124, {0, fffffa8004c988f8, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Mar 26 22:32:32.098 2010 (GMT-4)
System Uptime: 0 days 0:00:08.143
BugCheck 124, {0, fffffa8004cd58f8, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System

 

[fatwalrus]

What is my avast program? Is that my anti-virus software?

And I have discovered that I need to be running Windows 7 64-bit if I am to be using 4GB of RAM or more. I am using 4GB yet I am running the 32-bit system...maybe this is the problem?

 

[usasma]

Avast is your antivirus program.

No, the 4gB of RAM isn't causing this.
More info on the 4gB Physical Memory (RAM) limit situation here: The 4gB Memory Limit
Windows will only recognize the 4gB - even if you have much more installed.

It's the issues with the STOP 0x124 error that are your problem now - and that's either a hardware problem or a compatibility problem. Have a look at this post for suggested solutions for the STOP 0x124 error: http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

 

[fatwalrus]

So the cause of my BSOD is my anti-virus program instead of hardware?

Could I just manually remove one of the slots of RAM in my machine and see which one causes the STOP error? Assuming the antivirus program is not the problem.

 

[zigzag3143]

Hi, I recently upgraded from XP to Windows 7 Pro 32-bit. I have been getting many BSOD for a while now, and particularly when I have been surfing the internet. The system shuts off and reboots at random times. I also installed some RAM when I upgraded, so this may be the problem, but I am not sure. I have my minidump folder attached to my post. If anyone could help me diagnose my problem that would help very much.

ECCode: 0x0000009F

Thanks in advance!

EDIT: I cannot upload my .zip file, any help on this?

How big is it??? use these to help you upload it. http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html. if it is too big you can upload it to a service like rapidshare and put a link in your post

Thanks

Ken

 

[usasma]

No, we don't know the cause yet. The antivirus program is one possible cause - and removing it will remove one thing from the list of suspects. Then we'll wait for more BSOD's and see what they tell us.

 

[fatwalrus]

Did not uninstall anti-virus program yet, but I have now received another error, one related to Kernal Memory apparently. Are you sure this doesn't have to do anything with RAM or even my videocard? Or motherboard? I'm no techy so I don't know, file is attached to this post

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: 1000008e
BCP1: C000001D
BCP2: 95A1140B
BCP3: 9D15FA58
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\052810-19453-01.dmp
C:\Users\Chris\AppData\Local\Temp\WER-42562-0.sysdata.xml
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[ickymay]

Did not uninstall anti-virus program yet, but I have now received another error, one related to Kernal Memory apparently. Are you sure this doesn't have to do anything with RAM or even my videocard? Or motherboard? I'm no techy so I don't know, file is attached to this post

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: 1000008e
BCP1: C000001D
BCP2: 95A1140B
BCP3: 9D15FA58
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\052810-19453-01.dmp
C:\Users\Chris\AppData\Local\Temp\WER-42562-0.sysdata.xml
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

unninstall avast as usasma advises and replace with MSE for debugging purposes

 

[usasma]

No, we are not sure yet. Dump files often only give hints as to the problem - not an exact diagnosis.

There is not much different with this error message, but there is one difference that stands out.

The debugger states that it cannot locate symbols for win32k.sys. This is a Microsoft file, and I've located the symbols for this file in numerous different memory dumps for at least the last 6 months or so.

The possibilities are (IMO):
- an infection (try the scans here: Malware (read the details at the link)
- a corruption of Windows: run SFC.EXE /SCANNOW according to these instructions:

SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.

- lapsed/error in the Windows Activation process: Go to Start and type in "activate" (without the quotes) and press Enter. Follow the instructions there.
- a hacked/pirated copy of Windows - I suggest getting a legal copy of Windows

Summary of the BSOD:

Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sat May 29 02:11:10.558 2010 (GMT-4)
System Uptime: 0 days 3:47:39.324
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
BugCheck 1000008E, {c000001d, 95a1140b, 9d15fa58, 0}
Probably caused by : win32k.sys ( win32k+b140b )
BUGCHECK_STR:  0x8E
PROCESS_NAME:  explorer.exe