I left my laptop on last night, and in the morning I saw the error message saying "System Has Recovered from a Serious Error".
I have been using Windows 7 Ultimate since 2 months and this is the first time I got BSOD. Prior to Windows 7, I was using Vista Ultimate but I formatted my harddisk and installed from scratch. I haven't recieved a BSOD since I had this laptop. What should cause this error?
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: f4
BCP1: 00000003
BCP2: 878C4D40
BCP3: 878C4EAC
BCP4: 82C3AD50
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\123009-18064-01.dmp
C:\Users\Serkan\AppData\Local\Temp\WER-38797-0.sysdata.xml
Read our privacy statement online:
Windows 7 Privacy Highlights - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Hi and welcome
First drivers from 2001 thru 2006. these need to be updated.
Code:
register.sys 0x90c5a000 0x90c5a600 0x00000600 0x3c03f058 11/27/2001 2:58:16 PM
secdrv.SYS 0x981e0000 0x981ea000 0x0000a000 0x45080528 9/13/2006 8:18:32 AM
irsir.sys 0x90d71000 0x90d7c000 0x0000b000 0x479190c9 1/19/2008 12:55:21 AM
Second this crash was caused by hardware probably memory so I would download memtest and run it for 5 passes
Ken J+
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\123109-12355-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82817000 PsLoadedModuleList = 0x8295f810
Debug session time: Wed Dec 30 20:09:51.346 2009 (GMT-5)
System Uptime: 0 days 2:45:53.453
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {1, 1c, 1, 82882340}
Probably caused by : hardware ( amdk8!C1Halt+4 )
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: 00000001, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000001, 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: 82882340, address which referenced memory
Debugging Details:
------------------
WORKER_ROUTINE:
+59e9952f00e5dd14
00000001 ?? ???
WORK_ITEM: 82882340
CURRENT_IRQL: 1c
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: 8293db1c -- (.trap 0xffffffff8293db1c)
ErrCode = 00000002
eax=00000001 ebx=00002710 ecx=0001926a edx=00000000 esi=82940d20 edi=82942654
eip=82882340 esp=8293db90 ebp=8293dbb8 iopl=0 nv up ei pl nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010213
nt!KeUpdateRunTime+0x143:
82882340 0000 add byte ptr [eax],al ds:0023:00000001=??
Resetting default scope
MISALIGNED_IP:
nt!KeUpdateRunTime+143
82882340 0000 add byte ptr [eax],al
LAST_CONTROL_TRANSFER: from 82882340 to 8285d7eb
STACK_TEXT:
8293db1c 82882340 badb0d00 00000000 00000000 nt!KiTrap0E+0x2cf
8293dbb8 828821ef 90d56bb6 2f6ddb62 00000000 nt!KeUpdateRunTime+0x143
8293dc14 82887577 86e19102 86e19102 000000d1 nt!KeUpdateSystemTime+0x613
8293dc14 90d56bb6 86e19102 86e19102 000000d1 nt!KeUpdateSystemTimeAssist+0x13
8293dc98 8289c695 85074d48 8294a280 82940c00 amdk8!C1Halt+0x4
8293dd20 8287f00d 00000000 0000000e 00000000 nt!PoIdle+0x538
8293dd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd
STACK_COMMAND: kb
FOLLOWUP_IP:
amdk8!C1Halt+4
90d56bb6 c3 ret
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: amdk8!C1Halt+4
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
---------
Quote