BSOD - Need help!! - Windows 7 x86

N

ninerbubs30

New member
Joined
Feb 17, 2014
Posts
2
Hi,

My desktop has been BSOD multiple times a day and restarting. Below are the specs to my desktop. I have attached the zip file as requested. The perfmon is inside the zip file. Any help would be appreciated. If there is any other information I am missing, please let me know.

Thanks,
ninerbubs30

View attachment Windows7_Vista_jcgriff2.zip

OS - Windows 7
· x86 32-bit
· What was original installed OS on system? Original OS was Windows XP
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? OEM, already installed on system.
· Age of system (hardware) Purchased in 2006, upgraded the video card in 2008
· Age of OS installation - have you re-installed the OS? I just recently upgraded the OS to Windows 7 from XP, hoping that would resolve the BSOD issue, which it did not.

· CPU Intel Pentium D CPU 3.00 GHz Dual Processors
· Video Card NVidia GeForce GTS 250
· MotherBoard HP Pavilion 061 ASUS Emery
· Power Supply - brand & wattage (if laptop, skip this one) Antec 750 Watt Output, this is an upgraded power supply, since the original one stopped working.

· System Manufacturer Hewlett Packard
· Exact model number (if laptop, check label on bottom) HP Media Center PC m7367c

· Laptop or Desktop? Desktop
 
Hi,

All of the attached DMP files are of the WHEA_UNCORRECTABLE_ERROR (124) bugcheck.

A fatal hardware error has occurred. This fatal error displays data from the Windows Hardware Error Architecture (WHEA).

If we run an !errrec on the 2nd parameter of the bugcheck (address of the WER structure) we get the following:

Code: 
===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ 888840a4
Section       @ 8888417c
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x86
[COLOR=#ff0000][I][B]Error Type    : BUS error[/B][/I][/COLOR]
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000000f62
Processor ID  : 0x0000000000000001

Code: 
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ 88884134
Section       @ 8888438c
Offset        : 872
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

[COLOR=#ff0000][I][B]Error         : BUSLG_SRC_ERR_*_NOTIMEOUT_ERR (Proc 1 Bank 0)[/B][/I][/COLOR]
  Status      : 0xb20000001040080f

It appears there's a timeout on the BUS of the CPU.

-- PROCESS_NAME: AvastSvc.exe

^^ Related to avast!
Remove and replace avast! with Microsoft Security Essentials for temporary troubleshooting purposes:

avast! removal - avast! Uninstall Utility | Download aswClear for avast! Removal

MSE - Microsoft Security Essentials - Microsoft Windows
Click to expand...

-- hcwPP2.sys Tue Feb 06 13:27:02 2007

^^ Huappage WinTV PVR Video Capture - Hauppauge Computer Works Support Product Selector

-- pnp680.sys Tue Nov 13 14:26:50 2007

^^ SiI 680 ATA Controller - Host Controllers, SiI3531, SiI3512, SiI3132, SiI3124, SiI3114

-- e100b325 Fri Nov 16 13:53:32 2007

^^ Intel PRO/100 Adapter NDIS 5.1 driver - http://downloadcenter.intel.com/Default.aspx

Check for updates for these drivers, and if none are available, remove the device(s) and uninstall the software.


If the above fails, there is only so much you can do with a bugcheck like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:

1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - Speccy - System Information - Free Download

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - How To Clear CMOS (Reset BIOS)

3. Ensure your BIOS is up to date.

4. The only software conflict that can usually cause *124 bugchecks are OS to BIOS utilities from manufacturer's like Asus' AI Suite. If you have something like this software-wise, remove it ASAP.

5. Run Memtest for NO LESS than ~8 passes (several hours):

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

6. If all of the above fail, the only left to do is replace your processor as it is faulty.

Regards,

Patrick
 
Hi Patrick,

Thank you for the immediate and very thorough response. I will start with #1 and work my way down. I will let you know how it turns out.

Thanks again,
ninerbubs30
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top