BSOD error 1000009f doing basic stuff

[kkaylium]

Hello,
I've only had my laptop a few months and in the past 2-3 months i have been having BSOD errors once and a while when closing the lid to turn it to sleep mode. :sarc:
I uninstalled a few things and it seemed to be fixed, but I just had another this morning and I can't find the same error on here anywhere (I'm guessing I missed it)
anyway, here is the info that was in the "windows has recovered from an unexpected shutdown" window:

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

Additional information about the problem:
BCCode: 1000009f
BCP1: 0000000000000004
BCP2: 0000000000000258
BCP3: FFFFFA8006D15B50
BCP4: FFFFF80000B9C3D0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

I can't remember the other errors, but they were all BlueScreen as well.
I also have a dual boot with ubuntu, if that makes any difference. I will post my minidump files and such in a min.

Any help is greatly appreciated!

Thanks,
Kkaylium

 

[kkaylium]

Here are the minidump files (I think I had more crashes than this, I don't know what happened to those files, but here are the 4 most recent):

http://sdrv.ms/QNOZLW

edit: and here is the SF Diagnostic zip file (kkaylium.zip

 

[koolkat77]

Welcome

All your dumps show memory corruption.

Start with running memtest86+ on each stick for 8 passes preferably overnight, find out the fault one:
:ar: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Let us know the results

*******************************************************************************
*                                                                             *
*                        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]

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

 

[koolkat77]

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

 

[kkaylium]

I looked at the minidump files with windows debugger and it doesn't say anything about memory corruption. It says something like driver power failed. I am now really confused because I looked at the same minidump files as i uploaded on here. Also, some of the crashes are self induced because opening the lid and pressing the space bar won't always wake it up. so i've had to hold down the power button to turn off and back on. Sometimes I willl get a blueScreen popup when I get back to windows, sometimes not.
I haven't run any more memtest yet, because I had to run a virus scan last night instead (which showed nothing)

 

[koolkat77]

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.

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.

 

[Vir Gnarus]

Huh? I'm not sure what crashdump you opened, Koolkat, but I'm not seeing any memory_corruption errors in any of the dumps I opened (the four present).

Anyways, minidumps don't look to hold the info we seek here. Either turn on Driver Verifier and let it crash a couple more times and send us those crashdumps, or send us the large MEMORY.DMP file in your Windows directory.

 

[koolkat77]

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.

 

[Vir Gnarus]

Did you make sure to setup symbols correctly for Windbg? That could cause it to spurt out false information.

 

[koolkat77]

Did you make sure to setup symbols correctly for Windbg? That could cause it to spurt out false information.

Yes, but I'll recheck

 

[kkaylium]

This is the info from the MEMORY.DMP file. If you need the file to look for something I missed, I can upload it.
koolkat, I wasn't trying to say i didn't want to run the memtest, but I just don't want to run it for a long time if that isn't the problem.
I am going to turn on the driver verifier.
Thanks,
kkaylium

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

Use !analyze -v to get detailed debugging information.

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

Implicit thread is now fffffa80`06d15b50
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8006d15b50, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c3d0, nt!TRIAGE_9F_PNP on Win7

Debugging Details:
------------------

Implicit thread is now fffffa80`06d15b50

DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  fffffa8006d15b50

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002ccabd2 to fffff80002cd807a

STACK_TEXT:  
fffff880`031a1440 fffff800`02ccabd2 : fffffa80`06d15b50 fffffa80`06d15b50 00000000`00000000 00000000`0000000d : nt!KiSwapContext+0x7a
fffff880`031a1580 fffff800`02cd76da : fffffa80`0a46ffa0 00000000`00000000 ffffffff`00000000 00000000`a0000003 : nt!KiCommitThreadWait+0x1d2
fffff880`031a1610 fffff800`02f3afe4 : 00000000`00000003 fffff880`031a1928 00000000`00000001 fffffa80`00000000 : nt!KeWaitForMultipleObjects+0x272
fffff880`031a18d0 fffff800`03070c19 : 00000000`00000000 fffffa80`0f5c66d0 fffff8a0`036463a0 00000000`00000000 : nt!PnpNotifyUserMode+0x158
fffff880`031a1950 fffff800`0314bc81 : 00000000`00000000 00000000`00000000 fffff8a0`036463a0 fffff8a0`036463a0 : nt!PnpNotifyUserModeDeviceRemoval+0x49
fffff880`031a19a0 fffff800`0314c3bc : fffff880`031a1b78 fffffa80`0e6eae00 fffffa80`06d15b00 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0xb51
fffff880`031a1ae0 fffff800`0303564e : 00000000`00000000 fffffa80`0e6eae90 fffff8a0`036463a0 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`031a1b10 fffff800`02cde841 : fffff800`02f3a760 fffff8a0`036463a0 fffff800`02e722d8 fffff800`02e816c0 : nt! ?? ::NNGAKEGL::`string'+0x5ab8b
fffff880`031a1b70 fffff800`02f6be6a : 00000000`00000000 fffffa80`06d15b50 00000000`00000080 fffffa80`06cffb30 : nt!ExpWorkerThread+0x111
fffff880`031a1c00 fffff800`02cc5ec6 : fffff880`02fd7180 fffffa80`06d15b50 fffff880`02fe1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a1c40 00000000`00000000 : fffff880`031a2000 fffff880`0319c000 fffff880`031a1470 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .thread 0xfffffa8006d15b50 ; kb

FOLLOWUP_IP: 
nt!KiSwapContext+7a
fffff800`02cd807a 488d8c2400010000 lea     rcx,[rsp+100h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiSwapContext+7a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3

FAILURE_BUCKET_ID:  X64_0x9F_4_nt!KiSwapContext+7a

BUCKET_ID:  X64_0x9F_4_nt!KiSwapContext+7a

Followup: MachineOwner
---------

0: kd> lmvm nt
start             end                 module name
fffff800`02c56000 fffff800`0323e000   nt         (pdb symbols)          C:\ProgramData\dbg\sym\ntkrnlmp.pdb\ABD176D2C7AE41B88BBF2837A09A462C2\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Timestamp:        Fri May 04 02:18:59 2012 (4FA390F3)
    CheckSum:         00555F80
    ImageSize:        005E8000
    File version:     6.1.7601.17835
    Product version:  6.1.7601.17835
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ntkrnlmp.exe
    OriginalFilename: ntkrnlmp.exe
    ProductVersion:   6.1.7601.17835
    FileVersion:      6.1.7601.17835 (win7sp1_gdr.120503-2030)
    FileDescription:  NT Kernel & System
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

 

[Vir Gnarus]

We'll need to whole file. You'll have to compress it and then upload to a 3rd-party filesharing site.

 

[kkaylium]

I'm Back (with more crashes)

Sorry I didn't reply for a long time. I didn't have any more bsod errors for quite a while. if fact, it was working fine, except that my internet would stop working. (wireless)
A few days ago i got another BSOD error showing the same error message. I opened the new minidump file and it is still DRIVER_POWER_STATE_FAILURE. The driver it is blaming is ntkrnlmp.exe, which i think is the same one as last time and that it isn't really the cause of the error? :sarc:I'm just about to run driver verifier for these recurring crashes and i'll send you anything i get.
Thanks!

 

[Vir Gnarus]

Yes, please do. Run DV and send us some crashdumps. If I need it, I'll request a kernel dump from you.

 

[kkaylium]

Here is the MEMORY.DMP file

Here is the MEMORY.DMP file you wanted: http://sdrv.ms/S0zzFL
And the new crash dump: http://sdrv.ms/SPdkRV
I hope something will come from driver verifier soon.

 

[Vir Gnarus]

Hi mate,

I went perusing through previous threads and found this one hasn't been resolved. I tried accessing skydrive but I don't have a microsoft account, nor bother to make one just for this. If you can upload it to a 3rd-party filesharing meta site like mirrorcreator.com that would be a lot more convenient for us techs.