Received BSOD when flipping open laptop from sleep

[A600]

Last night I finished browsing and flipped down the laptop monitor, putting it to sleep. When I flipped open the monitor today the first thing I saw was a BSOD message. I haven't really noticed any unusual behavior other than this, except for one instance recently when I performed a similar task and noticed one of those memory access error messages on screen that looks something like x000000000017 and then some technical jargon. I can't remember if I clicked on the close tab for that or it disappeared on it's own, and I unfortunately didn't get a screen cap and lack the know-how on how to retrieve that log if there is one.

Here are my basic specs and the two zip files (perfmon log and the Windows_NT6_BSOD_jcgriff2 file)

- 64bit
- Windows 7 Home Premium
- OEM

- Hardware from 2010 or so
- Current OS installation a month or so old

 

[writhziden]

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


Loading Dump File [D:\Kingston\BSODDmpFiles\A600\Windows_NT6_BSOD_jcgriff2\042412-30810-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`03052650
Debug session time: Tue Apr 24 09:44:47.821 2012 (UTC - 6:00)
System Uptime: 4 days 11:25:35.491
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 23, {e0107, fffff8800311c7b8, fffff8800311c010, fffff80002e91a7c}

Probably caused by : fastfat.SYS ( fastfat!FatPerformVerify+92 )

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

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

FAT_FILE_SYSTEM (23)
    If you see FatExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000000e0107
Arg2: fffff8800311c7b8
Arg3: fffff8800311c010
Arg4: fffff80002e91a7c

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


EXCEPTION_RECORD:  fffff8800311c7b8 -- (.exr 0xfffff8800311c7b8)
ExceptionAddress: fffff80002e91a7c (nt!KeWaitForSingleObject+0x000000000000017c)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800311c010 -- (.cxr 0xfffff8800311c010)
rax=001500000060f110 rbx=0000000000000000 rcx=fffffa80059b8720
rdx=0000000000000000 rsi=fffffa80059b8718 rdi=fffffa8001847940
rip=fffff80002e91a7c rsp=fffff8800311c9f0 rbp=0000000000000000
 r8=fffff78000000008  r9=0000000000000000 r10=0000000000000000
r11=fffff80002fffe80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=fffffa8001847a48
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!KeWaitForSingleObject+0x17c:
fffff800`02e91a7c 4c8938          mov     qword ptr [rax],r15 ds:002b:00150000`0060f110=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bc100
 ffffffffffffffff 

FOLLOWUP_IP: 
fastfat!FatPerformVerify+92
fffff880`04fb4ad2 8bd8            mov     ebx,eax

FAULTING_IP: 
nt!KeWaitForSingleObject+17c
fffff800`02e91a7c 4c8938          mov     qword ptr [rax],r15

BUGCHECK_STR:  0x23

LAST_CONTROL_TRANSFER:  from fffff800032791b0 to fffff80002e91a7c

STACK_TEXT:  
fffff880`0311c9f0 fffff800`032791b0 : fffff8a0`02bad000 fffff8a0`00000000 fffff800`0302a200 00000000`00000000 : nt!KeWaitForSingleObject+0x17c
fffff880`0311ca90 fffff880`04fb4ad2 : 00000000`00000000 fffffa80`059b8600 fffffa80`06589b10 fffff8a0`028e6e00 : nt!IoVerifyVolume+0x30
fffff880`0311cb20 fffff880`04fa57f1 : fffffa80`019b8010 fffffa80`097a73c0 00000000`00000005 fffffa80`08c7cf20 : fastfat!FatPerformVerify+0x92
fffff880`0311cb90 fffff880`04faeee4 : fffffa80`019b8010 fffffa80`097a73c0 00000000`80000016 00000000`00000001 : fastfat!FatProcessException+0x2f1
fffff880`0311cbf0 fffff800`02e94361 : fffff880`02f0ce00 fffffa80`019b8010 fffff880`02f36200 fffff8a0`00000005 : fastfat!FatFspDispatch+0x2d4
fffff880`0311cc70 fffff800`03124fda : 00000000`00000000 fffffa80`01847940 00000000`00000080 fffffa80`017da6f0 : nt!ExpWorkerThread+0x111
fffff880`0311cd00 fffff800`02e7b9c6 : fffff800`02fffe80 fffffa80`01847940 fffffa80`018326e0 fffff8a0`083e14f8 : nt!PspSystemThreadStartup+0x5a
fffff880`0311cd40 00000000`00000000 : fffff880`0311d000 fffff880`03117000 fffff880`0311b5d0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  fastfat!FatPerformVerify+92

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fastfat

IMAGE_NAME:  fastfat.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc1f0

STACK_COMMAND:  .cxr 0xfffff8800311c010 ; kb

FAILURE_BUCKET_ID:  X64_0x23_fastfat!FatPerformVerify+92

BUCKET_ID:  X64_0x23_fastfat!FatPerformVerify+92

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

The above crash was caused by the Windows Fast FAT File System Driver. Check your system for corruption.

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.