BSOD error 1000009f doing basic stuff

Welcome

All your dumps show memory corruption.

Start with running memtest86+ on each stick for 8 passes preferably overnight, find out the fault one:
RAM - Test with Memtest86+

Let us know the results

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa8006d15b50, fffff80000b9c3d0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption

kkaylium said:

I have only had time to run one pass so far, and it brought up no errors, before I did the memtest, I got another unexpected shutdown black screen with the options to boot windows in safe mode, normally, etc. I just choose normal and when i signed in the normal popup window with the crash info didn't show up, and i didn't get a new minidump file.
Also, i think these crashes started after i installed tekkit minecraft and tekkit has been causing me problems like loosing internet connection, and saying java doesn't have enough memory to run (i have 8 gb ram). I tried to give tekkit more allocated memory, but i'm thinking i might have done it wrong and that might me contributing to the errors. what do you think?
I'll run some more memtest tonight or tomorrow.
I also am thinking of uninstalling tekkit and see what happens. Will it make any difference?
Thanks
-Kkaylium

Thanks for the update. Sure go ahead and uninstall it. See if the issue persists..
There are some software/apps that can irritate the memory.

Take 7 more passes to make sure nothing is wrong with your ram.

Good luck :)

If you don't want to do the memtest that's your wish.

To rule out buggy drivers we can enable driver verifier.

Driver Verifier

I'd suggest that you first backup your data 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/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in verifier 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 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 (an estimate on my part).

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.
Driver Verifier - Enable and Disable

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Capt.Jack Sparrow said:

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

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.

I am leaving this thread to the hands of a senior analyst.

Thanks Vir for coming to the thread.

I'm not sure which I opened but as far as I downloaded the second zip file from post #2. I probably made a mistake somewhere.

Anyway, thanks again.