New
#1
BSOD, core error
Can anyone explain me the error...
Thx
Can anyone explain me the error...
Thx
Hello,
Start by running Prime95; especially the Small and Large FFTs tests: https://www.sevenforums.com/tutorials...t-prime95.html
Could you upload a jcgriff2 report?
https://www.sevenforums.com/crashes-d...tructions.html
...Summary of the dumps:
Code:Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Fri Feb 11 06:35:14.470 2011 (UTC - 5:00) System Uptime: 0 days 0:53:34.531 Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE SystemProductName = System Product Name CPUID: "Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz" MaxSpeed: 2670 CurrentSpeed: 2672 จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Prime95 = 6-7 hours no crash. (smallFTTs)
3DMark = No crash
MemTest (overnight) = No errors
Furmark = Ok
Intel Processor Diagnostic Tool = Ok
Last edited by BuzzFuzz; 11 Feb 2011 at 09:49.
Oki, enabled...
After second reboot BSOD again, thx god, if i understand why is verifier enabled now.
Now is disabled coz my computer was very slow in this time.
Added attachments
Last edited by BuzzFuzz; 13 Feb 2011 at 13:50.
Well install these updated JMicron SATA drivers: ftp://driver.jmicron.com.tw/SATA_Con...17.62_WHQL.zipHow often do these crashes occur?Code:jraid.sys Mon Nov 23 01:43:32 2009 (4B0A2F14)
...Summary of the dumps:
Code:Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Sun Feb 13 13:22:17.151 2011 (GMT-5) System Uptime: 0 days 0:00:14.213 Probably caused by : CI.dll ( CI!SHATransform+5d8 ) DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0xA_VRF_CI!SHATransform+5d8 จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Quite often, when I turn on my computer starts after a few minutes freezing. If i play game, game freeze and stops responding so that the only solution is reboot pc manualy.
Most interesting in all this is if i reboot pc after first boot then the problem disappears.
I.E. When i wake up in the morning and turn on PC then i immediately turn off PC and again turn ON and problem disappears. It may sound strange but helps.
I do the same when PC idle (sleep) for some time. If i go anything work than my pc start freezing after 5-10 min, possible earlier.
Reboot and everything is ok.
Kenneth George King Many thanks for assistance-help
Cheers
Last edited by BuzzFuzz; 13 Feb 2011 at 21:45.
I suggest you backup your data, and then perform a clean install. It is almost certainly a hardware problem, but the diagnostics aren't showing the results we want to see.
Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jonathan\Desktop\Downloads\021411-23868-01\021411-23868-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Machine Name: Kernel base = 0xfffff800`03206000 PsLoadedModuleList = 0xfffff800`03443e50 Debug session time: Mon Feb 14 10:25:15.877 2011 (UTC - 5:00) System Uptime: 0 days 0:03:17.892 Loading Kernel Symbols ............................................................... ................................................................ .......................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) 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. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +6663663939616230 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x1E_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: BFBC2Game.exe CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff88002f935d8 -- (.exr 0xfffff88002f935d8) ExceptionAddress: fffff80003281d82 (nt!KiProcessExpiredTimerList+0x0000000000000072) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff88002f93680 -- (.trap 0xfffff88002f93680) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=a07f36768cdb0000 rbx=0000000000000000 rcx=fffffa80087c9360 rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80003281d82 rsp=fffff88002f93810 rbp=000000000000318d r8=fffff88002f66301 r9=0000000000000003 r10=000000000000008d r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc nt!KiProcessExpiredTimerList+0x72: fffff800`03281d82 803818 cmp byte ptr [rax],18h ds:8a00:a07f3676`8cdb0000=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000326e46e to fffff80003276710 STACK_TEXT: fffff880`02f926c8 fffff800`0326e46e : 00000000`00000014 fffffa80`0656f200 fffff880`02f92e40 fffff800`032a3668 : nt!KeBugCheck fffff880`02f926d0 fffff800`0329c40d : fffff800`03484b7c fffff800`033beea4 fffff800`03206000 fffff880`02f935d8 : nt!KiKernelCalloutExceptionHandler+0xe fffff880`02f92700 fffff800`032a3a90 : fffff800`033c5a60 fffff880`02f92778 fffff880`02f935d8 fffff800`03206000 : nt!RtlpExecuteHandlerForException+0xd fffff880`02f92730 fffff800`032b09ef : fffff880`02f935d8 fffff880`02f92e40 fffff880`00000000 fffff880`02f93838 : nt!RtlDispatchException+0x410 fffff880`02f92e10 fffff800`03275d82 : fffff880`02f935d8 fffffa80`087c9380 fffff880`02f93680 00000000`00000002 : nt!KiDispatchException+0x16f fffff880`02f934a0 fffff800`0327468a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2 fffff880`02f93680 fffff800`03281d82 : fffffa80`087c9380 fffffa80`08578c68 fffffa80`08578c68 00000000`00000102 : nt!KiGeneralProtectionFault+0x10a fffff880`02f93810 fffff800`032824be : 00000000`75f403e3 fffff880`02f93e88 00000000`0000318d fffff880`02f67728 : nt!KiProcessExpiredTimerList+0x72 fffff880`02f93e60 fffff800`03281cb7 : fffff880`02f641c2 fffff880`0000318d 00000000`00000001 00000000`0000008d : nt!KiTimerExpiration+0x1be fffff880`02f93f00 fffff800`0327c865 : 0000057c`00000000 fffffa80`064c5a80 00000000`00000000 fffff800`03396db0 : nt!KiRetireDpcList+0x277 fffff880`02f93fb0 fffff800`0327c67c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5 fffff880`091e7be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue STACK_COMMAND: kb FOLLOWUP_IP: nt!KiKernelCalloutExceptionHandler+e fffff800`0326e46e 90 nop SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e Followup: MachineOwner ---------
Ok, format - then what? Should I install drivers from Asus web or?
Or you need some "clean" report?