Windows 7: Hp dv9700 bsod

smacd · 06 Aug 2012

I recently repaired a broken HP DV9700 (hinge replacement), and following that I wiped the hard drive and installed a new copy of Windows 7 professional (64bit). Turns out that HP doesn't support Windows 7 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 Windows 7 with vista)?

**HonorGamer** · 07 Aug 2012

Hello,

Try running the SF Diag Tool in Safe mode by pressing F8 on start up.

But from that dump file do the following in Safe mode with networking:

Quote:

BugCheck 0x124

Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!

For your hardware stop 0x124 crash, read through Stop 0x124 - what it means and what to try and use the following hardware checks to supplement that link.

If you are overclocking any hardware, please stop.

If you have an SSD, make sure the following are up to date:
SSD firmware

BIOS Version

Chipset Drivers

Hard disk controller drivers/SATA drivers

If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Run all but the advanced tests with SeaTools for HDDs.
SeaTools for Windows

SeaTools for DOS

Monitor temperatures during the following tests.
Use the following programs to monitor the temperatures.
Real Temp is a good CPU temperature monitor.

Speccy - System Information - Free Download will monitor all hardware temperatures.

HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.

Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.

Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.

Follow the steps for doing CPU stress test using IntelBurnTest

Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
Shut down and turn off your computer.

Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)

Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.

Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.

Once these steps have been followed, it is safe to remove and replace components within your computer.

Coutesy of: writhziden

-Justin

smacd · 08 Aug 2012

Thanks for the info Justin.

So at this point, this laptop is either hanging on a blinking cursor, or screen-scrambling after the BIOS screen and prior to Windows loading. I managed to get in on safety mode once, but the moment after I opened Chrome the screen scrambled.

I know this model and this laptop does have an issue with overheating, and I'm definitely not overclocking. It looks like the BIOS is two versions out of date, but trying to flash it with this rapid random BSOD seems like a good way to end up with a bricked motherboard. I don't think I'll be able to pull off any more than the 5 or so minidumps I managed to get off there a few weeks ago (which I'm guessing show the same thing in each). Is there nothing else to go on from the minidump analysis that might help me figure out how to resolve this?

Windows 7: Hp dv9700 bsod

Hp dv9700 bsod problems?