Random BSOD crashes...error code 0x0000009f

Hello,

I've been having BSOD crashes for some time now and haven't been able to attribute them to any particular action. They sometimes occur when the computer is just sitting idle.

System Specs
Windows 7 Home Premium 64-bit
Original OS (OEM)
Hardware age: 2 yrs
OS Installation age: 2 yrs (never reinstalled)

According to BlueScreenView, almost all of the crashes have been caused by driver "ntoskrnl.exe", with one instance being caused by "atikmdag.sys". I'm a novice at this so I don't know how to go about fixing the problem. Any assistance would be appreciated.

An example of the typical error information is below and the performance monitor zip file is attached. The zipped Windows_NT6_BSOD_jcgriff2 folder was still too large to attach (10 MB). Is there any way to make it smaller (note: there are 50 dmp files)?

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8003D2A060
BCP3: FFFFF80000B9C4D8
BCP4: FFFFFA8004510370
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\020912-25303-01.dmp
C:\Users\Esi\AppData\Local\Temp\WER-83569-0.sysdata.xml

No DMP files included in upload

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Many thanks for the reply. Here's a link to the zipped "Windows_NT6_BSOD_jcgriff2" folder.

http://www.mediafire.com/download.php?79wechh3hwwzj2u

egt said:

Many thanks for the reply. Here's a link to the zipped "Windows_NT6_BSOD_jcgriff2" folder.

http://www.mediafire.com/download.php?79wechh3hwwzj2u

Virtually all of these are related to a driver causing an inconsistent power state. Please run these two tests to find out which



These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Hi zigzag,

I ran Memtest86+ and after 10 passes, zero errors were found.

I then tried Driver Verifier a few times, but every time I restart my computer, it won't boot past the Windows logo. The screen goes black, with only the mouse cursor arrow being visible. I eventually have to hit the power button to force a shut down. I checked the dump folder and there weren't any new dmp files. On a side note, the computer is able to start in Safe Mode while Driver Verifier is running.

Is there anything else I can do to get the verifier to work?

egt said:

Hi zigzag,

I ran Memtest86+ and after 10 passes, zero errors were found.

I then tried Driver Verifier a few times, but every time I restart my computer, it won't boot past the Windows logo. The screen goes black, with only the mouse cursor arrow being visible. I eventually have to hit the power button to force a shut down. I checked the dump folder and there weren't any new dmp files. On a side note, the computer is able to start in Safe Mode while Driver Verifier is running.

Is there anything else I can do to get the verifier to work?

What drivers are you verifying?

I selected all of the drivers not associated with Microsoft. I've attached screen captures of the list of drivers in Driver Verifier.