Thread: Hp dv9700 bsod
View Single Post
06 Aug 2012  
smacd

Windows 7 Professional 64bit
 
 
Hp dv9700 bsod

I recently repaired a broken HP DV9700 (hinge replacement), and following that I wiped the hard drive and installed a new copy of win7 professional (64bit). Turns out that HP doesn't support win7 for this laptop, only vista. Besides the wireless, sound and cdrom sometimes detected and sometimes not, the biggest problem is that completely randomly (anywhere from 2 seconds to hours later from initial power-on) the screen will appear to scramble, and I need to hard shutdown the machine. When I reboot, it tells me that it was a BSOD. I've heard there are driver issues, but haven't found any real solution to it yet.

Below is the results from windbg for one of the minidump files:


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


Loading Dump File [D:\C DRIVE BACKUP\desktop\Minidump\073012-23977-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are 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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02a5c000 PsLoadedModuleList = 0xfffff800`02ca0670
Debug session time: Mon Jul 30 08:31:45.835 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:07.676
Loading Kernel Symbols
...................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004d05038, 0, 0}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004d05038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02fee6f0 fffff800`02d1dca9 : fffffa80`04d05010 fffffa80`039f7040 00000000`00000004 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02feec10 fffff800`02bfe547 : fffffa80`04d05010 fffff800`02c782d8 fffffa80`039f7040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02feec40 fffff800`02b65945 : fffff800`02cd9ae0 00000000`00000001 fffffa80`0475f150 fffffa80`039f7040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02feec80 fffff800`02ae4841 : fffff880`01067e00 fffff800`02b65920 fffffa80`039f7000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02feecb0 fffff800`02d71e6a : 00000000`00000000 fffffa80`039f7040 00000000`00000080 fffffa80`039e5040 : nt!ExpWorkerThread+0x111
fffff880`02feed40 fffff800`02acbec6 : fffff880`009eb180 fffffa80`039f7040 fffff880`009f5f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02feed80 00000000`00000000 : fffff880`02fef000 fffff880`02fe9000 fffff880`02fede80 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV

Followup: MachineOwner
---------
I did see the SF Diagnostic Tool, however I currently cannot keep the system running long enough to use it, only about 10 seconds after windows finishes loading, for a few weeks now.

Any tips on how to resolve this (other than replacing win7 with vista)?
My System SpecsSystem Spec