BSOD Multiple causes, constant

BT99 · 20 May 2013

Crashes very frequently, minutes apart, sometimes longer interval, apparently random. Have run Memtest86 overnight with no report of memory issues after multiple passes. Nvidia 7300 LE drivers updated. Tried and removed various antivirus programs with no change with or with or without. Even replaced power supply. Have attempted update of various drivers via Device Manager web search.

The affected HP Media Center m7463w computer worked fine (had Vista installed) before I replaced it with another computer to manage media. The HP was in hibernation (off/unplugged) for several months. When I revived it, power supply did not work. I replaced it and began experiencing the BSOD with Vista. Replaced power supply again. No change. Upgraded to Windows 7 Home Premium. No improvement.

I check BlueScreenView frequently but nothing seems obvious to me. Would greatly appreciate help. Thank you.

koolkat77 · 20 May 2013

Hi BT99.

Dump output:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 86b4d024, b2000000, 1040080f}

Probably caused by : GenuineIntel

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: 00000000, Machine Check Exception
Arg2: 86b4d024, Address of the WHEA_ERROR_RECORD structure.
Arg3: b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 1040080f, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  setiathome_6.0

CURRENT_IRQL:  1f

STACK_TEXT:  
807c98ac 82e10fcd 00000124 00000000 86b4d024 nt!KeBugCheckEx+0x1e
807c98e8 82f0a7ec 86b4b871 86b4d024 82eb0770 hal!HalBugCheckSystem+0xab
807c9918 82e1127f 86b50a20 82e1ee40 00000000 nt!WheaReportHwError+0x230
807c9a2c 82e11371 86b50a20 86b50a70 00000002 hal!HalpMcaReportError+0x3b
807c9a50 82e1148d 00000000 86b50a70 00000000 hal!HalpMceHandler+0x8b
807c9a70 82e115d6 00000000 86b50a20 807c9b90 hal!HalpMceHandlerWithRendezvous+0x4b
807c9a80 82e075f5 00000000 00000000 00000000 hal!HalpHandleMachineCheck+0x34
807c9b90 82e04261 00000000 807c4750 00000000 hal!HalpMcaExceptionHandler+0x87
807c9b90 00000000 00000000 807c4750 00000000 hal!HalpMcaExceptionHandlerWrapper+0x89


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_BUS

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

1: kd> !errrec 86b4d024
===============================================================================
Common Platform Error Record @ 86b4d024
-------------------------------------------------------------------------------
Record Id     : 01ce550354d80d53
Severity      : Fatal (1)
Length        : 1136
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 5/20/2013 2:48:51 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ 86b4d0a4
Section       @ 86b4d17c
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x86
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000000f62
Processor ID  : 0x0000000000000001

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ 86b4d0ec
Section       @ 86b4d23c
Offset        : 536
Length        : 336
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000001
CPU Id        : 62 0f 00 00 00 08 02 01 - 3d e4 00 00 ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ 86b4d23c

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ 86b4d134
Section       @ 86b4d38c
Offset        : 872
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : BUSLG_SRC_ERR_*_NOTIMEOUT_ERR (Proc 1 Bank 0)
  Status      : 0xb20000001040080f

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Tip

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 124 Troubleshooting Strategy

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "msinfo32 /nfo %USERPROFILE%\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back. Then zip up the .nfo file and upload/attach the .zip file with your next post.

systeminfo:
Please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "systeminfo.exe >%USERPROFILE%\Desktop\systeminfo.txt" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the syteminfo.txt file. If you have difficulties with making this work, please post back. Then zip up the .txt file and upload/attach the .zip file with your next post.

Next time you get a bsod, please upload ALL the files following the posting instructions.

BT99 · 20 May 2013

Koolcat77. Thank you.

Attaching the two zipped files requested. Please let me know if incorrect or I'm missing anything.

BT99

koolkat77 · 20 May 2013

Thanks.

Have you checked for a BIOS update?

Code:

BIOS Version/Date	Phoenix Technologies, LTD 3.17, 9/15/2006

For monitoring heat of the system, use Speccy or HWMonitor

BT99 · 20 May 2013

Koolkat77,

Were a couple more BSOD and this time I think I have the complete SF files zipped.

BT99

BT99 · 20 May 2013

I have checked the HP site for a bios update without success. I've checked using the original OS, Vista, and the Win7 options. Using the Vista option on the HP support site and for the specific model computer I have several driver update options but no bios updates offered. Selecting the Win7 option (my current OS), only the Lightscribe driver is offered and no bios updates. According to the HP site, if there are no options for bios updates, you likely have the most current.

Note: in addition to the new power supply, other hardware changes have been minor (removal of two V-Box DTA 150 cards (no drivers for Windows 7) - I'm not using the HP as a media center any more. I've disabled (today) the drivers for the Hauppaugh Win TV tuner card. No effect.

I'll check the heat.

x BlueRobot · 21 May 2013

Please update your System Specifications with Speccy, and then copy this information into your System Specifications: Go to your UserCP, and then select Edit System Spec in the left pane. Copy the information from Speccy into the required fields. These System Specifications will then follow your every post.

BT99 · 21 May 2013

Have updated my specs. But more importantly, things have changed with the computer. Can't be certain, but it appears the BSODs have abated. Here's what I did but cannot pin down what is the main cause for the change.

BIOS: Although the HP site would not allow (no options) me to update from Phoenix Technologies 3.17, 9/15/2006, at PT website support I was redirected to BiosAgentPlus ($30 for a year of updates for 10 computers) which found a Rev (3.19 12/08/2006). I installed but on reboot Windows would not load. Tried everything (repair, safe, recovery point etc.). Nothing, and I started searching for new MBs.

Windows 7 Clean Install: Then I attempted clean (new) Windows 7 install. Since then (a meager two hours ago) the system has been steady.

One thing is notably different on the Speccy temperature readings. I had installed Speccy just before the BIOS update. The temp for the graphics card then was 71/72C (in red). Other temps seemed reasonable. After reinstalling Speccy there is no temperature reading at all for the card. I presume that's a good thing.

Bottom line: I still don't know where the problem was or what single thing turned it around: new BIOS, clean install of Windows 7, or what.

Anyway, thanks for your attention to this. I have been plagued by this problem for months. I could not use the system for more than a few minutes before BSOD.

BT99

x BlueRobot · 21 May 2013

BT99 said:

One thing is notably different on the Speccy temperature readings. I had installed Speccy just before the BIOS update. The temp for the graphics card then was 71/72C (in red). Other temps seemed reasonable. After reinstalling Speccy there is no temperature reading at all for the card. I presume that's a good thing.

BT99

Why would that be a good thing?

Are you sure you flashed with the correct BIOS version?

It also seems you had clear overheating issues with your system, have you checked inside the case for any dust?

BT99 · 21 May 2013

Well, the reason for no temperature is I had not downloaded the GeForce 7300 drivers. That done, using
Speccy the graphics card shows 86 degrees C (red). The Motherboard at 40C, hard drives Western Digital 43 and Seagate 50 (red). The case is open and clean and the fan is working. What could be causing the high temp for the card? The 86 compares to 71 yesterday.

And the honeymoon was brief. I got another BSOD just as I was installing Java. No idea if there is a relationship, but I have not installed it to see if things stabilize.

Have reinstalled BlueScreenView.