Hi,
I got random BSOD with STOP0x0000001e or 3b on my Seven Ultimate x64. Most of them appears when i look flash video.
I haven't found the Minidump related of BSOD, if you need it i'll try to find them.
PS: i'm a french guy so sorry if you can't translate most of things in the prefmom.html.
These crashes were caused by hardware.
Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try
Thanks
Ken
old driversCode:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\102210-23259-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;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 Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a09000 PsLoadedModuleList = 0xfffff800`02c46e50 Debug session time: Thu Oct 21 18:21:47.880 2010 (GMT-4) System Uptime: 0 days 23:48:51.285 Loading Kernel Symbols . Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading 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 : hardware ( 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: +6262952f033fde44 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1E PROCESS_NAME: System CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff88002f8b328 -- (.exr 0xfffff88002f8b328) ExceptionAddress: fffff80002a84978 (nt!KiTimerWaitTest+0x0000000000000038) ExceptionCode: c000001d (Illegal instruction) ExceptionFlags: 00000000 NumberParameters: 0 TRAP_FRAME: fffff88002f8b3d0 -- (.trap 0xfffff88002f8b3d0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=a9ec001b0ab5e5d5 rbx=0000000000000000 rcx=0000000000000000 rdx=fffffa80061df3a0 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002a84978 rsp=fffff88002f8b560 rbp=000000000053db08 r8=fffff88002f65301 r9=0000000000000009 r10=0000000000000008 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc nt!KiTimerWaitTest+0x38: fffff800`02a84978 ff ??? Resetting default scope MISALIGNED_IP: nt!KiTimerWaitTest+38 fffff800`02a84978 ff ??? LAST_CONTROL_TRANSFER: from fffff80002a72c2e to fffff80002a7aed0 STACK_TEXT: fffff880`02f8a408 fffff800`02a72c2e : 00000000`00000000 fffff880`02f8a668 fffff880`02f8ab80 fffff800`02aa7e28 : nt!KeBugCheck fffff880`02f8a410 fffff800`02aa0bed : fffff800`02c87c24 fffff800`02bc0a3c fffff800`02a09000 fffff880`02f8b328 : nt!KiKernelCalloutExceptionHandler+0xe fffff880`02f8a440 fffff800`02aa8250 : fffff800`02bc8b5c fffff880`02f8a4b8 fffff880`02f8b328 fffff800`02a09000 : nt!RtlpExecuteHandlerForException+0xd fffff880`02f8a470 fffff800`02ab51b5 : fffff880`02f8b328 fffff880`02f8ab80 fffff880`00000000 fffffa80`061df3a0 : nt!RtlDispatchException+0x410 fffff880`02f8ab50 fffff800`02a7a542 : fffff880`02f8b328 fffffa80`061df3a0 fffff880`02f8b3d0 528096dc`d6a085e0 : nt!KiDispatchException+0x135 fffff880`02f8b1f0 fffff800`02a7869f : fffff880`02f8b3d0 fffffa80`04871e02 fffff880`02f63100 fffff800`00000000 : nt!KiExceptionDispatch+0xc2 fffff880`02f8b3d0 fffff800`02a84978 : fffffa80`05eff068 fffffa80`05eff068 00000000`00000000 fffffa80`05eff060 : nt!KiInvalidOpcodeFault+0x11f fffff880`02f8b560 fffff800`02a862cd : fffffa80`0722a120 fffffa80`061df3e8 fffffa80`061df3e8 00000000`00000000 : nt!KiTimerWaitTest+0x38 fffff880`02f8b5e0 fffff800`02a86e7e : 000000c7`9bd40abb fffff880`02f8bc58 00000000`0053db08 fffff880`02f65688 : nt!KiProcessExpiredTimerList+0x6d fffff880`02f8bc30 fffff800`02a86697 : 0000003e`8fe47dc8 0000003e`0053db08 0000003e`8fe47daf 00000000`00000008 : nt!KiTimerExpiration+0x1be fffff880`02f8bcd0 fffff800`02a836fa : fffff880`02f63180 fffff880`02f6dfc0 00000000`00000000 fffff880`00ea1f44 : nt!KiRetireDpcList+0x277 fffff880`02f8bd80 00000000`00000000 : fffff880`02f8c000 fffff880`02f86000 fffff880`02f8bd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: nt!KiKernelCalloutExceptionHandler+e fffff800`02a72c2e 90 nop SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: hardware FAILURE_BUCKET_ID: X64_IP_MISALIGNED BUCKET_ID: X64_IP_MISALIGNED Followup: MachineOwner ---------
Code:ADIHdAud.sys fffff880`05200000 fffff880`0526d000 0x0006d000 0x469f1d8e 7/19/2007 04:15:10 Kone.sys fffff880`053e9000 fffff880`053ecc80 0x00003c80 0x4940b9b4 12/11/2008 02:56:52 yk62x64.sys fffff880`0429e000 fffff880`04301000 0x00063000 0x49a2ba83 2/23/2009 11:02:27
Hi, thanks for your really fast answer ^^.
I'll try to run a memtest tomorrow and a checkdisk too.
The " Kone.sys " driver is the last driver available on the Roccat Website.
I'll check for the two others.
I've check on the Asus website and many new Bios are available. Mine was a Beta used for my new CPU. Do you think i should flash for the latest one ?
Tanks for your help !
Yep the ASUS EZ flash tool have a Crash Bios in case of problem during the flash. And it's a fresh install so nothing to lose on my System
Quote