BSOD Help

[dramaking]

I have encountered BSOD many times and I am not sure what has caused this. Can someone please check the minidump files for me since I do not know how to read them myself.
Thanks in advance.

 

[zigzag3143]

I have encountered BSOD many times and I am not sure what has caused this. Can someone please check the minidump files for me since I do not know how to read them myself.
Thanks in advance.

hi and welcome


I took a quick look at the four dumps. They are pretty similar. They all show memory problems affecting the file system

I would
download and run memtestx86 and run it for hours (preferably over night)
Run a system file check by typing cmd in search>rightclick and run as admin
SFC /SCANNOW

If you are overclocking stop


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


Loading Dump File [C:\Users\K\Desktop\111409-21996-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8284c000 PsLoadedModuleList = 0x82994810
Debug session time: Sat Nov 14 10:33:53.737 2009 (GMT-5)
System Uptime: 0 days 0:45:32.594
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
1: kd> !lanalyze -v
No export lanalyze found
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter 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: 001904fb
Arg2: 99b2ba78
Arg3: 99b2b650
Arg4: 8288a85e

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


EXCEPTION_RECORD: 99b2ba78 -- (.exr 0xffffffff99b2ba78)
ExceptionAddress: 8288a85e (nt!memcpy+0x000000be)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 068ad123
Attempt to write to address 068ad123

CONTEXT: 99b2b650 -- (.cxr 0xffffffff99b2b650)
eax=00000000 ebx=0000144f ecx=00000000 edx=00000002 esi=974eef7c edi=a6628ad4
eip=8288a85e esp=99b2bb40 ebp=99b2bb4c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!memcpy+0xbe:
8288a85e 829023d18a0688 adc byte ptr [eax+68AD123h],88h ds:0023:068ad123=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

PROCESS_NAME: Gunz.exe

CURRENT_IRQL: 0

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: 00000001

EXCEPTION_PARAMETER2: 068ad123

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 829b4718
Unable to read MiSystemVaType memory at 82994160
068ad123

FOLLOWUP_IP:
nt!memcpy+be
8288a85e 829023d18a0688 adc byte ptr [eax+68AD123h],88h

FAULTING_IP:
nt!memcpy+be
8288a85e 829023d18a0688 adc byte ptr [eax+68AD123h],88h

BUGCHECK_STR: 0x24

LAST_CONTROL_TRANSFER: from 8a89dd21 to 8288a85e

STACK_TEXT:
99b2bb4c 8a89dd21 a6628aa2 974eef4a 00000034 nt!memcpy+0xbe
99b2bba4 8a89e65b 850049e8 85ef9b48 00000008 Ntfs!NtfsFindPrefixHashEntry+0x389
99b2bc00 8a8a0c5c 850049e8 87385658 8b78b868 Ntfs!NtfsFindStartingNode+0x7b6
99b2bcdc 8a827210 850049e8 87385658 a46ab344 Ntfs!NtfsCommonCreate+0x65f
99b2bd1c 828bc10e a46ab2dc 00000000 ffffffff Ntfs!NtfsCommonCreateCallout+0x20
99b2bd1c 828bc205 a46ab2dc 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x15a
a46ab240 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31


CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
4 errors : !nt (8288a848-8288a878)
8288a840 88 07 8a 46 01 c1 e9 02 *12 47 01 83 c6 02 83 c7 ...F.....G......
8288a850 02 83 f9 08 72 a6 f3 a5 *50 24 95 ec a8 88 82 90 ....r...P$......
8288a860 23 d1 8a 06 88 07 83 c6 *e8 c1 e9 02 83 c7 01 83 #...............
8288a870 f9 08 72 88 f3 a5 ff 24 *00 ec a8 88 82 8d 49 00 ..r....$......I.

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: STRIDE

STACK_COMMAND: .cxr 0xffffffff99b2b650 ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE

BUCKET_ID: MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

Hope this helps

Ken J++