BSOD BC Code 1e Windows 64-bit Home Premium

Donovan702 · 20 Jan 2012

I recently built a gaming PC, and this past week or so, it will just randomly BSOD. It doesnt seem to have any real noticable trigger (happens while playing games or just using IE), and so far nothing i've tried has had any effect. Any help would be extremely appreciated.

Accidentally closed the error screen while typing this, but the other four lines below the error code were all zeros. if it happens again, i will update this post with it.

Dump files, Performance Report and System Specs

Windows 7 64-bit Home Premium
AMD FX-8150 3.6 Ghz 8-Core
AsRock 870 Extreme 3 R2.0
Corsair DDR3 1600 Mhz 2x4 GB
XFX Radeon HD 6870 2GB GDDR5 900Mhz Clock
Sanyo 26' LED-LCD TV
Western Digital 250 Gb 7200 rpm
Raidmax Rx 700 AC psu
Cooler Master Vortex Plus
Blue screened again, got the error report this time
To- writhziden, thank you for the help, will take some time to test all of these. Will post results.
Locale ID: 1033
Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80001EDB4E2
BCP3: FFFFF8801159BE90
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

writhziden · 20 Jan 2012

Code:



Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Donovan702\Windows_NT6_BSOD_jcgriff2\011912-18189-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`01e1c000 PsLoadedModuleList = 0xfffff800`02061670
Debug session time: Thu Jan 19 22:14:39.585 2012 (UTC - 7:00)
System Uptime: 0 days 2:23:38.303
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
---------

3: 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: 
+6331633766326138
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:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff880020f81e8 -- (.exr 0xfffff880020f81e8)
ExceptionAddress: fffff80001e9f333 (nt!KiDeferredReadyThread+0x000000000000067c)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff880020f8290 -- (.trap 0xfffff880020f8290)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001e9f333 rsp=fffff880020f8420 rbp=0000000000000000
 r8=0000000000000001  r9=0000000000000003 r10=fffff80001e1c000
r11=fffff880020f8470 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiDeferredReadyThread+0x67c:
fffff800`01e9f333 f0490fba6c243000 lock bts qword ptr [r12+30h],0 ds:0040:00000000`00000030=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80001e905fe to fffff80001e98c10

STACK_TEXT:  
fffff880`020f72c8 fffff800`01e905fe : 00000000`00000001 00000000`00000001 fffff880`020f7a40 fffff800`01ec4830 : nt!KeBugCheck
fffff880`020f72d0 fffff800`01ec44fd : fffff800`020a271c fffff800`01fdfc30 fffff800`01e1c000 fffff880`020f81e8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`020f7300 fffff800`01ec32d5 : fffff800`01fe30fc fffff880`020f7378 fffff880`020f81e8 fffff800`01e1c000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`020f7330 fffff800`01ed4361 : fffff880`020f81e8 fffff880`020f7a40 fffff880`00000000 fffffa80`06cf1b60 : nt!RtlDispatchException+0x415
fffff880`020f7a10 fffff800`01e982c2 : fffff880`020f81e8 fffff800`0200ee80 fffff880`020f8290 fffff880`020d0180 : nt!KiDispatchException+0x135
fffff880`020f80b0 fffff800`01e9641f : fffff880`020f8290 fffff880`020f8302 fffff880`020f8300 fffff880`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`020f8290 fffff800`01e9f333 : fffff880`021b4180 fffffa80`06d75b60 00000000`000e79fd fffffa80`079daca0 : nt!KiInvalidOpcodeFault+0x11f
fffff880`020f8420 fffff800`01ea4527 : fffffa80`06ff7120 fffffa80`06cf1c68 fffffa80`06cf1c68 00000000`00000000 : nt!KiDeferredReadyThread+0x67c
fffff880`020f84a0 fffff800`01ea437e : 00000014`10e8d3d1 fffff880`020f8b18 00000000`00086e03 fffff880`020d25e8 : nt!KiProcessExpiredTimerList+0x157
fffff880`020f8af0 fffff800`01ea4167 : 00000007`0a2a9ec2 00000007`00086e03 00000007`0a2a9e8d 00000000`00000003 : nt!KiTimerExpiration+0x1be
fffff880`020f8b90 fffff800`01e9096a : fffff880`020d0180 fffff880`020db0c0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff880`020f8c40 00000000`00000000 : fffff880`020f9000 fffff880`020f3000 fffff880`020f8c00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`01e905fe 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:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

Followup: MachineOwner
---------

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Donovan702\Windows_NT6_BSOD_jcgriff2\011912-17643-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`01c0c000 PsLoadedModuleList = 0xfffff800`01e51670
Debug session time: Thu Jan 19 10:16:17.097 2012 (UTC - 7:00)
System Uptime: 0 days 9:54:43.815
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff100041c85c8, 2, 1, fffff80001c8ee91}

Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+1d1 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff100041c85c8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80001c8ee91, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001ebb100
 fffff100041c85c8 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiDeferredReadyThread+1d1
fffff800`01c8ee91 4889442428      mov     qword ptr [rsp+28h],rax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880020f8290 -- (.trap 0xfffff880020f8290)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000000f5 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001c8ee91 rsp=fffff880020f8420 rbp=0000000000000003
 r8=00000000000000f5  r9=0000000000000003 r10=fffff80001c0c000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KiDeferredReadyThread+0x1d1:
fffff800`01c8ee91 4889442428      mov     qword ptr [rsp+28h],rax ss:0018:fffff880`020f8448=00000000000000f5
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80001c881e9 to fffff80001c88c40

STACK_TEXT:  
fffff880`020f8148 fffff800`01c881e9 : 00000000`0000000a fffff100`041c85c8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`020f8150 fffff800`01c86e60 : 00000000`00000000 00000000`00000000 fffff880`020f8310 fffff880`020d0180 : nt!KiBugCheckDispatch+0x69
fffff880`020f8290 fffff800`01c8ee91 : fffff880`022a5180 fffffa80`09b3b060 fffff880`0028e95e fffff880`07555077 : nt!KiPageFault+0x260
fffff880`020f8420 fffff800`01c94527 : fffffa80`09b8cc20 fffffa80`09b8cc68 fffffa80`09b8cc68 fffffa80`09b8b800 : nt!KiDeferredReadyThread+0x1d1
fffff880`020f84a0 fffff800`01c9437e : 00000053`1536297b fffff880`020f8b18 00000000`0022e731 fffff880`020d2ba8 : nt!KiProcessExpiredTimerList+0x157
fffff880`020f8af0 fffff800`01c94167 : 0000001d`255bcdc2 0000001d`0022e731 0000001d`255bcd99 00000000`00000031 : nt!KiTimerExpiration+0x1be
fffff880`020f8b90 fffff800`01c8096a : fffff880`020d0180 fffff880`020db0c0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff880`020f8c40 00000000`00000000 : fffff880`020f9000 fffff880`020f3000 fffff880`020f8c00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDeferredReadyThread+1d1
fffff800`01c8ee91 4889442428      mov     qword ptr [rsp+28h],rax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiDeferredReadyThread+1d1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiDeferredReadyThread+1d1

BUCKET_ID:  X64_0xA_nt!KiDeferredReadyThread+1d1

Followup: MachineOwner
---------

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Donovan702\Windows_NT6_BSOD_jcgriff2\011812-22495-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`01c66000 PsLoadedModuleList = 0xfffff800`01eab670
Debug session time: Wed Jan 18 20:13:46.073 2012 (UTC - 7:00)
System Uptime: 0 days 5:28:46.791
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff80046ceef5e, d, 8, fffff80046ceef5e}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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: fffff80046ceef5e, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff80046ceef5e, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001f15100
 fffff80046ceef5e 

CURRENT_IRQL:  d

FAULTING_IP: 
+3230333434626239
fffff800`46ceef5e ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880009d38e0 -- (.trap 0xfffff880009d38e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000008
rdx=0000000000000008 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80046ceef5e rsp=fffff880009d3a78 rbp=0000000000000000
 r8=0000000000134b91  r9=0000000000134b91 r10=000000000001fbc1
r11=00000000002f5b00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
fffff800`46ceef5e ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80001ce21e9 to fffff80001ce2c40

FAILED_INSTRUCTION_ADDRESS: 
+3230333434626239
fffff800`46ceef5e ??              ???

STACK_TEXT:  
fffff880`009d3798 fffff800`01ce21e9 : 00000000`0000000a fffff800`46ceef5e 00000000`0000000d 00000000`00000008 : nt!KeBugCheckEx
fffff880`009d37a0 fffff800`01ce0e60 : 00000000`00000206 fffff800`01d3ba8f fffff800`01e58e80 00000000`00134b91 : nt!KiBugCheckDispatch+0x69
fffff880`009d38e0 fffff800`46ceef5e : fffff800`01ceef3d 00000000`00000001 fffffa80`079ca910 00000000`00000000 : nt!KiPageFault+0x260
fffff880`009d3a78 fffff800`01ceef3d : 00000000`00000001 fffffa80`079ca910 00000000`00000000 fffffa80`0a682060 : 0xfffff800`46ceef5e
fffff880`009d3a80 fffff800`01ceece1 : fffff880`009c0180 fffff880`009d3b30 fffff880`009cb0c0 fffffa80`0a132a20 : nt!KeUpdateRunTime+0x9d
fffff880`009d3ab0 fffff800`01cda942 : fffff880`009c0180 fffff880`00000001 00000000`00000001 fffff880`00000000 : nt!KiSecondaryClockInterrupt+0x131
fffff880`009d3c40 00000000`00000000 : fffff880`009d4000 fffff880`009ce000 fffff880`009d3c00 00000000`00000000 : nt!KiIdleLoop+0x32


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`01ce0e60 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260

BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260

Followup: MachineOwner
---------

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Donovan702\Windows_NT6_BSOD_jcgriff2\011312-22807-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`01c18000 PsLoadedModuleList = 0xfffff800`01e55e70
Debug session time: Fri Jan 13 22:37:07.614 2012 (UTC - 7:00)
System Uptime: 0 days 1:28:08.332
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {100, 2, 1, fffff80001c94ff8}

Probably caused by : hardware ( nt!KiInsertTimerTable+168 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000100, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80001c94ff8, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001ec00e0
 0000000000000100 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiInsertTimerTable+168
fffff800`01c94ff8 0001            add     byte ptr [rcx],al

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff80001b7a370 -- (.trap 0xfffff80001b7a370)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000100 rbx=0000000000000000 rcx=0000000000000100
rdx=fffffa80077c90e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001c94ff8 rsp=fffff80001b7a500 rbp=0000000000000001
 r8=fffffa80077c90a0  r9=0000000000000032 r10=fffff80001e02e80
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
nt!KiInsertTimerTable+0x168:
fffff800`01c94ff8 0001            add     byte ptr [rcx],al ds:0001:00000000`00000100=??
Resetting default scope

MISALIGNED_IP: 
nt!KiInsertTimerTable+168
fffff800`01c94ff8 0001            add     byte ptr [rcx],al

LAST_CONTROL_TRANSFER:  from fffff80001c87b29 to fffff80001c885c0

STACK_TEXT:  
fffff800`01b7a228 fffff800`01c87b29 : 00000000`0000000a 00000000`00000100 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`01b7a230 fffff800`01c867a0 : 00000000`00000000 fffffa80`077c90e0 fffff880`020a4180 fffff800`021fbb7f : nt!KiBugCheckDispatch+0x69
fffff800`01b7a370 fffff800`01c94ff8 : 00000000`00000001 fffff800`01d40fbc fffff800`00000007 fffffa80`00000000 : nt!KiPageFault+0x260
fffff800`01b7a500 fffff800`01c9211a : ffffffff`fffe7960 fffffa80`0a3dab60 fffff800`01b7a648 fffffa80`00000000 : nt!KiInsertTimerTable+0x168
fffff800`01b7a560 fffff800`01c93c1d : fffffa80`077c90e0 fffffa80`0a3dac68 fffffa80`0a3dac68 00000000`00000000 : nt!KiTimerWaitTest+0x15a
fffff800`01b7a5e0 fffff800`01c9434e : 0000000c`50178c7c fffff800`01b7ac58 00000000`00052c31 fffff800`01e058a8 : nt!KiProcessExpiredTimerList+0x6d
fffff800`01b7ac30 fffff800`01c93b57 : 00000004`51e2eec3 00000004`00052c31 00000004`51e2ee0c 00000000`00000031 : nt!KiTimerExpiration+0x1be
fffff800`01b7acd0 fffff800`01c90d8a : fffff800`01e02e80 fffff800`01e10c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`01b7ad80 00000000`00000000 : fffff800`01b7b000 fffff800`01b75000 fffff800`01b7ad40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiInsertTimerTable+168
fffff800`01c94ff8 0001            add     byte ptr [rcx],al

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiInsertTimerTable+168

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

If you are overclocking anything, please stop.

Possible causes are Memory problems... Viruses... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Drivers...
Thanks to JMH for helping with my understanding of this crash.

Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors. Post back if it continues to show errors after the third run or if the first run comes back with no integrity violations.
Check for viruses.

Download and install the free version of Malwarebytes : Free anti-malware, anti-virus and spyware removal download (do not start the trial) and make sure it is updated. Do not run a scan yet.
Download VIPRE Rescue - VIPRE Computer Recovery Solution from Sunbelt Software but do not unzip it yet
Download the Fakerean removal tool but do not run it yet.
Start your computer in Safe Mode
Unzip VIPRE Rescue and let it run.
Run a full scan with Malwarebytes.
Run the fakerean removal tool.
Install all Windows Updates.
An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:

a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.

Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.

Also, update the following driver.

Code:

ALSysIO64	fffff880`0e77d000	fffff880`0e785000	Sun Apr 19 13:41:04 2009 (49eb7e50)	0000bbad		ALSysIO64.sys

You may use the following sites as references for finding drivers. We recommend finding the manufacturer of the driver and downloading drivers directly from the manufacturer or software developer. If you have trouble finding a driver or driver manufacturer, let us know and we will do our best to assist you. If you need help, please provide the device name, manufacturer, and the driver .sys file that you are looking for.

Driver Reference is a good site to find the driver .sys files, their descriptions, and the site most likely to contain an update.
Driver Search Methods provides driver manufacturers and links to their homepages.

There are a few methods for updating drivers.

To fully re-install a driver, use the following steps.

Click Start Menu
Right Click My Computer/Computer
Click Manage
Click Device Manager from the list on the left
Find the device you are trying to uninstall by expanding the appropriate set of devices
Right click the device
Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer
Install the latest driver for the device once Windows starts.

Alternatively:

Login as an adminstrative user.
Click Start Menu
Click Control Panel
Click Hardware and Sound
Click Device Manager (the last link under Devices and Printers)
Find the device you are trying to uninstall by expanding the appropriate set of devices
Right click the device
Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer
Install the latest driver for the device once Windows starts.