Random Blue Screens

My computer will random reset itself (no actual Blue Screen) and restart saying I've had a BSOD.

These are the dump files I've gotten so far, if anyone could help me figure out the cause that'd be great!

Ok my friend, looks like this is hardware issue. The bugcheck code is 124, this is usually hardware issue (We don't know for sure yet). Plesae read this article to know what it is and what to try:
https://www.sevenforums.com/crash-loc...-what-try.html

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.071\062910-24960-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02849000 PsLoadedModuleList = 0xfffff800`02a86e50
Debug session time: Tue Jun 29 13:27:20.144 2010 (UTC + 7:00)
System Uptime: 0 days 0:00:08.580
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading 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, fffffa800364d038, 0, 0}

Probably caused by : hardware

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

Looks like it always happend when you start your computer right?

Code:

System Uptime: 0 days 0:00:09.765
System Uptime: 0 days 0:00:08.580

Can you boot into safe mode, you might wanna try this:
http://support.microsoft.com/kb/929135

~Tuan

ttran said:

Ok my friend, looks like this is hardware issue. The bugcheck code is 124, this is usually hardware issue (We don't know for sure yet). Plesae read this article to know what it is and what to try:
https://www.sevenforums.com/crash-loc...-what-try.html

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.071\062910-24960-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02849000 PsLoadedModuleList = 0xfffff800`02a86e50
Debug session time: Tue Jun 29 13:27:20.144 2010 (UTC + 7:00)
System Uptime: 0 days 0:00:08.580
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading 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, fffffa800364d038, 0, 0}

Probably caused by : hardware

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

Looks like it always happend when you start your computer right?

Code:

System Uptime: 0 days 0:00:09.765
System Uptime: 0 days 0:00:08.580

Can you boot into safe mode, you might wanna try this:
How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

~Tuan

Actually, my computer just reboots as if I reset it. Then upon booting into the desktop I get a popup showing a 'check for solutions' window about the bluescreen. I never actually see a bluescreen show up. (I've told Windows to NOT automatically restart upon BSOD)

It did it again to just now.

Steven, are you doing any overclocking? If so, try restoring the defaults.

It almost sounds like a heat issue. What your your temps like? If you don't already have a program, Speedfan works quite well.

If you can get to another PSU, try it.

BSOD BUGCHECK SUMMARY

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 02:27:20.144 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:08.580
BugCheck 124, {0, fffffa800364d038, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Jonathan_King said:

Steven, are you doing any overclocking? If so, try restoring the defaults.

It almost sounds like a heat issue. What your your temps like? If you don't already have a program, Speedfan works quite well.

If you can get to another PSU, try it.

BSOD BUGCHECK SUMMARY

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 02:27:20.144 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:08.580
BugCheck 124, {0, fffffa800364d038, 0, 0}
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Hello Johnathan. Yes, I am overclocking (3.5GHz, stock is 2.8GHz).

I doubt it is a heat issue as my temps for the CPU stay below 50C. I had this problem before with a 450W PSU but I figured at the time it was due to lack of power. Since I got a 750W now I know that is not the case (and both PSU's cannot be bad).

I'll try lowering scrapping the OC for now, if that solves it and I don't BSOD for a bit then I will try OCing again at a lower GHz.

Thank you, both. :)

If restoring the overclock doesn't work, we can do some other hardware tests.

Best of luck Steven.

Jonathan_King said:

If restoring the overclock doesn't work, we can do some other hardware tests.

Best of luck Steven.

It didn't work.

Update the motherboard BIOS according to the manufacturer's instructions. Their website should provide detailed instructions as to the brand and model-specific procedure.

Have you tried that my friend??:)

ttran said:

Update the motherboard BIOS according to the manufacturer's instructions. Their website should provide detailed instructions as to the brand and model-specific procedure.

Have you tried that my friend??:)

I've had the latest BIOS update for a bit now.

What I am trying right now is trying Vista instead of 7, as I've noticed I never have any problems in Linux or OS X on this computer. Yet I have BSOD's on Windows.

EDIT: That was epic fail, sitting there loading a webpage and RESTART. Still could be a Windows specific issue but, wont rule anything out right now though.

Try a RAM test. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

I'll have another look at your dmps to see if I can pick up anything else, but I do suspect hardware.