Share via

BSOD error, please help

Anonymous
2015-09-30T16:00:39+00:00

CACHE_MANAGER (34)

    See the comment for FAT_FILE_SYSTEM (0x23)

Arguments:

Arg1: 000000000000055f

Arg2: ffffffffc0000420

Arg3: 0000000000000000

Arg4: 0000000000000000

Debugging Details:

EXCEPTION_RECORD:  ffffffffc0000420 -- (.exr 0xffffffffc0000420)

Cannot read Exception record @ ffffffffc0000420

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x34

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80002d4b471 to fffff80002cd55c0

STACK_TEXT:  

fffff88009219508 fffff80002d4b471 : 0000000000000034 000000000000055f ffffffffc0000420 0000000000000000 : nt!KeBugCheckEx

fffff88009219510 fffff80002fbf952 : fffffa8000000000 0000000000070000 fffff880092195e0 fffff88009219670 : nt! ?? ::FNODOBFM::`string'+0x387bb

fffff880092195a0 fffff880016ef01f : fffff88000000000 0000000000000001 fffffa80086753f0 fffffa8003821f01 : nt!CcCopyRead+0x132

fffff88009219660 fffff8800155e098 : fffffa8003821f20 fffffa8008675388 0000000000120089 fffffa8003821f01 : Ntfs!NtfsCopyReadA+0x18f

fffff88009219840 fffff880015618ba : fffff88009219910 0000000006c00303 0000000006c00300 fffffa8003821f00 : fltmgr!FltpPerformFastIoCall+0x88

fffff880092198a0 fffff8800157f630 : fffffa8003821f20 0000000000000000 fffff88009219a00 0000000000002000 : fltmgr!FltpPassThroughFastIo+0xda

fffff880092198e0 fffff80002fbf4d9 : fffffa8003821f20 000007fe00000001 fffffa80036b5de0 fffffa8003821f20 : fltmgr!FltpFastIoRead+0x1d0

fffff88009219980 fffff80002cd4853 : 000000000000071c 0000000000000000 0000000000000000 0000000000000000 : nt!NtReadFile+0x417

fffff88009219a70 00000000770dda1a : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x13

0000000001cfce88 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x770dda1a

STACK_COMMAND:  kb

FOLLOWUP_IP: 

nt! ?? ::FNODOBFM::`string'+387bb

fffff800`02d4b471 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+387bb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  55afca65

IMAGE_VERSION:  6.1.7601.18939

FAILURE_BUCKET_ID:  X64_0x34_nt!_??_::FNODOBFM::_string_+387bb

BUCKET_ID:  X64_0x34_nt!_??_::FNODOBFM::_string_+387bb

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x34_nt!_??_::fnodobfm::_string_+387bb

FAILURE_ID_HASH:  {21bae3e1-dddb-3f2e-f55c-c50e52a31808}

Followup: MachineOwner

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2015-09-30T16:30:02+00:00

    We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here

    If you have any questions about the procedure please ask

    Was this answer helpful?

    0 comments