BSoD help needed

iwantmoretacos · 17 Dec 2010

Hey guys, been getting BSoD on my computer for the last month or two, and it seems to be happening more frequently. Sometimes shortly after windows boots up, and all I do is open up Mozilla. Sometimes it takes an hour, sometimes 4.

I have made no changes to my system, hardware or anything since the day I bought it. I've run a registry repair thing that I think I found on this forum (sfc /scannow I think) and its all fine, apparently.

Files are attached in the Zip file as per the instructions.

Heres my system info:

Ultra XBlaster Mid-Tower Case
XFX GeForce 8200 MCP Socket AM2+ Motherboard
XFX GeForce 9600 GSO 768MB PCIe w/Dual Link DVI
AMD Phenom X4 9500 4M 95W Socket AM2 CPU
Thermaltake Ruby Orb CPU Cooler
HITACHI 1TB SERIAL ATA HD 7200/16MB/SATA-3G
Lite ON 22X DVDRW SATA OEM w/o Software
ULTRA LS500 500W ATX POWER SUPPLY
Kingston 2048MB PC5400 DDR2 667MHz CL5 (x4)

Built the machine myself and it ran perfect for nearly 2 years. I've updated the video card driver to the latest version as of yesterday. Thought that was it as I hadnt had a crash all day yesterday and all night, but today I got hit by that blasted BSoD again. I'm not very savvy with computer diagnosis and fixing problems or whatnot, so you hardcore folks might have to dummy down your talk a little. I know enough that I built the machine, installed the OS, the drivers that came with it all, and got it all working, but when it comes to crashes and stuff like this I'm at a loss.

Thanks for your help, this is ridiculously frustrating.

DeanP · 17 Dec 2010

Hi iwantmoretacos and welcome to Seven Forums!

I'm not sure whether it's coming from your AMD Processor. We'll just wait for the BSOD Experts to come.

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80077b6028, b601a000, 135}

Probably caused by : hardware

Followup: MachineOwner

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

BUGCHECK_STR: 0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

STACK_TEXT:
fffff880`02f6ca88 fffff800`02e30903 : 00000000`00000124 00000000`00000000 fffffa80`077b6028 00000000`b601a000 : nt!KeBugCheckEx
fffff880`02f6ca90 fffff800`02fed593 : 00000000`00000001 fffffa80`077b7d30 00000000`00000000 fffffa80`077b7d80 : hal!HalBugCheckSystem+0x1e3
fffff880`02f6cad0 fffff800`02e305c8 : 00000000`00000728 fffffa80`077b7d30 fffff880`02f6ce30 00000000`00000000 : nt!WheaReportHwError+0x263
fffff880`02f6cb30 fffff800`02e2ff1a : fffffa80`077b7d30 fffff880`02f6ce30 fffffa80`077b7d30 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02f6cc80 fffff800`02e23e8f : fffffa80`06cbd880 00000000`00000001 fffff880`02f6ceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02f6ccc0 fffff800`02ed5fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02f6ccf0 fffff800`02ed5e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02f6ce30 fffff800`02ee2d80 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`02f8c5e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiProcessExpiredTimerList+0x70

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE

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

Also, test your RAM with Memtest:
http://www.memtest.org/

Run at least 7 passes on a cold boot, to know everything about Memtest is here (Jonathan King's Tutorial):

RAM - Test with Memtest86+

Jonathan_King · 17 Dec 2010

DeanP gave some good advice. The only thing I can add is run Prime95: https://www.sevenforums.com/tutorials...t-prime95.html

...Summary of the dumps:

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Dec 17 18:04:47.802 2010 (UTC - 5:00)
System Uptime: 0 days 0:50:24.112
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Dec 15 18:49:07.409 2010 (UTC - 5:00)
System Uptime: 0 days 0:55:05.345
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Dec 15 05:14:07.070 2010 (UTC - 5:00)
System Uptime: 0 days 1:09:43.396
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Dec 15 04:03:41.288 2010 (UTC - 5:00)
System Uptime: 0 days 0:21:54.597
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Dec 15 03:40:37.046 2010 (UTC - 5:00)
System Uptime: 0 days 2:54:28.981
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Dec 14 02:13:02.959 2010 (UTC - 5:00)
System Uptime: 0 days 3:08:50.284
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Dec 13 23:03:09.213 2010 (UTC - 5:00)
System Uptime: 0 days 1:59:18.149
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Dec 13 21:03:07.413 2010 (UTC - 5:00)
System Uptime: 0 days 5:30:06.723
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Dec 13 15:32:16.773 2010 (UTC - 5:00)
System Uptime: 0 days 0:35:06.099
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Dec 13 03:39:12.115 2010 (UTC - 5:00)
System Uptime: 0 days 1:46:34.051
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Dec 13 01:51:54.241 2010 (UTC - 5:00)
System Uptime: 0 days 2:41:44.176
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

iwantmoretacos · 18 Dec 2010

Ok, so I downloaded SpeedFan 4.42 and checked tempuratures. Everything is normal except the GPU and AUX, which are running ar around 42C and 48C respectively.

What are normal tempuratures for everything? The window shows that when anything gets to about 50C a little fire icon appears next to it, yet chatting to some friends they say that 50-60 is totally normal for a GPU. A buddy said his GPU would hit 90C before it crashed his comp.

Thoughts?

DeanP · 18 Dec 2010

I'm no hardware expert, but I would suggest that you test your RAM for errors with memtest. Run at least 7 passes overnight, on a cold boot. As Jonathan Said, run Prime95.

Memtest:
Memtest86+ - Advanced Memory Diagnostic Tool

Memtest Tutorial:
RAM - Test with Memtest86+

Prime 95:
https://www.sevenforums.com/tutorials...t-prime95.html

Dean

Sent from my iPhone

Jonathan_King · 18 Dec 2010

Speedfan's flame icon doesn't really tell you much. 60C is cool for a GPU; nVidia GPUs can safely operate up to 105C!

If the CPU got past 65, I'd try to cool it down.