Hi all.
I have had several problems with my new rig, and now they are back. I am getting random BSOD's with various error codes. I have tried changing my gfx board, tried changing ram, triedf changing sounboards. I have also tried reinstalling and tried removing/changing mouse and keyboard. The only things remaining that I have not vhanged, are the CPU, PSU, mobo and HD.
Have run memtest86 without problems overnight, chkdisk, and also have run prime95 (and a gfx intensive test program at the same time) for several hours without problems. Also updated BIOS and all drivers.
So I thought that my problems dissapeared when I reinstalled Win7 some weeks ago, but now they seem to have returned.
Attaching dump files, I have no idea how to analyze them myself, so hopefully you can make something out of it.
EDIT: I am running a win7 proffessional 64bit OS
I hate to tell you but the DMP I analyzed was caused by pool corruption and had a 24 bugcheck. The
Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
I see you have run memtest but wonder for how many passes and if it was one stick at a time. did you also test eash mobo slot with known good ram?
I would also run a chkdsk
CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.
Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"
CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.
Remove your AV and replace with Microsoft security essentials
Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW
Let us know the results from the report at the end.
Ken
Analysis
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\New folder\081910-25334-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03016000 PsLoadedModuleList = 0xfffff800`03253e50
Debug session time: Wed Aug 18 18:58:35.316 2010 (GMT-4)
System Uptime: 3 days 13:09:02.875
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904fb, fffff88009658c28, fffff88009658490, fffff800031b9f8c}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
Followup: Pool_corruption
---------
0: 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: 00000000001904fb
Arg2: fffff88009658c28
Arg3: fffff88009658490
Arg4: fffff800031b9f8c
Debugging Details:
------------------
EXCEPTION_RECORD: fffff88009658c28 -- (.exr 0xfffff88009658c28)
ExceptionAddress: fffff800031b9f8c (nt!ExDeferredFreePool+0x0000000000000100)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88009658490 -- (.cxr 0xfffff88009658490)
rax=fffffa800fbcc620 rbx=0000000000000000 rcx=fffff80003215a00
rdx=ff00fa800fbcc4d0 rsi=0000000000000000 rdi=fffffa800e70f010
rip=fffff800031b9f8c rsp=fffff88009658e60 rbp=0000000000000000
r8=ff00fa800fbcc4d0 r9=0000000000000000 r10=fffff80003215888
r11=0000000000000000 r12=fffff80003215880 r13=0000000000000000
r14=0000000000000002 r15=0000000000000001
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!ExDeferredFreePool+0x100:
fffff800`031b9f8c 4c8b02 mov r8,qword ptr [rdx] ds:002b:ff00fa80`0fbcc4d0=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: WerFault.exe
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 fffff800032be0e0
ffffffffffffffff
FOLLOWUP_IP:
nt!ExDeferredFreePool+100
fffff800`031b9f8c 4c8b02 mov r8,qword ptr [rdx]
FAULTING_IP:
nt!ExDeferredFreePool+100
fffff800`031b9f8c 4c8b02 mov r8,qword ptr [rdx]
BUGCHECK_STR: 0x24
LAST_CONTROL_TRANSFER: from fffff800031bb4c1 to fffff800031b9f8c
STACK_TEXT:
fffff880`09658e60 fffff800`031bb4c1 : 00000000`00000100 fffffa80`0fbcc660 00000000`00000000 fffff800`03212d40 : nt!ExDeferredFreePool+0x100
fffff880`09658ef0 fffff800`032e63fb : fffffa80`09d42b10 fffffa80`0fbcc6b8 fffffa80`6c526d4d 00000000`000007ff : nt!ExFreePoolWithTag+0x411
fffff880`09658fa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x3896e
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ExDeferredFreePool+100
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
STACK_COMMAND: .cxr 0xfffff88009658490 ; kb
FAILURE_BUCKET_ID: X64_0x24_nt!ExDeferredFreePool+100
BUCKET_ID: X64_0x24_nt!ExDeferredFreePool+100
Followup: Pool_corruption
---------
0: 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: 00000000001904fb
Arg2: fffff88009658c28
Arg3: fffff88009658490
Arg4: fffff800031b9f8c
Debugging Details:
------------------
EXCEPTION_RECORD: fffff88009658c28 -- (.exr 0xfffff88009658c28)
ExceptionAddress: fffff800031b9f8c (nt!ExDeferredFreePool+0x0000000000000100)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88009658490 -- (.cxr 0xfffff88009658490)
rax=fffffa800fbcc620 rbx=0000000000000000 rcx=fffff80003215a00
rdx=ff00fa800fbcc4d0 rsi=0000000000000000 rdi=fffffa800e70f010
rip=fffff800031b9f8c rsp=fffff88009658e60 rbp=0000000000000000
r8=ff00fa800fbcc4d0 r9=0000000000000000 r10=fffff80003215888
r11=0000000000000000 r12=fffff80003215880 r13=0000000000000000
r14=0000000000000002 r15=0000000000000001
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!ExDeferredFreePool+0x100:
fffff800`031b9f8c 4c8b02 mov r8,qword ptr [rdx] ds:002b:ff00fa80`0fbcc4d0=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: WerFault.exe
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: ffffffffffffffff
FOLLOWUP_IP:
nt!ExDeferredFreePool+100
fffff800`031b9f8c 4c8b02 mov r8,qword ptr [rdx]
FAULTING_IP:
nt!ExDeferredFreePool+100
fffff800`031b9f8c 4c8b02 mov r8,qword ptr [rdx]
BUGCHECK_STR: 0x24
LAST_CONTROL_TRANSFER: from fffff800031bb4c1 to fffff800031b9f8c
STACK_TEXT:
fffff880`09658e60 fffff800`031bb4c1 : 00000000`00000100 fffffa80`0fbcc660 00000000`00000000 fffff800`03212d40 : nt!ExDeferredFreePool+0x100
fffff880`09658ef0 fffff800`032e63fb : fffffa80`09d42b10 fffffa80`0fbcc6b8 fffffa80`6c526d4d 00000000`000007ff : nt!ExFreePoolWithTag+0x411
fffff880`09658fa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x3896e
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ExDeferredFreePool+100
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
STACK_COMMAND: .cxr 0xfffff88009658490 ; kb
FAILURE_BUCKET_ID: X64_0x24_nt!ExDeferredFreePool+100
BUCKET_ID: X64_0x24_nt!ExDeferredFreePool+100
Followup: Pool_corruption
---------
Old drivers needing update
Code:
GVTDrv64.sys fffff880`057db000 fffff880`057e5000 0x0000a000 0x44fd22ca 9/5/2006 03:10:02
Rt64win7.sys fffff880`13e00000 fffff880`13e32000 0x00032000 0x49a65b0d 2/26/2009 05:04:13
gdrv.sys fffff880`05bf7000 fffff880`05c00000 0x00009000 0x49b9d175 3/12/2009 23:22:29
AtiPcie.sys fffff880`01840000 fffff880`01848000 0x00008000 0x4a005486 5/5/2009 11:00:22
spldr.sys fffff880`015f0000 fffff880`015f8000 0x00008000 0x4a0858bb 5/11/2009 12:56:27
spsys.sys fffff880`04570000 fffff880`045e1000 0x00071000 0x4a085e7a 5/11/2009 13:20:58
amdxata.sys fffff880`00e33000 fffff880`00e3e000 0x0000b000 0x4a12f2eb 5/19/2009 13:56:59
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads