Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\Kingston\BSODDmpFiles\jainmohit\Windows_NT6_BSOD_jcgriff2\020512-49327-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x8321c000 PsLoadedModuleList = 0x833654d0
Debug session time: Sun Feb 5 06:41:30.498 2012 (GMT-7)
System Uptime: 0 days 0:01:51.730
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {ff630817, 1c, 8, ff630817}
Probably caused by : amdk8.sys ( amdk8!C1Halt+4 )
Followup: MachineOwner
---------
0: 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: ff630817, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: ff630817, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 83385848
Unable to read MiSystemVaType memory at 83364e20
ff630817
CURRENT_IRQL: 1c
FAULTING_IP:
+62c3952f0396d9f8
ff630817 ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: 83343ba8 -- (.trap 0xffffffff83343ba8)
ErrCode = 00000010
eax=8b63ed00 ebx=00000000 ecx=00000000 edx=000000d1 esi=eec83e87 edi=92504bb6
eip=ff630817 esp=83343c1c ebp=83343c28 iopl=0 nv up ei ng nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287
ff630817 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from ff630817 to 8325d5fb
FAILED_INSTRUCTION_ADDRESS:
+62c3952f0396d9f8
ff630817 ?? ???
STACK_TEXT:
83343ba8 ff630817 badb0d00 000000d1 83343c14 nt!KiTrap0E+0x2cf
WARNING: Frame IP not in any known module. Following frames may be wrong.
83343c18 83630794 00000802 000000d1 83343d20 0xff630817
83343c18 92504bb6 00000802 000000d1 83343d20 hal!HalpHpetClockInterrupt+0x160
83343c98 8329c37f 886494c8 83350380 83346c00 amdk8!C1Halt+0x4
83343d20 83293e0d 00000000 0000000e 00000000 nt!PoIdle+0x524
83343d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd
STACK_COMMAND: kb
FOLLOWUP_IP:
amdk8!C1Halt+4
92504bb6 c3 ret
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: amdk8!C1Halt+4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: amdk8
IMAGE_NAME: amdk8.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf07
FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_amdk8!C1Halt+4
BUCKET_ID: 0xD1_CODE_AV_BAD_IP_amdk8!C1Halt+4
Followup: MachineOwner
---------
Please fill out your system specs using System Info - See Your System Specs use steps 1-4 to get the specs and step 5 to fill them out.
If there are any BIOS updates for your system, I would suggest this first since the driver being blamed in the crash is related to your processor. Processors do not fail often, so it is best to do troubleshooting steps to determine other possible causes first. Given the age of your BIOS version,
Code:
BIOS Version/Date Phoenix Technologies, LTD 5.05, 4/18/2007
this seems like a good place to start.
Also, do you have ZoneAlarm on your system?