 | |
| |
| 10 Sep 2010 | #1 |
| | BSOD on Start - able to start in Safe Mode and Restore Windows 7 Home Premium 64-bit on Dell XPS 8100 with Intel Core i5, 650@3.20 GHz, 8Gb RAM, worked flawlessly out of the box in April (for five months). For a few weeks, powering off had produced "Installing Windows Updates, 1 (etc) of 8" - each and every time. Two days ago, power on results in normal system start until Windows Log In screen, which lasts about 2 seconds; then monitor displays all sorts of pretty colors. Left alone, the system restarts and ends in Black Screen with Start options; Start in Safe Mode works fine. System Restore works fine. But, removing power and starting again (cold) repeats above performance. Have attached zip file of Windows_NT6_BSOD_jcgriff2; but could not figure out how to include a Performance Monitor Report (no User Defined, or System reports shown). |
My System Specs | |
| 11 Sep 2010 | #2 |
| | 
Quote: Originally Posted by peteinkent  Windows 7 Home Premium 64-bit on Dell XPS 8100 with Intel Core i5, 650@3.20 GHz, 8Gb RAM, worked flawlessly out of the box in April (for five months). For a few weeks, powering off had produced "Installing Windows Updates, 1 (etc) of 8" - each and every time. Two days ago, power on results in normal system start until Windows Log In screen, which lasts about 2 seconds; then monitor displays all sorts of pretty colors. Left alone, the system restarts and ends in Black Screen with Start options; Start in Safe Mode works fine. System Restore works fine. But, removing power and starting again (cold) repeats above performance. Have attached zip file of Windows_NT6_BSOD_jcgriff2; but could not figure out how to include a Performance Monitor Report (no User Defined, or System reports shown). These were both caused by hardware. Please read these to find out what it means and what to try 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 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\Windows_NT6_BSOD_jcgriff2\042510-17862-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
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 Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c0e000 PsLoadedModuleList = 0xfffff800`02e4be50
Debug session time: Sun Apr 25 19:00:39.186 2010 (GMT-4)
System Uptime: 0 days 0:03:34.684
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc000001d, fffff80002c704c9, 0, fffff70001080400}
Probably caused by : hardware ( nt!MiIssueHardFault+329 )
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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80002c704c9, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: fffff70001080400, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
FAULTING_IP:
nt!MiIssueHardFault+329
fffff800`02c704c9 44 ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: fffff70001080400
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
EXCEPTION_RECORD: fffff8800ada57b8 -- (.exr 0xfffff8800ada57b8)
ExceptionAddress: fffff80002c704c9 (nt!MiIssueHardFault+0x0000000000000329)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
TRAP_FRAME: fffff8800ada5860 -- (.trap 0xfffff8800ada5860)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000114 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000200 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c704c9 rsp=fffff8800ada59f0 rbp=fffff8800ada5a60
r8=fffffa800e7659c8 r9=fffffa80040ff9b0 r10=fffff70001080488
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!MiIssueHardFault+0x329:
fffff800`02c704c9 44 ???
Resetting default scope
MISALIGNED_IP:
nt!MiIssueHardFault+329
fffff800`02c704c9 44 ???
LAST_CONTROL_TRANSFER: from fffff80002cb8929 to fffff80002c7e600
FAILED_INSTRUCTION_ADDRESS:
nt!MiIssueHardFault+329
fffff800`02c704c9 44 ???
STACK_TEXT:
fffff880`0ada4fe8 fffff800`02cb8929 : 00000000`0000001e ffffffff`c000001d fffff800`02c704c9 00000000`00000000 : nt!KeBugCheckEx
fffff880`0ada4ff0 fffff800`02c7dc42 : fffff880`0ada57b8 00000000`00000000 fffff880`0ada5860 fffffa80`0b3b4660 : nt!KiDispatchException+0x1b9
fffff880`0ada5680 fffff800`02c7bd9f : fffff880`0ada5860 fffffa80`00401800 fffff880`0ada5a00 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0ada5860 fffff800`02c704c9 : 00000003`00000000 00000000`00000000 fffff880`0ada5a60 fffffa80`0b3b4660 : nt!KiInvalidOpcodeFault+0x11f
fffff880`0ada59f0 fffff800`02c9979b : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff800`00000000 : nt!MiIssueHardFault+0x329
fffff880`0ada5ac0 fffff800`02c7c6ee : 00000000`00000008 00000000`ffffffff fffffa80`0e765601 00000000`00000001 : nt!MmAccessFault+0x14bb
fffff880`0ada5c20 000007fe`f4ecd7b0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0ae1d568 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`f4ecd7b0
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiIssueHardFault+329
fffff800`02c704c9 44 ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nt!MiIssueHardFault+329
FOLLOWUP_NAME: MachineOwner
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_NAME: hardware
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
--------- old drivers needing updating Code: OA002Afx.sys fffff880`03eb3000 fffff880`03ee6f80 0x00033f80 0x46690ca4 6/8/2007 04:00:36 OA002Ufd.sys fffff880`05637000 fffff880`056603a0 0x000293a0 0x48450f3d 6/3/2008 05:30:37 OA002Vid.sys fffff880`03e68000 fffff880`03eb2d80 0x0004ad80 0x4892d8bc 8/1/2008 05:34:52 Mpfp.sys fffff880`0418c000 fffff880`041c9000 0x0003d000 0x49de3cd5 4/9/2009 14:22:13 spldr.sys fffff880`01677000 fffff880`0167f000 0x00008000 0x4a0858bb 5/11/2009 12:56:27 amdxata.sys fffff880`01235000 fffff880`01240000 0x0000b000 0x4a12f2eb 5/19/2009 13:56:59 athrx.sys fffff880`05038000 fffff880`051a6000 0x0016e000 0x4a2997be 6/5/2009 18:10:06 PxHlpa64.sys fffff880`012a0000 fffff880`012abe00 0x0000be00 0x4a416253 6/23/2009 19:16:35 |
| My System Specs |
| 11 Sep 2010 | #3 |
| | Welcome! Start by installing this Atheros driver: Drivers and Downloads Next, remove McAfee with this tool: http://download.mcafee.com/products/...tches/MCPR.exe Replace it with MSE: http://www.microsoft.com/security_essentials ...Summary of the Dumps: Code:
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jul 6 20:34:18.936 2010 (UTC - 4:00)
System Uptime: 0 days 0:07:46.434
BugCheck D1, {10, 2, 0, fffff880016c55d6}
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+2e297 )
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Apr 25 19:00:39.186 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:34.684
BugCheck 1E, {ffffffffc000001d, fffff80002c704c9, 0, fffff70001080400}
Probably caused by : hardware ( nt!MiIssueHardFault+329 )
BUGCHECK_STR: 0x1E_c000001d
PROCESS_NAME: svchost.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии |
| My System Specs |
| . |
| |
 |
BSOD on Start - able to start in Safe Mode and Restore problems?
| Thread Tools | |
| Similar help and support threads for: BSOD on Start - able to start in Safe Mode and Restore | ||||
| Thread | Forum | |||
| BSOD after I start the computer even in Safe Mode | BSOD Help and Support | |||
| BSOD 0x000000f4 on start up/safe mode too | BSOD Help and Support | |||
| BSOD during startup for normal mode. Can only start in safe mode. | BSOD Help and Support | |||
| BSOD during boot - cannot start even in safe mode | BSOD Help and Support | |||
| BSOD after start up, even in safe mode | BSOD Help and Support | |||
All times are GMT -5. The time now is 04:11 PM.
