|01 Nov 2013||#1|
| || |
BSOD When Running WoW / PA / Civ V
Hi, as mentioned in the title im getting seemingly random black-screen reboots with very occasional BSOD's when running the above games( haven't tried others, could just be GPU heavy titles). The dreaded "Power Supply Surges detected during the previous power on. ASUS Anti-Surge was triggered to protect system from unstable power supply unit! " seems to suggest the problem lies with a faulty power supply, as my previous machine using the same component was prone to these type of restarts, however i would like to tap into this well of knowledge to reassure myself before spending money. I tried turning off Anti-Surge in the BIOS to see if it was artificially causing these restarts, but the problem continues. I've uploaded what i hope is all the crash dump data from the last occurrence. Many thanks for taking the time to help me out with this
|My System Specs|
|02 Nov 2013||#2|
| || |
Welcome to SF !
Out of the fourteen dumps, twelve of them are a 0x124 bug check with a cache write error,
predominantly on processor #3. The other two bug checks are at bottom of the priority at the moment.
=============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ fffffa8008a57138 Section @ fffffa8008a572c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : DCACHEL0_WR_ERR (Proc 3 Bank 1) Status : 0xbf80000000000124 Address : 0x000000021a005b80 Misc. : 0x0000000000000086
=============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ fffffa8008a4a138 Section @ fffffa8008a4a2c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : DCACHEL0_WR_ERR (Proc 0 Bank 1) Status : 0xbf80000000000124 Address : 0x000000021a4b57c0 Misc. : 0x0000000000000086
A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. 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. - H2SO4
the trail & error approach.
Do you have any spare parts (or another PC) to test with?
The usual suspect of this kind of BCCode is the CPU but it's often not the the case which is why we need
to test other components to rule them out as the cause.
How old are your components?
What is the make an model of you PSU?
Fill out this form and post back the result:
Make sure that every connection is seating properly and firmly in-place.
Also have a look at the motherboard and the GPU, search for any "bad caps", bulky, leaking bloated capacitors.
Test for thermals and stability:
Testing the RAM:
Test and Diagnose RAM Issues with Memtest86+:
Test your secondary Hard-Drive.
Event: Log Name: System Source: Disk Date: 2013-10-30T10:02:22.408 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: O-PC Description: An error was detected on device \Device\Harddisk1\DR3 during a paging operation. Event: Log Name: System Source: Ntfs Date: 2013-10-30T10:02:22.408 Event ID: 57 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: O-PC Description: The system failed to flush data to the transaction log. Corruption may occur.
The Following Method Should NOT Be Performed On An SSD!
Testing the HDD:
Boot into the BIOS using the *Fx key.
Look for an entry called SATA Mode (or something similar), it should be set to IDE / AHCI.
It's probably set to AHCI which is why SeaTools doesn't recognize them in the DOS environment.
Set it to IDE then save and exit usually by pressing the F10 key.
Now boot into SeaTools and it should detect the drives.
Start the Long Test and let it run.
Upon completion don't try to boot into Windows as it will only result in a BSOD, go back into the BIOS
and change the SATA setting back to what it was in the first place.
Reset the BIOS back to default:
Write down the current value of the SATA Mode!
Its either AHCI or IDE.
After resetting the CMOS go back and verify the value for SATA Mode is what it was
when the OS was installed.
If any component is overclocked reset it back to stock speeds!
Update the BIOS to the latest release:
Flashing the BIOS is a risky procedure. If you are uncomfortable
performing it yourself have a technician perform it for you.
Regardless, flashing is at your own risk.
Good places to read more:
|My System Specs|
|Similar help and support threads for2: BSOD When Running WoW / PA / Civ V|
|BSOD running when running intel driver update utility and more apps||BSOD Help and Support|
|BSOD Running SWTOR Launcher, followed BSOD Posting instructions||BSOD Help and Support|
|BSOD even with nothing running||BSOD Help and Support|
|BSOD while running firefox. Computer has been running terrible.||BSOD Help and Support|
|BSOD while running IE9 (flash plugin running)||BSOD Help and Support|
|Our Sites ||Site Links ||About Us ||Find Us |
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
All times are GMT -5. The time now is 01:35 AM.