BSOD Win7 64bit. Help!!

D

Dans16

Member
Joined
Sep 8, 2013
Posts
8
Location
FNC, Australia
Hi guys, I hope someone can help, this BSOD is driving me crazy..

I have been experiencing the dreaded BSOD recently whilst trying to relax playing BF3.


I updated my GPU drivers, then the crashes started.. I reverted back to the drivers I knew worked but it is still crashing.. I usually get 10mins into a game and its crashes.. sometimes following through into a BSOD.

I rarely play PC games, my usual PC usage is fine and never get a BSOD while using windows or my trading platforms, I tried many things to rectify the problem.



I scanned for viruses and malware, using Superantispyware, Malware bytes and Combofix. I have tried to clean the registry with CCcleaner. I have run HDD tests and memtest86. I have tried changing the Video card into the other PCi-e slot, I have cleaned the PC of dust.

I have stress tested the GPU with 3dmarks 11 and run it on extreme for 2 hours on loop. The GPU doesn't overheat and also my CPU doesn't over heat. Northbridge is hot but I heard the NB usually runs hot in a Rampage ii Gene motherboard.

I have attached the files needed, I will now go and play bf3 with Verifier enabled to create a fresh dump file.

Many thanks to whoever has a crack at diagnosis.
 
Hi,

In regards to the perfmon:

The device, Photosmart C7100 series, is disabled. If this device is no longer used it may be intentionally disabled. The Plug and Play ID for this device is ROOT\MULTIFUNCTION\0000.
Click to expand...

Is this disabled on purpose?

In regards to the DMP files, it seems the jcgriff app failed to collect any. Can you please manually navigate to your Minidump folder (%systemroot%\Minidump) and zip and attach here?

Regards,

Patrick
 
Hi,

The attached DMP file is 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 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8006f32a08
Section       @ fffffa8006f32b90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

[I][COLOR=#ff0000][U][B]Error         : Internal timer (Proc 0 Bank 5)[/B][/U][/COLOR][/I]
  Status      : 0xbe00000000800400
  Address     : 0x00003880050c57a9
  Misc.       : 0x0000000000007fff

It seems we have an internal CPU timer failing. As we only have one dump it's not possible to check for consistency, but it's occurring in Processor 0 (first and primary core) and Cache Bank 5.

MODULE_NAME: hardware

IMAGE_NAME: hardware

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

^^ ^^ Implies that this was very much NOT caused by any sort of software complication (drivers, etc) but hardware... processor cache also furthers our diagnosis in the CPU itself (L1 Cache) possibly being faulty.

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. If all of the above fail, the only left to do is replace your processor as it is faulty.

Regards,

Patrick
 
Hi Patrick,

I uninstalled all Asus and related software, reset Bios to default settings.. the only other thing I can try is maybe updating Bios version, though Im pretty sure its ok as I flashed it a while back.

I ran intel CPU test, with no error. I have another Dump file created today, is it unusual for a faulty CPU to only crash under certain conditions?


Is it possible to check this dumpfile and see if its the same error?


Thank you so much for all your help!! :)
 

Attachments

Great work, and yes, here are the dump results:

Code: 
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8006f98a08
Section       @ fffffa8006f98b90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

[COLOR=#ff0000][U][I][B]Error         : Internal timer (Proc 0 Bank 5)[/B][/I][/U][/COLOR]
  Status      : 0xfe00000000800400
  Address     : 0x000038800508b7a9
  Misc.       : 0x0000000000007fff

Exact same as above, so we can now mold consistency into the equation as well. It's looking more and more like a faulty CPU to me.

Regards,

Patrick
 
Thanks a lot Patrick, Im now trying to source a new CPU for my outdated 1366 socket. lol.

Many thanks, I will post back once I install new CPU :)
 
Hi Patrick, I upgraded and installed new CPU (i7 720 3.2g)

Unfortunately the crashes are still happening.. oh noes!

I have attached new minidumps, one with verifier enabled and the other standard...



Can this issue also be caused by Motherboard error seeing its a CPU issue?
 

Attachments

Hi -

Both of the latest dumps had bugcheck 0x124, which is a machine check exception -- hardware failure.

System uptimes were 6-9 seconds before BSOD -
Code: 
[font=lucida console]
System Uptime: 0 days 0:00:08.860
System Uptime: 0 days 0:00:06.692
[/font]

Unfortunately, the dumps are not capable of telling us the exact piece of hardware that is failing/ has failed.

mobo, PSU, RAM, etc... are all suspect.

Apologies that I cannot provide further information to help you at this time.

Regards. . .

jcgriff2

Code: 
[font=lucida console]
Loading Dump File [C:\Users\x1\_jcgriff2_\dbug\__Kernel__\091713-17440-01.dmp]
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Mon Sep 16 23:07:51.410 2013 (UTC - 4:00)
System Uptime: 0 days 0:00:08.860
Probably caused by : GenuineIntel
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`074a9038 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\x1\_jcgriff2_\dbug\__Kernel__\091713-15802-01.dmp]
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Mon Sep 16 22:36:10.304 2013 (UTC - 4:00)
System Uptime: 0 days 0:00:06.692
Probably caused by : GenuineIntel
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`068f4038 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]
 
No, not really.

The system is crashing in under 8 seconds after boot-up.

Have you tried to reinstall Windows?

Given new CPU, it is probably a good idea.
 
Hi,

In the new dumps, nothing has changed since post #4's analysis.

Possible motherboard failure now since the CPU has been replaced. I would recommend also reinstalling Windows as John suggested just in case. Also, you can run a 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

Regards,

Patrick
 

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

Back
Top