BSOD while moving between desktop folders, error 0x0000009F

Thank you for starting your own thread. :)

Your .dmp files are all dated May or June of 2011. If your system clock is not set correctly, it can cause system instability. Rectify this first.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [K:\Kingston\BSODDmpFiles\poseiden79\Windows_NT6_BSOD_jcgriff2\062611-22276-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`0300d000 PsLoadedModuleList = 0xfffff800`03252650
Debug session time: Sun Jun 26 07:42:57.644 2011 (GMT-7)
System Uptime: 0 days 0:10:37.361
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8006cd6a10, fffff80000b9c518, fffffa80083d8640}

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

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8006cd6a10, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa80083d8640, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa80083d8640

DEVICE_OBJECT: fffffa8008671050

DRIVER_OBJECT: fffffa800865bb50

IMAGE_NAME:  nvmf6264.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c63defe

MODULE_NAME: nvmf6264

FAULTING_MODULE: fffff88004a81000 nvmf6264

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800030f99c2 to fffff8000308cd00

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`030f99c2 : 00000000`0000009f 00000000`00000003 fffffa80`06cd6a10 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`03098652 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c570 fffff800`030984f6 : fffffa80`6e076168 fffffa80`6e076168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`030983de : 00000001`7be5a1b0 fffff800`00b9cc58 00000000`00009f98 fffff800`03203588 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`030981c7 : 00000000`4dfca6c3 00000000`00009f98 00000000`4dfca6ae 00000000`00000098 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`03084a2a : fffff800`031ffe80 fffff800`0320dcc0 00000000`00000000 fffff800`0313b7b0 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_nvmf6264.sys

BUCKET_ID:  X64_0x9F_IMAGE_nvmf6264.sys

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

Your network adapter driver is causing the power state failure; update your network adapter drivers using the following method.

1. Click Start Menu
2. Right Click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left
5. Find the device you are trying to uninstall by expanding the appropriate set of devices
6. Right click the device
7. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
8. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer
10. Install the latest driver for the device once Windows starts.

Alternatively:

1. Login as an adminstrative user.
2. Click Start Menu
3. Click Control Panel
4. Click Hardware and Sound
5. Click Device Manager (the last link under Devices and Printers)
6. Find the device you are trying to uninstall by expanding the appropriate set of devices
7. Right click the device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
10. Restart your computer
11. Install the latest driver for the device once Windows starts.

I noticed my time was incorrect. I have fixed the time and I will make the change to the driver and then let the computer sit. Thanks. I will reply back later today with a result.

Thank you much writhziden. So far since I made the driver change, I have been running without issues. Hopefully this is fixed. I will post back if another blue screen comes up. Hopefully not.

That's good news. Good luck!