Solved Black Screen of Death or Black Gaming Screen of Death

[sutex]

I would keep the latest version, then monitor your computer and see if issue remains.

Incidentally, have you tried seeing if the issue exists in safe-mode?

:ar: Boot into Safe-mode

cheers

Dave

No I have no seen it in safe mode UNTIL TWO DAYS AGO, while in safe mode Blacksod happened for the first time. Which is why a week ago , I was very certain it was a driver issue. After the Blacksod in safe mode, I'm not so sure I feel blaming hardware ,will not help if it's NOT the hardware.

Also I have notice that there is No OS showing up in msiconfig boot section ,was there at some point, not now, and can't get a kernel dump going, OS not showing up their either.

 

[Northernsoul55]

Navigate to:
Control Panel -> System and Security -> System -> Advanced System Settings, Start and Recovery

Is your operating system listed there?

 

[sutex]

Navigate to:
Control Panel -> System and Security -> System -> Advanced System Settings, Start and Recovery

Is your operating system listed there?

No.

 

[Northernsoul55]

Navigate to:

Start>In the "search programs and files" box type> manage
Click on Computer management
Double click on Storage> then Disk Management in the left pane.

Post a screenshot of the resulting screen

 

[sutex]

Navigate to:

Start>In the "search programs and files" box type> manage
Click on Computer management
Double click on Storage> then Disk Management in the left pane.

Post a screenshot of the resulting screen

Done

 

[sutex]

SF Diagnostic Tool

Here is a SF_Diagnostic_Tool report. taken after a blacksod just now

 

[Arc]

So it happened after the BIOS update?

Can you point me out the BIOS that you taken?

 

[cipley]

again, it's blaming your hardware:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8008925038, 0, 0}

Probably caused by : [B][COLOR="Red"]hardware[/COLOR][/B]

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

also:

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.


.........

STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

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

The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124. This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).

looks like NorthernSoul pointed, that your processor may be finally give in

 

[Northernsoul55]

Cipley - That's a previous log dated 2/5/2013 Its already been analysed.

 

[cipley]

Cipley - That's a previous log dated 2/5/2013 Its already been analysed.

aaah...missed it :huh:
so when it's BSODed again it didn't generate new .dmp files, huh....
and I ended up opening the old log...hahaha

 

[Northernsoul55]

Basically...Yes! Dont worry...I done my fair share...its easy enough to do, now i scrutinise the dates

 

[Arc]

Cipley - That's a previous log dated 2/5/2013 Its already been analysed.

aaah...missed it :huh:
so when it's BSODed again it didn't generate new .dmp files, huh....
and I ended up opening the old log...hahaha

What I do .... My folder view is set to "details"
Unzip, and right click > group by > Date

All the files get ranked according to date. Now it is most easy to check the latest files

 

[cipley]

Cipley - That's a previous log dated 2/5/2013 Its already been analysed.

aaah...missed it :huh:
so when it's BSODed again it didn't generate new .dmp files, huh....
and I ended up opening the old log...hahaha

What I do .... My folder view is set to "details"
Unzip, and right click > group by > Date

All the files get ranked according to date. Now it is most easy to check the latest files

will try to do that...thanks

 

[sutex]

So it happened after the BIOS update?

Can you point me out the BIOS that you taken?

SABERTOOTH-X58-ASUS-1304 OLD One , had Blacksod

SABERTOOTH-X58-ASUS-1402 New updated last few days ,, Still gettting Blacksod.

 

[sutex]

again, it's blaming your hardware:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8008925038, 0, 0}

Probably caused by : [B][COLOR=Red]hardware[/COLOR][/B]

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

also:

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.


.........

STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

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

The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124. This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).

looks like NorthernSoul pointed, that your processor may be finally give in

WOW. This morning the Sabertooth x58 gave ,Beeps.. One short 3 long meaning a VGA error. Also last night after nurmous Blacksod and the Beeping. I tried to re-insatll the ATI drivers again , the ATI install software could no detect the Graphic card, driver.

 

[sutex]

Would like to thank all for doing the yards in trying to pin down the Blacksod issue. So given the information , ie missing OS in Msconfig, VGA beeps ,and Blacksod, we can all asume , my PC is not working well lol.

 

[sutex]

I'm taking the PC to be diagnosed at PC store.Today PC would not boot into main OS would only work in Safe Mode. and then not for long , would stil get Blacksod.
If you can all continue with your analysis , on my files , that will be a big help, as the tech guys at the store will be given this page as a means of double checking their findings. Wil keep this post updated , so don't close this thread just yet. At least this way, when some else gets this issue , they will have something to go on.

 

[Northernsoul55]

Good luck, look forward to your report

 

[sutex]

Quick update , PC back from shop , TECH guy cleaned out dust inside graphics CARD , re-did heat sink cement. And still PC went into Blacksod.
Tech then place GPU into second PCI slot. That seems to fixed the Blackdsod., still have to test in game, but there has been no Blacksod , since GPU has been moved.
Problem seems to be the Sabertooth X58 motherboard. SO ? for you all, who have helped , anyone see anything in the TXT uploaded, that my have indicted a PCI board malfunction. Just trying to get the error codes in line with what I have seen and been told. It may help others in the future.

Within a week , will know for sure if this problem is solved , for the time been I'm still in the testing phase, of this "FIX" of moving the GPU around. This thread is still open , as Tech dude. has Motherboard manual, just to see if there was any thing he missed, and what is the best possible setup, for my system.

 

[Northernsoul55]

Thanks for the feedback.

Nothing in the logs indicated a Mobo malfunction, but these issues are quite
hard to diagnose from logs, so it was good that it was narrowed down to either PSU/Mobo/CPU.

Please mark the thread as solved once you are happy that your issue has been resolved.

cheers

Dave