Sign in with
Sign up | Sign in
Your question

Anyone able to help with BSOD (have dump)

Last response: in Windows 7
Share
December 11, 2012 5:31:46 PM

Just want to understand what caused it. Thanks

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`03203000 PsLoadedModuleList = 0xfffff800`03447670
Debug session time: Tue Dec 11 14:03:54.268 2012 (UTC - 5:00)
System Uptime: 0 days 3:59:40.845
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols

Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff87fc41850c4, d, 1, fffff8000328d3b3}

Probably caused by : ntkrnlmp.exe ( nt!KiSecondaryClockInterrupt+1c3 )

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

2: 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: fffff87fc41850c4, memory referenced
Arg2: 000000000000000d, 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: fffff8000328d3b3, address which referenced memory

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


WRITE_ADDRESS: fffff87fc41850c4

CURRENT_IRQL: d

FAULTING_IP:
nt!KiSecondaryClockInterrupt+1c3
fffff800`0328d3b3 4da9440f22c1 test rax,0FFFFFFFFC1220F44h

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80003281fc0

STACK_TEXT:
00000000`000286a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!KiSecondaryClockInterrupt+1c3
fffff800`0328d3b3 4da9440f22c1 test rax,0FFFFFFFFC1220F44h

SYMBOL_NAME: nt!KiSecondaryClockInterrupt+1c3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be

FAILURE_BUCKET_ID: X64_0xA_nt!KiSecondaryClockInterrupt+1c3

BUCKET_ID: X64_0xA_nt!KiSecondaryClockInterrupt+1c3

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

More about : bsod dump

a b $ Windows 7
December 11, 2012 6:55:25 PM

Well most BSOD's are RAM or driver related, voltage ant thermal may also be the cause. I would start with running memtest over night. Update drivers and monitor your temps and voltage with speedfan.
!