BSOD error 1000009f doing basic stuff

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

Code:

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

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

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? I'm just about to run driver verifier for these recurring crashes and i'll send you anything i get.
Thanks!

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

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.

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.