Hi,
I just joined this forum because i am having bluescreens frequently and cannot find the source. I was wondering if anyone had any suggestions.
I get seemingly random bluescreen message codes that dont seem related to me in any way.
I have 2 ATi graphics cards running the latest drivers, I have also tried older drivers as well. I have tried to run with only 1 card and that seems to stop the bluescreens, but if i put the second card back in, it starts to bluescreen. This would indicate a fault graphics card, however it doesnt matter which card is in, as long as its on its own.
I am currently running with only 1 stick of ram at a time to see if any of the ram is faulty, but i did get another bluescreen shortly after starting back up from removing all other ram sticks.
i dont have dump files for all of the bluescreens ive had, but the last 5 are said to be caused by the following:
- tcpip.sys
- fltmgr.sys
- ntfs.sys
- atikmdag.sys
- tunnel.sys
I also remember having quite a few from ntokrnl.exe as well.
not long after the bluescreens started, i completely re-installed my OS and software (usually i would just restore from an image). so i dont think its software related.
any suggestions?
I just joined this forum because i am having bluescreens frequently and cannot find the source. I was wondering if anyone had any suggestions.
I get seemingly random bluescreen message codes that dont seem related to me in any way.
I have 2 ATi graphics cards running the latest drivers, I have also tried older drivers as well. I have tried to run with only 1 card and that seems to stop the bluescreens, but if i put the second card back in, it starts to bluescreen. This would indicate a fault graphics card, however it doesnt matter which card is in, as long as its on its own.
I am currently running with only 1 stick of ram at a time to see if any of the ram is faulty, but i did get another bluescreen shortly after starting back up from removing all other ram sticks.
i dont have dump files for all of the bluescreens ive had, but the last 5 are said to be caused by the following:
- tcpip.sys
- fltmgr.sys
- ntfs.sys
- atikmdag.sys
- tunnel.sys
I also remember having quite a few from ntokrnl.exe as well.
not long after the bluescreens started, i completely re-installed my OS and software (usually i would just restore from an image). so i dont think its software related.
any suggestions?
Welcome to the forum.
Please read these threads and post back. We will be glad to help you.
[1 - Novice] How to ask for help with a BSOD problem
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html
Please read these threads and post back. We will be glad to help you.
[1 - Novice] How to ask for help with a BSOD problem
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html
Thanks for that.
I have run the tool and zipped the output as requested.
I hope someone can help me identify my problem.
I myself am thinking the motherboard is becomming faulty.
I have run the tool and zipped the output as requested.
I hope someone can help me identify my problem.
I myself am thinking the motherboard is becomming faulty.
Why are you suspecting the motherboard? I'm not doubting you, just asking. I will look at the files and be right back.
I suspect my motherboard because it is the oldest part in my machine. bought back in 2008.
I have just had another 2 bluescreens. the first whilst half way through a film, and the second whilst trying to post about the first bluescreen. thats 4 bluescreens since 7PM (UK Time).
these were caused by msahci.sys and ntfs.sys.. this is so annoying
I have just had another 2 bluescreens. the first whilst half way through a film, and the second whilst trying to post about the first bluescreen. thats 4 bluescreens since 7PM (UK Time).
these were caused by msahci.sys and ntfs.sys.. this is so annoying
The error codes point to hardware or hardware related issues.
Notice the things in common in the usual causes of each error code: device driver in all of them followed by memory in two.
The dumps don't point to a specific cause; most of them blame a Windows system driver, which is highly unlikely.
To begin troubleshooting, I suggest you enable Driver Verifier. Keep in mind that Driver Verifier will cause a crash when it encounters a faulty driver. Let driver verifier run for 36 hours and use your computer normally.
Driver Verifier - Enable and Disable
Upload any new BSOD's as soon as you can. You don't need to upload the whole package again.
http://www.sevenforums.com/tutorials...en-forums.html
Quote:
STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver
STOP 0x00000034: CACHE_MANAGER
Usual causes: Insufficient physical memory, Indexing, Device driver
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver
STOP 0x00000034: CACHE_MANAGER
Usual causes: Insufficient physical memory, Indexing, Device driver
The dumps don't point to a specific cause; most of them blame a Windows system driver, which is highly unlikely.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Reports.zip\Windows7_BSOD_jcgriff2\080810-29000-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02e55000 PsLoadedModuleList = 0xfffff800`03092e50 Debug session time: Sun Aug 8 13:58:38.467 2010 (GMT-4) System Uptime: 0 days 19:32:27.314 Loading Kernel Symbols ............................................................... ................................................................ .............................. Loading User Symbols Loading unloaded module list ............ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff88001075100, fffff88009ea4d70, 0} Probably caused by : fltmgr.sys ( fltmgr!FltpPerformPreCallbacks+3d0 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff88001075100, Address of the exception record for the exception that caused the bugcheck Arg3: fffff88009ea4d70, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: fltmgr!FltpPerformPreCallbacks+3d0 fffff880`01075100 b911000000 mov ecx,11h CONTEXT: fffff88009ea4d70 -- (.cxr 0xfffff88009ea4d70) rax=0000000000000000 rbx=fffffa80062a4100 rcx=0000000000000002 rdx=000000000000014c rsi=fffffa800c4c8e30 rdi=fffffa8006f63010 rip=fffff88001075100 rsp=fffff88009ea5740 rbp=fffffa8006f60e60 r8=fffffa8006f83940 r9=fffffa8006f6daf0 r10=000000000000014e r11=0000000000000001 r12=0000000000000054 r13=fffffa80062a1630 r14=fffffa8006f60bb0 r15=fffff88009ea58e0 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 fltmgr!FltpPerformPreCallbacks+0x3d0: fffff880`01075100 b911000000 mov ecx,11h Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: mpc-hc.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88001075100 STACK_TEXT: fffff880`09ea5740 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fltmgr!FltpPerformPreCallbacks+0x3d0 FOLLOWUP_IP: fltmgr!FltpPerformPreCallbacks+3d0 fffff880`01075100 b911000000 mov ecx,11h SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: fltmgr!FltpPerformPreCallbacks+3d0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: fltmgr IMAGE_NAME: fltmgr.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc11f STACK_COMMAND: .cxr 0xfffff88009ea4d70 ; kb FAILURE_BUCKET_ID: X64_0x3B_fltmgr!FltpPerformPreCallbacks+3d0 BUCKET_ID: X64_0x3B_fltmgr!FltpPerformPreCallbacks+3d0 Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Reports.zip\Windows7_BSOD_jcgriff2\080810-26800-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02e51000 PsLoadedModuleList = 0xfffff800`0308ee50 Debug session time: Sun Aug 8 14:21:50.478 2010 (GMT-4) System Uptime: 0 days 0:03:25.226 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {2, 2, 1, fffff8800167a6c0} Probably caused by : tcpip.sys ( tcpip!KfdIsV4InTransportFastEmpty+0 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 0000000000000002, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff8800167a6c0, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f90e0 0000000000000002 CURRENT_IRQL: 2 FAULTING_IP: tcpip!KfdIsV4InTransportFastEmpty+0 fffff880`0167a6c0 ff259a650c00 jmp qword ptr [tcpip!_imp_KfdIsV4InTransportFastEmpty (fffff880`01740c60)] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff88003bb0910 -- (.trap 0xfffff88003bb0910) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000002 rbx=0000000000000000 rcx=fffffa8001d1ff00 rdx=fffffa8001444980 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8800167a6c0 rsp=fffff88003bb0aa8 rbp=fffff88003bb0db8 r8=fffff88003bb0db8 r9=0000000000000000 r10=fffff88003bb0d10 r11=fffff88003bb0c58 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc tcpip!KfdIsV4InTransportFastEmpty: fffff880`0167a6c0 ff259a650c00 jmp qword ptr [tcpip!_imp_KfdIsV4InTransportFastEmpty (fffff880`01740c60)] ds:2120:fffff880`01740c60=00000000001da7ea Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ec0b69 to fffff80002ec1600 STACK_TEXT: fffff880`03bb07c8 fffff800`02ec0b69 : 00000000`0000000a 00000000`00000002 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`03bb07d0 fffff800`02ebf7e0 : 00000000`00000000 00000000`00000020 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`03bb0910 fffff880`0167a6c0 : fffff880`01675791 00000000`00000000 00000000`00000010 fffffa80`014337b0 : nt!KiPageFault+0x260 fffff880`03bb0aa8 fffff880`01675791 : 00000000`00000000 00000000`00000010 fffffa80`014337b0 fffffa80`04f3a5c0 : tcpip!KfdIsV4InTransportFastEmpty fffff880`03bb0ab0 fffff880`0167a0ca : fffffa80`01d1ff00 00000000`00000000 fffffa80`01bc4da8 00000000`00000000 : tcpip!TcpTcbReceive+0x291 fffff880`03bb0c60 fffff880`01679c17 : fffffa80`0289cf22 fffffa80`01d1b270 00000000`00000000 fffff880`0165d400 : tcpip!TcpMatchReceive+0x1fa fffff880`03bb0db0 fffff880`0165c3c7 : fffffa80`01d15000 fffffa80`01bf8ec0 fffffa80`01d15000 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x177 fffff880`03bb0e60 fffff880`0165c499 : fffff880`03bb0fe0 fffff880`0176c9a0 fffff880`03bb0ff0 fffffa80`01b98df0 : tcpip!IppDeliverListToProtocol+0x97 fffff880`03bb0f20 fffff880`0165c990 : fffffa80`02651030 fffffa80`02650a00 00000000`00000011 fffff880`03bb0fe0 : tcpip!IppProcessDeliverList+0x59 fffff880`03bb0f90 fffff880`0165b821 : 00000000`1900a8c0 fffffa80`01d1b270 fffff880`0176c9a0 00000000`025d9001 : tcpip!IppReceiveHeaderBatch+0x231 fffff880`03bb1070 fffff880`0165a272 : fffffa80`02668220 00000000`00000000 fffffa80`025d9001 00000000`00000003 : tcpip!IpFlcReceivePackets+0x651 fffff880`03bb1270 fffff880`016736ba : fffffa80`025d9010 fffff880`03bb13a0 fffffa80`025d9010 fffff880`03bb0000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2 fffff880`03bb1350 fffff800`02ed0d4a : fffffa80`02650030 fffff880`03bac000 00000000`00004800 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda fffff880`03bb13a0 fffff880`016730e2 : fffff880`016735e0 fffff880`03bb14b0 fffffa80`025db302 fffff880`014964bc : nt!KeExpandKernelStackAndCalloutEx+0xda fffff880`03bb1480 fffff880`014cc0eb : fffffa80`025db380 00000000`00000000 fffffa80`024f91a0 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2 fffff880`03bb14f0 fffff880`01495fc6 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb fffff880`03bb1560 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6 STACK_COMMAND: kb FOLLOWUP_IP: tcpip!KfdIsV4InTransportFastEmpty+0 fffff880`0167a6c0 ff259a650c00 jmp qword ptr [tcpip!_imp_KfdIsV4InTransportFastEmpty (fffff880`01740c60)] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: tcpip!KfdIsV4InTransportFastEmpty+0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: tcpip IMAGE_NAME: tcpip.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc26e FAILURE_BUCKET_ID: X64_0xD1_tcpip!KfdIsV4InTransportFastEmpty+0 BUCKET_ID: X64_0xD1_tcpip!KfdIsV4InTransportFastEmpty+0 Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Reports.zip\Windows7_BSOD_jcgriff2\080710-36098-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02e18000 PsLoadedModuleList = 0xfffff800`03055e50 Debug session time: Fri Aug 6 20:11:14.063 2010 (GMT-4) System Uptime: 0 days 0:08:34.640 Loading Kernel Symbols ............................................................... ................................................................ ........................... Loading User Symbols Loading unloaded module list .......... Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff8800a1fff71, fffff88007bd04e8, fffff88007bcfd50} Probably caused by : atikmdag.sys ( atikmdag+360f71 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff8800a1fff71, The address that the exception occurred at Arg3: fffff88007bd04e8, Exception Record Address Arg4: fffff88007bcfd50, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: atikmdag+360f71 fffff880`0a1fff71 488b01 mov rax,qword ptr [rcx] EXCEPTION_RECORD: fffff88007bd04e8 -- (.exr 0xfffff88007bd04e8) ExceptionAddress: fffff8800a1fff71 (atikmdag+0x0000000000360f71) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000000 Attempt to read from address 0000000000000000 CONTEXT: fffff88007bcfd50 -- (.cxr 0xfffff88007bcfd50) rax=fffffa8008c7f200 rbx=fffffa8008c7f200 rcx=0000000000000000 rdx=fffffa8005a18400 rsi=fffffa8005a18020 rdi=fffffa8005a18420 rip=fffff8800a1fff71 rsp=fffff88007bd0720 rbp=0000000000000000 r8=0000000000000000 r9=0000000000000000 r10=fffffa8008c7f200 r11=fffff88007bd0600 r12=0000000000000000 r13=fffffa8005ea28a0 r14=fffffa8009333640 r15=fffffa8005f0f000 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210282 atikmdag+0x360f71: fffff880`0a1fff71 488b01 mov rax,qword ptr [rcx] ds:002b:00000000`00000000=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: NULL_DEREFERENCE PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c00e0 0000000000000000 FOLLOWUP_IP: atikmdag+360f71 fffff880`0a1fff71 488b01 mov rax,qword ptr [rcx] BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8800a1fff71 STACK_TEXT: fffff880`07bd0720 00000000`00000000 : 00000000`00000004 00000000`00000001 00000000`000007ff fffffa80`05a18420 : atikmdag+0x360f71 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: atikmdag+360f71 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmdag IMAGE_NAME: atikmdag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c33da58 STACK_COMMAND: .cxr 0xfffff88007bcfd50 ; kb FAILURE_BUCKET_ID: X64_0x7E_atikmdag+360f71 BUCKET_ID: X64_0x7E_atikmdag+360f71 Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Reports.zip\Windows7_BSOD_jcgriff2\080710-24242-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02e58000 PsLoadedModuleList = 0xfffff800`03095e50 Debug session time: Sat Aug 7 13:25:20.018 2010 (GMT-4) System Uptime: 0 days 4:11:48.000 Loading Kernel Symbols ............................................................... ................................................................ .............................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 34, {50830, fffff880033937c8, fffff88003393030, fffff80002ef2580} Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+10 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CACHE_MANAGER (34) See the comment for FAT_FILE_SYSTEM (0x23) Arguments: Arg1: 0000000000050830 Arg2: fffff880033937c8 Arg3: fffff88003393030 Arg4: fffff80002ef2580 Debugging Details: ------------------ EXCEPTION_RECORD: fffff880033937c8 -- (.exr 0xfffff880033937c8) ExceptionAddress: fffff80002ef2580 (nt!MmUnmapViewInSystemCache+0x0000000000000010) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000001 Parameter[1]: 0000000000000000 Attempt to write to address 0000000000000000 CONTEXT: fffff88003393030 -- (.cxr 0xfffff88003393030) rax=0000000000000000 rbx=fffffa800620a730 rcx=fffff98007900000 rdx=fffff8a00cfc8960 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002ef2580 rsp=fffff88003393a00 rbp=0000000000000000 r8=0000000000000000 r9=0000000000000000 r10=000000000000007f r11=0000000000000003 r12=fffffa80057dc380 r13=fffffa800620a730 r14=0000000000000001 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210246 nt!MmUnmapViewInSystemCache+0x10: fffff800`02ef2580 56 push rsi Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: NULL_DEREFERENCE PROCESS_NAME: System 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: 0000000000000001 EXCEPTION_PARAMETER2: 0000000000000000 WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800031000e0 0000000000000000 FOLLOWUP_IP: nt!MmUnmapViewInSystemCache+10 fffff800`02ef2580 56 push rsi FAULTING_IP: nt!MmUnmapViewInSystemCache+10 fffff800`02ef2580 56 push rsi BUGCHECK_STR: 0x34 LAST_CONTROL_TRANSFER: from fffff800031e0155 to fffff80002ef2580 STACK_TEXT: fffff880`03393a00 fffff800`031e0155 : fffff980`07900000 fffff8a0`0cfc8960 00000000`00000000 00000000`00200246 : nt!MmUnmapViewInSystemCache+0x10 fffff880`03393a10 fffff800`02ee1447 : 00000000`00000000 fffffa80`057dc380 00000000`00000000 00000000`00040000 : nt!CcUnmapVacb+0x5d fffff880`03393a50 fffff800`02eb8174 : 00000000`00000001 fffffa80`05fe6480 fffffa80`0620a700 00000000`00000000 : nt!CcUnmapVacbArray+0x1b7 fffff880`03393ae0 fffff800`02ebbc1c : fffffa80`0620a730 00000000`00000011 fffffa80`0620a730 fffff800`00000000 : nt!CcDeleteSharedCacheMap+0x140 fffff880`03393b50 fffff800`02ebc41c : fffff800`030cf100 fffff880`03393c58 00000000`00000000 fffff800`00000000 : nt!CcWriteBehind+0x5bc fffff880`03393c00 fffff800`02ed5861 : fffffa80`05808ab0 fffff800`02ebc254 fffff800`030cf140 fffffa80`00000000 : nt!CcWorkerThread+0x1c8 fffff880`03393cb0 fffff800`0316da86 : 33333333`33333333 fffffa80`05804040 00000000`00000080 fffffa80`057ee040 : nt!ExpWorkerThread+0x111 fffff880`03393d40 fffff800`02ea6b06 : fffff880`03164180 fffffa80`05804040 fffff880`0316efc0 33333333`13333333 : nt!PspSystemThreadStartup+0x5a fffff880`03393d80 00000000`00000000 : fffff880`03394000 fffff880`0338e000 fffff880`033939f0 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!MmUnmapViewInSystemCache+10 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb STACK_COMMAND: .cxr 0xfffff88003393030 ; kb IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x34_nt!MmUnmapViewInSystemCache+10 BUCKET_ID: X64_0x34_nt!MmUnmapViewInSystemCache+10 Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Reports.zip\Windows7_BSOD_jcgriff2\080610-24554-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02e17000 PsLoadedModuleList = 0xfffff800`03054e50 Debug session time: Fri Aug 6 13:02:36.923 2010 (GMT-4) System Uptime: 0 days 0:48:28.500 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc000001d, fffffa8009abab3e, fffff8800339aa08, fffff8800339a270} Probably caused by : tunnel.sys ( tunnel!TunnelWorkQueueRoutine+1c ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc000001d, The exception code that was not handled Arg2: fffffa8009abab3e, The address that the exception occurred at Arg3: fffff8800339aa08, Exception Record Address Arg4: fffff8800339a270, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction. FAULTING_IP: +16 fffffa80`09abab3e ff ??? EXCEPTION_RECORD: fffff8800339aa08 -- (.exr 0xfffff8800339aa08) ExceptionAddress: fffffa8009abab3e ExceptionCode: c000001d (Illegal instruction) ExceptionFlags: 00000000 NumberParameters: 0 CONTEXT: fffff8800339a270 -- (.cxr 0xfffff8800339a270) rax=fffffa8006ea67d0 rbx=fffffa8006ee1060 rcx=fffff880042c3d58 rdx=fffffa8006ea67d0 rsi=fffffa8005804b60 rdi=fffffa8006ed3390 rip=fffffa8009abab3e rsp=fffff8800339ac48 rbp=fffff8000302c5a0 r8=0000000000000000 r9=00000000002a4c66 r10=0000000000008493 r11=fffffa8006ed3390 r12=fffffa8006ed3390 r13=0000000000000001 r14=0000000000000000 r15=0000000000000001 iopl=0 nv up ei ng nz ac po cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010297 fffffa80`09abab3e ff ??? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x7E PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction. LAST_CONTROL_TRANSFER: from fffff880042b65a8 to fffffa8009abab3e FAILED_INSTRUCTION_ADDRESS: +16 fffffa80`09abab3e ff ??? STACK_TEXT: fffff880`0339ac48 fffff880`042b65a8 : fffff800`0302c5a0 fffff880`045745d8 00000000`00000000 00000000`00000000 : 0xfffffa80`09abab3e fffff880`0339ac50 fffff800`03184827 : fffffa80`06ee1060 fffff800`0302c5a0 fffffa80`09045010 fffffa80`05804b60 : tunnel!TunnelWorkQueueRoutine+0x1c fffff880`0339ac80 fffff800`02e94861 : fffff880`04574500 fffff880`04574510 fffffa80`05804b60 fffff800`00000000 : nt!IopProcessWorkItem+0x23 fffff880`0339acb0 fffff800`0312ca86 : fffd3ab8`e8ce8b4c fffffa80`05804b60 00000000`00000080 fffffa80`057ee040 : nt!ExpWorkerThread+0x111 fffff880`0339ad40 fffff800`02e65b06 : fffff880`03164180 fffffa80`05804b60 fffff880`0316efc0 0148c22b`480b7ec9 : nt!PspSystemThreadStartup+0x5a fffff880`0339ad80 00000000`00000000 : fffff880`0339b000 fffff880`03395000 fffff880`0339a9f0 00000000`00000000 : nt!KxStartSystemThread+0x16 FOLLOWUP_IP: tunnel!TunnelWorkQueueRoutine+1c fffff880`042b65a8 488b3d99d70000 mov rdi,qword ptr [tunnel!TunnelGlobal+0x368 (fffff880`042c3d48)] SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: tunnel!TunnelWorkQueueRoutine+1c FOLLOWUP_NAME: MachineOwner MODULE_NAME: tunnel IMAGE_NAME: tunnel.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bccc1 STACK_COMMAND: .cxr 0xfffff8800339a270 ; kb FAILURE_BUCKET_ID: X64_0x7E_BAD_IP_tunnel!TunnelWorkQueueRoutine+1c BUCKET_ID: X64_0x7E_BAD_IP_tunnel!TunnelWorkQueueRoutine+1c Followup: MachineOwner ---------
Driver Verifier - Enable and Disable
Upload any new BSOD's as soon as you can. You don't need to upload the whole package again.
http://www.sevenforums.com/tutorials...en-forums.html
Hi.. Thanks for a quick reply..
I have tried the driver verifier before and it just crashes constantly.
I have just had another bluescreen this one is caused by dxgmm1.sys. i have included the minidumps from these last few BSOD's.
I have now put all my RAM back into my pc as it doesnt seem to make any difference with the crashes. (now back up to 6GB)
I have tried the driver verifier before and it just crashes constantly.
I have just had another bluescreen this one is caused by dxgmm1.sys. i have included the minidumps from these last few BSOD's.
I have now put all my RAM back into my pc as it doesnt seem to make any difference with the crashes. (now back up to 6GB)
I bought installed my motherboard in 2005. It is obsolete; but still working fine.
Driver Verifier is supposed to cause crashes it it finds faulty drivers. The dump files will (hopefully) point to the offending driver.
I will look that that latest dump. dxgmm1.sys is a Direct X driver. That could mean your video card is acting up. What antivirus and firewall are you using.
The latest dump is another error code D1. It does blame dxgmm1.sys and also points to atikmdag.sys, ATI grapchic card driver.
Driver Verifier is supposed to cause crashes it it finds faulty drivers. The dump files will (hopefully) point to the offending driver.
I will look that that latest dump. dxgmm1.sys is a Direct X driver. That could mean your video card is acting up. What antivirus and firewall are you using.
The latest dump is another error code D1. It does blame dxgmm1.sys and also points to atikmdag.sys, ATI grapchic card driver.
I have tried testing my video cards by removing them. I have 2 ATi 4870's one of them is an X2. If i remove either one of them my pc seems to be ok, but both in together seems to cause crashes. which is one of the other reasons why i suspect my motherboard. if it was my graphics card alone that was causing faults.. it would still appear if i had the bad card alone in my pc. but that doesnt appear to be the case.
i have Microsoft Security Essentials and i just use the windows default firewall.
i have Microsoft Security Essentials and i just use the windows default firewall.
Very good on the antivirus and Windows Firewall.
I suspect it is your graphics card arrangement causing some of this. All of your drivers are up to date, something I rarely see with BSOD's. I am going to ask for help from the graphics card gurus. I am not an expert in that area by any means. By the way, one of the other dumps I looked at implicated atikmdag.sys, also.
I suspect it is your graphics card arrangement causing some of this. All of your drivers are up to date, something I rarely see with BSOD's. I am going to ask for help from the graphics card gurus. I am not an expert in that area by any means. By the way, one of the other dumps I looked at implicated atikmdag.sys, also.
Ok no worries. Thanks for your help.
do you think it would be possible to tell which of my cards is the faulty one from bug reports?
do you think it would be possible to tell which of my cards is the faulty one from bug reports?
No, rarely does a bug report point to a specific piece of hardware. You can test your graphics cards, though. I would test them one at a time without driver verifier running. Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Ok. I will try and run the GPU stress test.
in the meantime, i just had another bluescreen. this time from win32k.sys, it occurred shortly after the furmark download completed.
in the meantime, i just had another bluescreen. this time from win32k.sys, it occurred shortly after the furmark download completed.
This one is another error code 3B. When debug points to a Windows system driver you can almost be positive that driver is not the cause. Debug simply blames it because it has to have something to blame. The key in this dump is BugCheck 3B, {c0000005, fffff960000e3c88, fffff88009377990, 0}. 0000005 means a memory error. It does not necessarily mean bad RAM; it can be corrupted memory caused by something else. And I think this is probably the case.
so you're thinking that one of my graphics cards is sending bad signals which is causing corruption in my RAM, which then leads to a bluescreen. I guess I can understand this, but why would the error message be different each time? is it because the area on the RAM which gets corrupted due to bad signals is random?
It depends on what other drivers and/or processes are in use at the time, what interrupts are involved, what registers are involved, etc. I am not sure either of your video cards are bad. It could be some sort of conflict between the two of them. As I said, I am not knowledgeable in this area and I have put out a call for help with this. Most of the guys who can help us in this area are not on line right now.
Are you overclocking anything?
Check for a BIOS update, if you find a newer version, load it.
Have you gotten any TDR errors?
The atikmdag.sys problem is an indication of GPU driver problems, uninstall the drivers and re-install them.
You might need to search for all atikmdag files and delete them.
Check here for some ideas, STOP 0x116: VIDEO_TDR_ERROR troubleshooting
Check for FW for the graphics cards, you might need to update them.
Check for a BIOS update, if you find a newer version, load it.
Have you gotten any TDR errors?
The atikmdag.sys problem is an indication of GPU driver problems, uninstall the drivers and re-install them.
You might need to search for all atikmdag files and delete them.
Check here for some ideas, STOP 0x116: VIDEO_TDR_ERROR troubleshooting
Check for FW for the graphics cards, you might need to update them.
Thanks much, Dave.
Hi Dave,
I am not overclocking anything my BIOS is pretty much at defaults. It is also the latest stable release of the BIOS firmware.
I dont get any TDR errors and that atikmdag.sys bluescreen is the only one ive seen since these bluescreens started. my Driver and CCC is the latest version.
not sure about graphics cards firmware..i just assume this is part of the driver update process.
I could uninstall and re-install them (which i did recently during an update from 10.5 to 10.7), but as i said in a previous post. I have re-installed windows from scratch and the bluescreens continue.
I ran the Fur Test on my X2 for 20 mins last night (just as a quick test i know it needs to run for many many hours to be of any use) and nothing special happened. Will try running it on my 4870 single now and see if it bluescreens.
I am not overclocking anything my BIOS is pretty much at defaults. It is also the latest stable release of the BIOS firmware.
I dont get any TDR errors and that atikmdag.sys bluescreen is the only one ive seen since these bluescreens started. my Driver and CCC is the latest version.
not sure about graphics cards firmware..i just assume this is part of the driver update process.
I could uninstall and re-install them (which i did recently during an update from 10.5 to 10.7), but as i said in a previous post. I have re-installed windows from scratch and the bluescreens continue.
I ran the Fur Test on my X2 for 20 mins last night (just as a quick test i know it needs to run for many many hours to be of any use) and nothing special happened. Will try running it on my 4870 single now and see if it bluescreens.
Hello and Welcome !
There are few issues going on mainly i have noticed the Keyboard is not functioning properly i.e.
Lot of Random crashes mostly caused by the Memory i would recommend Run a Hardware Diagnostic (Memory and Hard Drive) follow this link for instructions Hardware Diagnostic !! � Captain Debugger
Good Luck,
Captain
There are few issues going on mainly i have noticed the Keyboard is not functioning properly i.e.
Code:
Standard PS/2 Keyboard ACPI\PNP0303\4&23F9C1E3&0 This device is not present, is not working properly, or does not have all its drivers installed.
Good Luck,
Captain
Hello Captain Jack,
My keyboard works just fine. I dont know why that message showed up in the report.
I have tried all sorts of combinations for my RAM and it doesnt seem to make a difference. I have tried both Windows Own Memory Checker and Memtest86+ and it found no errors.
My keyboard works just fine. I dont know why that message showed up in the report.
I have tried all sorts of combinations for my RAM and it doesnt seem to make a difference. I have tried both Windows Own Memory Checker and Memtest86+ and it found no errors.
�� Quote: Originally Posted by Sirik 
Hello Captain Jack,
My keyboard works just fine. I dont know why that message showed up in the report.
I have tried all sorts of combinations for my RAM and it doesnt seem to make a difference. I have tried both Windows Own Memory Checker and Memtest86+ and it found no errors.
My keyboard works just fine. I dont know why that message showed up in the report.
I have tried all sorts of combinations for my RAM and it doesnt seem to make a difference. I have tried both Windows Own Memory Checker and Memtest86+ and it found no errors.
Device Manager says the best driver is already installed for this device.
HID Keyboard Device.
Memtest i ran overnight and it seemed fine in the morning.
HID Keyboard Device.
Memtest i ran overnight and it seemed fine in the morning.
Hi,
I dont know if you guys are still interested. I know i'm getting very fed up with this problem now and am very tempted to take a hammer to everything in my PC. But I've just had another crash.. this one by the ntoskrnl.exe
dump file attached
I dont know if you guys are still interested. I know i'm getting very fed up with this problem now and am very tempted to take a hammer to everything in my PC. But I've just had another crash.. this one by the ntoskrnl.exe
dump file attached
I see your Yukon network drivers are old. Please update them to the latest version.
Enable driver verifier: Driver Verifier - Enable and Disable
Enable driver verifier: Driver Verifier - Enable and Disable
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_080910-20888-01.zip\080910-20888-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 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02e11000 PsLoadedModuleList = 0xfffff800`0304ee50 Debug session time: Mon Aug 9 17:40:32.485 2010 (UTC - 4:00) System Uptime: 0 days 1:48:21.077 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {8, 80050031, 6f8, fffff80002e90d47} Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050031 Arg3: 00000000000006f8 Arg4: fffff80002e90d47 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: mpc-hc.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002e80b69 to fffff80002e81600 STACK_TEXT: fffff880`0316ace8 fffff800`02e80b69 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx fffff880`0316acf0 fffff800`02e7f032 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`0316ae30 fffff800`02e90d47 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2 00000000`07dbe2c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd7 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiDoubleFaultAbort+b2 fffff800`02e7f032 90 nop SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiDoubleFaultAbort+b2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 Followup: MachineOwner --------- 2: kd> lmnsm start end module name fffff880`00f8a000 fffff880`00fe1000 ACPI ACPI.sys fffff880`07e6d000 fffff880`07eac000 afcdp afcdp.sys fffff880`02e3b000 fffff880`02ec5000 afd afd.sys fffff880`041e1000 fffff880`041f7000 AgileVpn AgileVpn.sys fffff880`00c2a000 fffff880`00c35000 amdxata amdxata.sys fffff880`04a43000 fffff880`04a4b000 ASACPI ASACPI.sys fffff880`0845a000 fffff880`08465000 asyncmac asyncmac.sys fffff880`00ecd000 fffff880`00ed6000 atapi atapi.sys fffff880`00c00000 fffff880`00c2a000 ataport ataport.SYS fffff880`06200000 fffff880`06223000 AtiHdmi AtiHdmi.sys fffff880`04a5b000 fffff880`0518a000 atikmdag atikmdag.sys fffff880`040f2000 fffff880`04138000 atikmpag atikmpag.sys fffff880`013e1000 fffff880`013e8000 Beep Beep.SYS fffff880`01050000 fffff880`01061000 blbdrive blbdrive.sys fffff880`02db0000 fffff880`02dce000 bowser bowser.sys fffff960`00720000 fffff960`00747000 cdd cdd.dll fffff880`015d4000 fffff880`015fe000 cdrom cdrom.sys fffff880`00d0a000 fffff880`00dca000 CI CI.dll fffff880`01816000 fffff880`01846000 CLASSPNP CLASSPNP.SYS fffff880`00cac000 fffff880`00d0a000 CLFS CLFS.SYS fffff880`01124000 fffff880`01197000 cng cng.sys fffff880`04092000 fffff880`040a2000 CompositeBus CompositeBus.sys fffff880`06223000 fffff880`06231000 crashdmp crashdmp.sys fffff880`0458e000 fffff880`045cb000 CT20XUT CT20XUT.SYS fffff880`04138000 fffff880`041e0b80 ctaud2k ctaud2k.sys fffff880`06298000 fffff880`063fc000 CTEXFIFX CTEXFIFX.SYS fffff880`05de4000 fffff880`05e00000 CTHWIUT CTHWIUT.SYS fffff880`051c7000 fffff880`051f8000 ctoss2k ctoss2k.sys fffff880`043f5000 fffff880`043fd000 ctprxy2k ctprxy2k.sys fffff880`05c00000 fffff880`05c38000 ctsfm2k ctsfm2k.sys fffff880`02e0f000 fffff880`02e2d000 dfsc dfsc.sys fffff880`02e00000 fffff880`02e0f000 discache discache.sys fffff880`01800000 fffff880`01816000 disk disk.sys fffff880`04211000 fffff880`04233000 drmk drmk.sys fffff880`06231000 fffff880`0623d000 dump_dumpata dump_dumpata.sys fffff880`06248000 fffff880`0625b000 dump_dumpfve dump_dumpfve.sys fffff880`0623d000 fffff880`06248000 dump_msahci dump_msahci.sys fffff880`0625b000 fffff880`06267000 Dxapi Dxapi.sys fffff880`04234000 fffff880`04328000 dxgkrnl dxgkrnl.sys fffff880`04328000 fffff880`0436e000 dxgmms1 dxgmms1.sys fffff880`04544000 fffff880`0458e000 emupia2k emupia2k.sys fffff880`010b2000 fffff880`010c6000 fileinfo fileinfo.sys fffff880`01066000 fffff880`010b2000 fltmgr fltmgr.sys fffff880`013d7000 fffff880`013e1000 Fs_Rec Fs_Rec.sys fffff880`019c5000 fffff880`019ff000 fvevol fvevol.sys fffff880`0158a000 fffff880`015d4000 fwpkclnt fwpkclnt.sys fffff880`05c42000 fffff880`05dcf000 ha20x22k ha20x22k.sys fffff800`033ed000 fffff800`03436000 hal hal.dll fffff880`0436e000 fffff880`04392000 HDAudBus HDAudBus.sys fffff880`045cb000 fffff880`045e4000 HIDCLASS HIDCLASS.SYS fffff880`05c38000 fffff880`05c40080 HIDPARSE HIDPARSE.SYS fffff880`06284000 fffff880`06292000 hidusb hidusb.sys fffff880`02ce8000 fffff880`02db0000 HTTP HTTP.sys fffff880`01a3a000 fffff880`01a43000 hwpolicy hwpolicy.sys fffff880`040dc000 fffff880`040f2000 intelppm intelppm.sys fffff880`04083000 fffff880`04092000 kbdclass kbdclass.sys fffff880`045f1000 fffff880`045ff000 kbdhid kbdhid.sys fffff800`00bc5000 fffff800`00bcf000 kdcom kdcom.dll fffff880`04a00000 fffff880`04a43000 ks ks.sys fffff880`013ac000 fffff880`013c6000 ksecdd ksecdd.sys fffff880`0155f000 fffff880`0158a000 ksecpkg ksecpkg.sys fffff880`051f8000 fffff880`051fd200 ksthunk ksthunk.sys fffff880`02cbb000 fffff880`02cd0000 lltdio lltdio.sys fffff880`01846000 fffff880`01869000 luafv luafv.sys fffff880`00c54000 fffff880`00c98000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll fffff880`04400000 fffff880`0440e000 monitor monitor.sys fffff880`044c7000 fffff880`044d6000 mouclass mouclass.sys fffff880`045e4000 fffff880`045f1000 mouhid mouhid.sys fffff880`00dda000 fffff880`00df4000 mountmgr mountmgr.sys fffff880`01197000 fffff880`011c4000 MpFilter MpFilter.sys fffff880`08400000 fffff880`08410000 MpNWMon MpNWMon.sys fffff880`02dce000 fffff880`02de6000 mpsdrv mpsdrv.sys fffff880`02c00000 fffff880`02c2d000 mrxsmb mrxsmb.sys fffff880`02c2d000 fffff880`02c7b000 mrxsmb10 mrxsmb10.sys fffff880`07e4a000 fffff880`07e6d000 mrxsmb20 mrxsmb20.sys fffff880`00ff4000 fffff880`00fff000 msahci msahci.sys fffff880`01009000 fffff880`01014000 Msfs Msfs.SYS fffff880`00fea000 fffff880`00ff4000 msisadrv msisadrv.sys fffff880`010c6000 fffff880`01124000 msrpc msrpc.sys fffff880`02ff1000 fffff880`02ffc000 mssmbios mssmbios.sys fffff880`019b3000 fffff880`019c5000 mup mup.sys fffff880`0140d000 fffff880`014ff000 ndis ndis.sys fffff880`04436000 fffff880`04442000 ndistapi ndistapi.sys fffff880`04442000 fffff880`04471000 ndiswan ndiswan.sys fffff880`05dcf000 fffff880`05de4000 NDProxy NDProxy.SYS fffff880`02f39000 fffff880`02f48000 netbios netbios.sys fffff880`02ec5000 fffff880`02f0a000 netbt netbt.sys fffff880`014ff000 fffff880`0155f000 NETIO NETIO.SYS fffff880`01014000 fffff880`01025000 Npfs Npfs.SYS fffff880`02fe5000 fffff880`02ff1000 nsiproxy nsiproxy.sys fffff800`02e11000 fffff800`033ed000 nt ntkrnlmp.exe fffff880`01209000 fffff880`013ac000 Ntfs Ntfs.sys fffff880`01400000 fffff880`01409000 Null Null.SYS fffff880`02f13000 fffff880`02f39000 pacer pacer.sys fffff880`00e40000 fffff880`00e55000 partmgr partmgr.sys fffff880`00e00000 fffff880`00e33000 pci pci.sys fffff880`00ec6000 fffff880`00ecd000 pciide pciide.sys fffff880`00dca000 fffff880`00dda000 PCIIDEX PCIIDEX.SYS fffff880`013c6000 fffff880`013d7000 pcw pcw.sys fffff880`07eac000 fffff880`07f52000 peauth peauth.sys fffff880`0518a000 fffff880`051c7000 portcls portcls.sys fffff880`00c98000 fffff880`00cac000 PSHED PSHED.dll fffff880`04412000 fffff880`04436000 rasl2tp rasl2tp.sys fffff880`04471000 fffff880`0448c000 raspppoe raspppoe.sys fffff880`0448c000 fffff880`044ad000 raspptp raspptp.sys fffff880`044ad000 fffff880`044c7000 rassstp rassstp.sys fffff880`02f94000 fffff880`02fe5000 rdbss rdbss.sys fffff880`013f6000 fffff880`013ff000 RDPCDD RDPCDD.sys fffff880`01200000 fffff880`01209000 rdpencdd rdpencdd.sys fffff880`01000000 fffff880`01009000 rdprefmp rdprefmp.sys fffff880`01a00000 fffff880`01a3a000 rdyboost rdyboost.sys fffff880`0841a000 fffff880`08429000 RNDISMPX RNDISMPX.SYS fffff880`02cd0000 fffff880`02ce8000 rspndr rspndr.sys fffff880`07f52000 fffff880`07f5d000 secdrv secdrv.SYS fffff880`04a4b000 fffff880`04a57000 serenum serenum.sys fffff880`02f48000 fffff880`02f65000 serial serial.sys fffff880`01bbb000 fffff880`01bfa000 snapman snapman.sys fffff880`01bb4000 fffff880`01bbb000 speedfan speedfan.sys fffff880`01bac000 fffff880`01bb4000 spldr spldr.sys fffff880`0855a000 fffff880`085f2000 srv srv.sys fffff880`084f1000 fffff880`0855a000 srv2 srv2.sys fffff880`07f5d000 fffff880`07f8a000 srvnet srvnet.sys fffff880`044d6000 fffff880`044d7480 swenum swenum.sys fffff880`01602000 fffff880`017ff000 tcpip tcpip.sys fffff880`07f8a000 fffff880`07f9c000 tcpipreg tcpipreg.sys fffff880`01043000 fffff880`01050000 TDI TDI.SYS fffff880`01a46000 fffff880`01bac000 tdrpm251 tdrpm251.sys fffff880`01025000 fffff880`01043000 tdx tdx.sys fffff880`02f80000 fffff880`02f94000 termdd termdd.sys fffff880`01882000 fffff880`01967000 timntr timntr.sys fffff960`005c0000 fffff960`005ca000 TSDDD TSDDD.dll fffff880`040b6000 fffff880`040dc000 tunnel tunnel.sys fffff880`044d8000 fffff880`044ea000 umbus umbus.sys fffff880`08410000 fffff880`0841a000 usb8023x usb8023x.sys fffff880`04065000 fffff880`04082000 usbccgp usbccgp.sys fffff880`06282000 fffff880`06283f00 USBD USBD.SYS fffff880`04200000 fffff880`04211000 usbehci usbehci.sys fffff880`044ea000 fffff880`04544000 usbhub usbhub.sys fffff880`0439f000 fffff880`043f5000 USBPORT USBPORT.SYS fffff880`06267000 fffff880`06282000 USBSTOR USBSTOR.SYS fffff880`04392000 fffff880`0439f000 usbuhci usbuhci.sys fffff880`00e33000 fffff880`00e40000 vdrvroot vdrvroot.sys fffff880`013e8000 fffff880`013f6000 vga vga.sys fffff880`011c4000 fffff880`011e9000 VIDEOPRT VIDEOPRT.SYS fffff880`00e55000 fffff880`00e6a000 volmgr volmgr.sys fffff880`00e6a000 fffff880`00ec6000 volmgrx volmgrx.sys fffff880`01967000 fffff880`019b3000 volsnap volsnap.sys fffff880`02f65000 fffff880`02f80000 wanarp wanarp.sys fffff880`011e9000 fffff880`011f9000 watchdog watchdog.sys fffff880`00ed7000 fffff880`00f7b000 Wdf01000 Wdf01000.sys fffff880`00f7b000 fffff880`00f8a000 WDFLDR WDFLDR.SYS fffff880`02f0a000 fffff880`02f13000 wfplwf wfplwf.sys fffff960`000b0000 fffff960`003bf000 win32k win32k.sys fffff880`00fe1000 fffff880`00fea000 WMILIB WMILIB.SYS fffff880`02c9a000 fffff880`02cbb000 WudfPf WudfPf.sys fffff880`08429000 fffff880`0845a000 WUDFRd WUDFRd.sys fffff880`04000000 fffff880`04065000 yk62x64 yk62x64.sys Unloaded modules: fffff880`08465000 fffff880`084d6000 spsys.sys fffff880`01846000 fffff880`01854000 crashdmp.sys fffff880`01854000 fffff880`01860000 dump_pciidex fffff880`01860000 fffff880`0186b000 dump_msahci. fffff880`0186b000 fffff880`0187e000 dump_dumpfve fffff880`04065000 fffff880`04083000 i8042prt.sys 2: kd> lmvm yk62x64 start end module name fffff880`04000000 fffff880`04065000 yk62x64 (deferred) Image path: \SystemRoot\system32\DRIVERS\yk62x64.sys Image name: yk62x64.sys Timestamp: Mon Sep 28 04:19:31 2009 (4AC07193) CheckSum: 0006B55C ImageSize: 00065000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Thanks for that. I updated my network driver from the marvel website even though Windows Update says the driver was up to date. It clearly wasnt.
I have enabled driver verifier.. will see what happens tomorrow when i turn my pc on again.
I have enabled driver verifier.. will see what happens tomorrow when i turn my pc on again.
�� Quote: Originally Posted by Sirik Hi Dave,
I am not overclocking anything my BIOS is pretty much at defaults. It is also the latest stable release of the BIOS firmware.
I dont get any TDR errors and that atikmdag.sys bluescreen is the only one ive seen since these bluescreens started. my Driver and CCC is the latest version.
not sure about graphics cards firmware..i just assume this is part of the driver update process.
I could uninstall and re-install them (which i did recently during an update from 10.5 to 10.7), but as i said in a previous post. I have re-installed windows from scratch and the bluescreens continue.
I ran the Fur Test on my X2 for 20 mins last night (just as a quick test i know it needs to run for many many hours to be of any use) and nothing special happened. Will try running it on my 4870 single now and see if it bluescreens.
I am not overclocking anything my BIOS is pretty much at defaults. It is also the latest stable release of the BIOS firmware.
I dont get any TDR errors and that atikmdag.sys bluescreen is the only one ive seen since these bluescreens started. my Driver and CCC is the latest version.
not sure about graphics cards firmware..i just assume this is part of the driver update process.
I could uninstall and re-install them (which i did recently during an update from 10.5 to 10.7), but as i said in a previous post. I have re-installed windows from scratch and the bluescreens continue.
I ran the Fur Test on my X2 for 20 mins last night (just as a quick test i know it needs to run for many many hours to be of any use) and nothing special happened. Will try running it on my 4870 single now and see if it bluescreens.
It's a good suggestion to run the Hardware Diagnostics posted by Capt. Jack.
Be thorough, take notes and be as specific as possible when reporting the results.
Does your device manager have any yellow triangles next to any of the listed devices?
How long have you had the graphic cards?
Which brand and p/n are they?
Can you D/L CPUZ.
Open CPUZ and take a screen shot of the CPU, Memory and SPD tabs, use the Snipping tool, Start button> All Programs> Accessories> Snipping Tool.
Save to a convenient place.
Then post using this method.
How to Post a Screenshot in Seven Forums.
This will give us some information needed to analyze further.
Check your BIOS and let us know what voltage the RAM is currently running at.
�� Quote: Originally Posted by Sirik Thanks for that. I updated my network driver from the marvel website even though Windows Update says the driver was up to date. It clearly wasnt.
I have enabled driver verifier.. will see what happens tomorrow when i turn my pc on again.
I have enabled driver verifier.. will see what happens tomorrow when i turn my pc on again.
Oh dear another day another 3 bluescreens.
I turned my computer on for the first time after enabling the driver verifier and as soon as my PC got to the desktop it crashed due to snapman.sys.
So i let it reboot and try again and snapman crashed again,
so one last time i let it reboot and yep...snapman crashed again.
so i went into safemode to turn off the verifier so i could post the 3 minidumps this created.
I turned my computer on for the first time after enabling the driver verifier and as soon as my PC got to the desktop it crashed due to snapman.sys.
So i let it reboot and try again and snapman crashed again,
so one last time i let it reboot and yep...snapman crashed again.
so i went into safemode to turn off the verifier so i could post the 3 minidumps this created.
I haven't checked the dumps, but Snapman is an Acronis driver. I have seen it crash before, so I would advise removing Acronis True Image completely.
You don't have to be left without backup, though. Windows has a built-in backup program that works quite well. To create a system image, see these tutorials:
Backup Complete Computer - Create an Image Backup
System Image Recovery
You don't have to be left without backup, though. Windows has a built-in backup program that works quite well. To create a system image, see these tutorials:
Backup Complete Computer - Create an Image Backup
System Image Recovery
Thanks Jonathan... I will try removing this now.
I did a quick check on the acronis support site and version 7046 of True Image Home 2010 is supposed to fix "freezes in Windows Vista and Windows 7".
I have used this version for quite a while without any bluescreens, so either Windows Update did something Acronis didnt like, or there is still something else killing my PC.
I did a quick check on the acronis support site and version 7046 of True Image Home 2010 is supposed to fix "freezes in Windows Vista and Windows 7".
I have used this version for quite a while without any bluescreens, so either Windows Update did something Acronis didnt like, or there is still something else killing my PC.
Hello Sirik!
Thank you for reporting about the issue!
Jonathan is right - snapman is our service, but there are different reasons why it may crash. Most probably that's the drivers conflict, which can be easily solved by updating SnapAPI. In order to receive the update link you need to either contact support directly or send a Private Message to any Forum Moderator. We will be very glad to help you and make sure that everything is working fine.
I will entirely understand, though, if you decide to remove the product from your machine. Please keep in mind that you can always share your feedback with us and Our Manahgement team.
Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!
Thank you!
--
Best regards,
Yana | Acronis Customer Central
Thank you for reporting about the issue!
Jonathan is right - snapman is our service, but there are different reasons why it may crash. Most probably that's the drivers conflict, which can be easily solved by updating SnapAPI. In order to receive the update link you need to either contact support directly or send a Private Message to any Forum Moderator. We will be very glad to help you and make sure that everything is working fine.
I will entirely understand, though, if you decide to remove the product from your machine. Please keep in mind that you can always share your feedback with us and Our Manahgement team.
Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!
Thank you!
--
Best regards,
Yana | Acronis Customer Central
Hello Again,
After uninstalling Acronis yesterday, Today i have another Bluescreen caused by NTFS.sys.
Looks like Acronis is not causing my bluescreens.
any more ideas?
After uninstalling Acronis yesterday, Today i have another Bluescreen caused by NTFS.sys.
Looks like Acronis is not causing my bluescreens.
any more ideas?
Please follow these directions: http://www.sevenforums.com/crashes-d...tructions.html
Open an elevated command prompt and enter chkdsk /r.
Open an elevated command prompt and enter chkdsk /r.
Oh just remembered someone wanted me to post these screenshots from CPU-z
I performed the checkdisk. No errors were found.
Looks like i have no choice but to buy new hardware and replace everything in my PC.
Computers are so expensive...if it wasnt for all the PC games i have and the triple monitor setup I would just buy a laptop instead and give up my PC.
Looks like i have no choice but to buy new hardware and replace everything in my PC.
Computers are so expensive...if it wasnt for all the PC games i have and the triple monitor setup I would just buy a laptop instead and give up my PC.
�� Quote: Originally Posted by Sirik Hello Again,
After uninstalling Acronis yesterday, Today i have another Bluescreen caused by NTFS.sys.
Looks like Acronis is not causing my bluescreens.
any more ideas?
After uninstalling Acronis yesterday, Today i have another Bluescreen caused by NTFS.sys.
Looks like Acronis is not causing my bluescreens.
any more ideas?
At this point, please turn Driver Verifier off and lets see how your system is running.
I have now uninstalled Rainmeter and disabled driver verifier.
I have also run another sfc /scannow and have attached the log as it said there were errors it was unable to repair.
I have also run another sfc /scannow and have attached the log as it said there were errors it was unable to repair.
Very good. Let's see how your system does.
I seem to have had another bluescreen this morning whilst i was in the shower.
Unfortunatly there were no minidumps created. just some entries in the event viewer.
Log Name: System
Source: EventLog
Date: 15-Aug-10 11:43:39 AM
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Sirik-PC
Description:
The previous system shutdown at 11:42:11 on ?15/?08/?2010 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-08-15T10:43:39.000000000Z" />
<EventRecordID>20956</EventRecordID>
<Channel>System</Channel>
<Computer>Sirik-PC</Computer>
<Security />
</System>
<EventData>
<Data>11:42:11</Data>
<Data>?15/?08/?2010</Data>
<Data>
</Data>
<Data>
</Data>
<Data>3981</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>DA07080000000F000B002A000B008E03DA07080000000F000A002A000B008E033C0000003C000000000000000000 0000000000000000000001000000F7FFFFFF</Binary>
</EventData>
</Event>
Unfortunatly there were no minidumps created. just some entries in the event viewer.
Log Name: System
Source: EventLog
Date: 15-Aug-10 11:43:39 AM
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Sirik-PC
Description:
The previous system shutdown at 11:42:11 on ?15/?08/?2010 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-08-15T10:43:39.000000000Z" />
<EventRecordID>20956</EventRecordID>
<Channel>System</Channel>
<Computer>Sirik-PC</Computer>
<Security />
</System>
<EventData>
<Data>11:42:11</Data>
<Data>?15/?08/?2010</Data>
<Data>
</Data>
<Data>
</Data>
<Data>3981</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>DA07080000000F000B002A000B008E03DA07080000000F000A002A000B008E033C0000003C000000000000000000 0000000000000000000001000000F7FFFFFF</Binary>
</EventData>
</Event>
I seem to be forgetting when these crashes happen.
What is the make/model of your PSU?
What is the make/model of your PSU?
The crashes happen randomly... this morning my pc had not long been on, it wasnt doing anything just being idle on the desktop when it happened.
my PSU is not that old, its a Corsair 1000w Modular PSU
my PSU is not that old, its a Corsair 1000w Modular PSU
Hi Again,
I have another random Bluescreen again when my computer was idle.
any idea's what piece of hardware is causing this so i can replace it...this is really annoying.
I have another random Bluescreen again when my computer was idle.
any idea's what piece of hardware is causing this so i can replace it...this is really annoying.
Do you have another video card you can try? Try borrowing one from a friend or another computer.
...Summary of the Dumps:
...Summary of the Dumps:
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Mon Aug 16 16:34:31.003 2010 (UTC - 4:00) System Uptime: 0 days 4:03:49.986 BugCheck A, {15d0e1, 2, 1, fffff80002ee0880} Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+250 ) BUGCHECK_STR: 0xA PROCESS_NAME: sidebar.exe �������������������������������������������������������������������������������������� I'm afraid I dont have access to another video card. Is that what you think the problem is?
I have to suspect some sort of video memory corruption. Try taking the computer to the local PC shop and having them test your card.
Did your computer have the BSoDs since you built it?
If not, what software and/or hardware was installed before the blue screens started?
List everything, even if it seems un-related.
Did it start out as very seldom and slowly increased or start all of a sudden?
When you updated the BIOS, was this around the time the blue screens started?
Check your graphics card manufacturer site for FW (FirmWare) updates.
This has to be done separately, it does not come with MOBO BIOS or any drivers.
What is the brand and exact model numbers of your graphic cards?
When you ran memtest86+ was this with all the RAM cards installed?
How many runs did you do?
Do you have 6GB RAM?
What size are the cards? (3X2GB, 2X2GB and 2X1GB?)
How many cards are installed? (3 or 4?)
Did you buy these all at the same time? Same brand and P/N?
Have you ever bumped the north bridge voltage?
Check everything in the case for loose connections, possible grounding points.
Re-seat all cables.
This could be a grounding issue.
Check your MOBO for bulging or leaking capacitors.
What version is your MOBO?
P5E3 Deluxe?
Version E3468 or Version E3366?
If anything here doesn't help then you should do a bench test, take everything out of the case and set it up on a table.
PSU, motherboard, one RAM card, one graphics card and one monitor.
Take everything else out, no sound card etc.
Test if it will load BIOS.
Add HDD, see if it will run, test for BSoD.
Then add one component at a time until you get the blue screen.
Edit:
Just noticed this:
�� Quote: Originally Posted by Sirik You should resolve this issue before doing any hardware tests.
Try a restore point, run sfc /scannow, if you get the same message, choose an earlier restore point.
If this fails to resolve the problem, try a Repair Install.
If not, what software and/or hardware was installed before the blue screens started?
List everything, even if it seems un-related.
Did it start out as very seldom and slowly increased or start all of a sudden?
When you updated the BIOS, was this around the time the blue screens started?
Check your graphics card manufacturer site for FW (FirmWare) updates.
This has to be done separately, it does not come with MOBO BIOS or any drivers.
What is the brand and exact model numbers of your graphic cards?
When you ran memtest86+ was this with all the RAM cards installed?
How many runs did you do?
Do you have 6GB RAM?
What size are the cards? (3X2GB, 2X2GB and 2X1GB?)
How many cards are installed? (3 or 4?)
Did you buy these all at the same time? Same brand and P/N?
Have you ever bumped the north bridge voltage?
Check everything in the case for loose connections, possible grounding points.
Re-seat all cables.
This could be a grounding issue.
Check your MOBO for bulging or leaking capacitors.
What version is your MOBO?
P5E3 Deluxe?
Version E3468 or Version E3366?
If anything here doesn't help then you should do a bench test, take everything out of the case and set it up on a table.
PSU, motherboard, one RAM card, one graphics card and one monitor.
Take everything else out, no sound card etc.
Test if it will load BIOS.
Add HDD, see if it will run, test for BSoD.
Then add one component at a time until you get the blue screen.
Edit:
Just noticed this:
�� Quote: Originally Posted by Sirik I have now uninstalled Rainmeter and disabled driver verifier.
I have also run another sfc /scannow and have attached the log as it said there were errors it was unable to repair.
I have also run another sfc /scannow and have attached the log as it said there were errors it was unable to repair.
Try a restore point, run sfc /scannow, if you get the same message, choose an earlier restore point.
If this fails to resolve the problem, try a Repair Install.
Quote:
Originally Posted by Sirik 
I have now uninstalled Rainmeter and disabled driver verifier.
I have also run another sfc /scannow and have attached the log as it said there were errors it was unable to repair.
I have now uninstalled Rainmeter and disabled driver verifier.
I have also run another sfc /scannow and have attached the log as it said there were errors it was unable to repair.
Quote:
You should resolve this issue before doing any hardware tests.
Try a restore point, run sfc /scannow, if you get the same message, choose an earlier restore point.
If this fails to resolve the problem, try a Repair Install.
Try a restore point, run sfc /scannow, if you get the same message, choose an earlier restore point.
If this fails to resolve the problem, try a Repair Install.
I think i narrowed down the SFC problem...It was misreading the system files due to the "change" created by Windows 7 Universal Theme Patcher. When i reboot after doing an SFC it restores the theme files back to system default and SFC completes ok.. of course then i patch again.
My Computer did not bluescreen when i first built it 2 years ago. It started this year first only when i first turned it on, it would get to the desktop bluescreen, reboot, and then it would be fine for the rest of the day. then it start to progress to several random times a day.
I have not updated my BIOS, it came with the latest firmware and there are no updates available. it is a P5E3 Standard.
I have 2 Graphics Cards: 1x ATi 4870X2 PowerColor 1GB GDDR5, and 1x ATi 4870 Saphire 1GB GDDR5. Linked by Crossfire Cable, but Crossfire disabled most of the time in CCC. Drivers and CCC is the latest version, I dont know where to find Firmware on ATi's website so I've never done that.
I have run memtest86+ for 8 hours with all sticks in with no errors.
I have 4 Sticks of DDR3-PC10660 Geil RAM. All bought at the same time.
I have 2x2GB and 2x1GB all running at 1.5v default in the bios.
Motherboard does not appear damaged in any way.
I could try taking everything out as you suggest, but unfortunatly i need at least 1 of my ATi cards installed as my motherboard doesnt have an onboard graphics. This makes it tricky to test if its the motherboard causing the problem or the graphics card.
My Computer did not bluescreen when i first built it 2 years ago. It started this year first only when i first turned it on, it would get to the desktop bluescreen, reboot, and then it would be fine for the rest of the day. then it start to progress to several random times a day.
I have not updated my BIOS, it came with the latest firmware and there are no updates available. it is a P5E3 Standard.
I have 2 Graphics Cards: 1x ATi 4870X2 PowerColor 1GB GDDR5, and 1x ATi 4870 Saphire 1GB GDDR5. Linked by Crossfire Cable, but Crossfire disabled most of the time in CCC. Drivers and CCC is the latest version, I dont know where to find Firmware on ATi's website so I've never done that.
I have run memtest86+ for 8 hours with all sticks in with no errors.
I have 4 Sticks of DDR3-PC10660 Geil RAM. All bought at the same time.
I have 2x2GB and 2x1GB all running at 1.5v default in the bios.
Motherboard does not appear damaged in any way.
I could try taking everything out as you suggest, but unfortunatly i need at least 1 of my ATi cards installed as my motherboard doesnt have an onboard graphics. This makes it tricky to test if its the motherboard causing the problem or the graphics card.
Among other things, the bench test will eliminate any grounding issues, you can save this step until you have checked everything else.
You should follow Jonathan_King's advice and find a way to test with a different graphics card.
If you get another crash, uninstall Windows 7 Universal Theme Patcher, check if you still have crashes.
Have you checked for an updated version of this program?
You need to eliminate any possible causes of the crashes.
You should follow Jonathan_King's advice and find a way to test with a different graphics card.
If you get another crash, uninstall Windows 7 Universal Theme Patcher, check if you still have crashes.
Have you checked for an updated version of this program?
You need to eliminate any possible causes of the crashes.
Hi Dave,
I will try rolling back the universal theme patcher back to Windows Default and see if that helps.
as for testing a different graphics card, would this give a different result to taking 1 of my cards out? I have tried running my PC with only 1 of my graphics cards installed and i ran it for a week without any crashes, but when i install the second cards it starts crashing again. problem is, it doesnt seem to matter which card i take out, its only with the 2 cards that i get crashes.
I will try rolling back the universal theme patcher back to Windows Default and see if that helps.
as for testing a different graphics card, would this give a different result to taking 1 of my cards out? I have tried running my PC with only 1 of my graphics cards installed and i ran it for a week without any crashes, but when i install the second cards it starts crashing again. problem is, it doesnt seem to matter which card i take out, its only with the 2 cards that i get crashes.
�� Quote: Originally Posted by Sirik Hi Dave,
I will try rolling back the universal theme patcher back to Windows Default and see if that helps.
as for testing a different graphics card, would this give a different result to taking 1 of my cards out? I have tried running my PC with only 1 of my graphics cards installed and i ran it for a week without any crashes, but when i install the second cards it starts crashing again. problem is, it doesnt seem to matter which card i take out, its only with the 2 cards that i get crashes.
I will try rolling back the universal theme patcher back to Windows Default and see if that helps.
as for testing a different graphics card, would this give a different result to taking 1 of my cards out? I have tried running my PC with only 1 of my graphics cards installed and i ran it for a week without any crashes, but when i install the second cards it starts crashing again. problem is, it doesnt seem to matter which card i take out, its only with the 2 cards that i get crashes.
I will leave this to the graphics card gurus and wish you the best in figuring out the problem.
I decided to take my single 4870 out of my system so i could test for crashes using my 4870x2. Windows 7 Universal Theme Patcher is uninstalled also.
today shortly after turning my pc on i recieved the attached crash. again NTFS.sys.
today shortly after turning my pc on i recieved the attached crash. again NTFS.sys.
BugCheck 24 NTFS_FILE_SYSTEM - Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
The dump does not tell us very much. I have to admit to admit that I am baffled by this. You have run chkdsk and well as Memtest. And you have run Driver Verifier. At the moment, the only thing I can suggest is to make sure your RAM is seated properly and that your connections to your hard drive are good.
Code:
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {c08a2, 0, 0, 0} Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 ) Followup: MachineOwner --------- 3: 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: 00000000000c08a2 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x24 PROCESS_NAME: CCC.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff8800124ce95 to fffff80002e7f740 STACK_TEXT: fffff880`096196b8 fffff880`0124ce95 : 00000000`00000024 00000000`000c08a2 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx fffff880`096196c0 fffff880`0124cae8 : 00000001`00000000 00000000`00000000 00000000`00000000 000001fb`00001000 : Ntfs!NtfsPagingFileIo+0x155 fffff880`096197c0 fffff880`0109623f : fffffa80`094428d0 fffffa80`09442530 fffffa80`05acec30 00000000`00000000 : Ntfs! ?? ::FNODOBFM::`string'+0x9e89 fffff880`09619870 fffff880`010946df : fffffa80`064de950 fffffa80`09442530 fffffa80`064de900 fffffa80`09442530 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f fffff880`09619900 fffff800`02e711f2 : fffffa80`09442550 fffffa80`0645f9a0 00000000`00000043 fffff683`ff7b48c0 : fltmgr!FltpDispatch+0xcf fffff880`09619960 fffff800`02e714f5 : fffffa80`09d97601 fffffa80`09d97601 fffff880`09619a60 00000000`00000000 : nt!IoPageRead+0x252 fffff880`096199f0 fffff800`02e9a8bb : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffffa80`09ba92a8 : nt!MiIssueHardFault+0x255 fffff880`09619ac0 fffff800`02e7d82e : 00000000`00000008 00000000`00000051 ffffffff`ffb3b401 00000000`000001f4 : nt!MmAccessFault+0x14bb fffff880`09619c20 000007fe`f6918d60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`1bb3f938 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`f6918d60 STACK_COMMAND: kb FOLLOWUP_IP: Ntfs!NtfsPagingFileIo+155 fffff880`0124ce95 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: Ntfs!NtfsPagingFileIo+155 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Ntfs IMAGE_NAME: Ntfs.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc14f FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsPagingFileIo+155 BUCKET_ID: X64_0x24_Ntfs!NtfsPagingFileIo+155 Followup: MachineOwner --------- yeah i have tried all of that.... i think i will just replace it all when i get enough free cash together.
I believe it is a hardware issue; I just can't put my finger on it.
You need to test with another graphics card to be able to rule this out or confirm it's the cause.
If you need to find a shop that can do this for you, it will confirm the cause instead of guessing, then you'll know if it's the graphics cards and not RAM related or motherboard faults.
If you need to find a shop that can do this for you, it will confirm the cause instead of guessing, then you'll know if it's the graphics cards and not RAM related or motherboard faults.
I just thought I would post a bit of a closing post in this thread.
I replaced my motherboard and CPU and since then I have not had a single Blue Screen.
The replacements where made last saturday, so should have had at least 1 by now.
Thank you for all your efforts.
I replaced my motherboard and CPU and since then I have not had a single Blue Screen.
The replacements where made last saturday, so should have had at least 1 by now.
Thank you for all your efforts.
Glad to hear that it's running stable.
Let us know if there are any other issues.
Let us know if there are any other issues.
That is good news! Thank you for posting back with the solution. Happy computing. Don't be a starnger to the forum.
Không có nhận xét nào:
Đăng nhận xét