F5F Stay Refreshed Software Operating Systems My computer suddenly shuts down to a blank screen without any warning?

My computer suddenly shuts down to a blank screen without any warning?

My computer suddenly shuts down to a blank screen without any warning?

Pages (3): Previous 1 2 3
D
DonMcOne
Member
188
08-19-2016, 07:55 AM
#21
The page file needs to reside on the same drive as your operating system.
Set the page file size to "system managed."
Type the command sysdm.cpl into the Run command box.
Select the Advanced tab, then click the top Settings button.
Proceed to the Advanced tab again, click the Change button.
Make sure the Automatically manage paging file size for all drives option is selected.
Confirm by clicking OK (you’ll be prompted to restart).
Restart the system.

System crash/recovery settings should display "Automatic memory dump."
Check the box for "Overwrite any existing file."
Ensure "Write an event to the system log" is selected.
Set the dump file location to %SystemRoot%\MEMORY.DMP.
Run sysdm.cpl again, go to the Run command box, and type Advanced.
Click the bottom Settings button.
Verify the Write an Event to the System log box is checked.
Set the Write debugging information pull-down to Automatic memory dump.
Set the Dump File location to %SystemRoot%\MEMORY.DMP.
Check the Overwrite any existing file box.
Click OK to proceed.
Press OK again to finish and be reminded to reboot (click Restart Later if needed).

Windows Error Reporting (WER) service must be configured as MANUAL.
Open services.msc, find Windows Error Reporting, set its Startup type to Manual (Trigger Start).
If not already done, double-click the service to open the change dialog.
Set the Startup type pull-down to Manual.
Click OK and close the Services dialog.

User account control must be active.
Run useraccountcontrolsettings, adjust the slider to Notify me only when applications attempt changes (default).
Confirm with OK to close the window.
Proceed to reboot.
D
DonMcOne
08-19-2016, 07:55 AM #21

The page file needs to reside on the same drive as your operating system.
Set the page file size to "system managed."
Type the command sysdm.cpl into the Run command box.
Select the Advanced tab, then click the top Settings button.
Proceed to the Advanced tab again, click the Change button.
Make sure the Automatically manage paging file size for all drives option is selected.
Confirm by clicking OK (you’ll be prompted to restart).
Restart the system.

System crash/recovery settings should display "Automatic memory dump."
Check the box for "Overwrite any existing file."
Ensure "Write an event to the system log" is selected.
Set the dump file location to %SystemRoot%\MEMORY.DMP.
Run sysdm.cpl again, go to the Run command box, and type Advanced.
Click the bottom Settings button.
Verify the Write an Event to the System log box is checked.
Set the Write debugging information pull-down to Automatic memory dump.
Set the Dump File location to %SystemRoot%\MEMORY.DMP.
Check the Overwrite any existing file box.
Click OK to proceed.
Press OK again to finish and be reminded to reboot (click Restart Later if needed).

Windows Error Reporting (WER) service must be configured as MANUAL.
Open services.msc, find Windows Error Reporting, set its Startup type to Manual (Trigger Start).
If not already done, double-click the service to open the change dialog.
Set the Startup type pull-down to Manual.
Click OK and close the Services dialog.

User account control must be active.
Run useraccountcontrolsettings, adjust the slider to Notify me only when applications attempt changes (default).
Confirm with OK to close the window.
Proceed to reboot.

S
SkyInsane
Senior Member
718
08-19-2016, 01:03 PM
#22
I encountered difficulties accessing the Event Viewer logs and typically avoid downloading such files. This might not matter given the "unsupported file type" warning shown.
= = = =
There are several issues occurring in Reliability History/Monitor, which raises more questions. I’ll address them later.
My advice is to follow @ubuysa’s suggestion from their previous message and revisit the logs as needed.
Then, check Reliability History/Monitor and Event Viewer again to identify any changes—such as new error codes, warnings, or patterns.
Please share screenshots via imgur (www.imgur.com > green "New post" icon).
S
SkyInsane
08-19-2016, 01:03 PM #22

I encountered difficulties accessing the Event Viewer logs and typically avoid downloading such files. This might not matter given the "unsupported file type" warning shown.
= = = =
There are several issues occurring in Reliability History/Monitor, which raises more questions. I’ll address them later.
My advice is to follow @ubuysa’s suggestion from their previous message and revisit the logs as needed.
Then, check Reliability History/Monitor and Event Viewer again to identify any changes—such as new error codes, warnings, or patterns.
Please share screenshots via imgur (www.imgur.com > green "New post" icon).

R
Razlorus
Posting Freak
976
09-02-2016, 05:54 PM
#23
Sorry for the delayed response, life has been chaotic, but I completed these steps. The only adjustment that needed updating was setting the system crash/recovery option to Automatic memory Dump. All other aspects already aligned with what you mentioned earlier.
In reality, when reviewing reliability and the event viewer, it’s hard to interpret the text or identify any changes in error codes or warnings. I’m not confident I’d spot anything different even if I examined them closely. I struggle with navigating the Event Viewer and figuring out how to extract meaningful data from it.
I noticed something in the application windows logs too. It doesn’t make sense, but it seems related to the crash that occurred while playing a game.
I experienced several more crashes, and after a thorough reboot today, I received a result I’ve never seen before. Replacing the DisplayPort cable resolved the issue.
R
Razlorus
09-02-2016, 05:54 PM #23

Sorry for the delayed response, life has been chaotic, but I completed these steps. The only adjustment that needed updating was setting the system crash/recovery option to Automatic memory Dump. All other aspects already aligned with what you mentioned earlier.
In reality, when reviewing reliability and the event viewer, it’s hard to interpret the text or identify any changes in error codes or warnings. I’m not confident I’d spot anything different even if I examined them closely. I struggle with navigating the Event Viewer and figuring out how to extract meaningful data from it.
I noticed something in the application windows logs too. It doesn’t make sense, but it seems related to the crash that occurred while playing a game.
I experienced several more crashes, and after a thorough reboot today, I received a result I’ve never seen before. Replacing the DisplayPort cable resolved the issue.

A
Abood_99am
Member
115
09-03-2016, 07:31 AM
#24
Does that indicate the problem has been resolved?
A
Abood_99am
09-03-2016, 07:31 AM #24

Does that indicate the problem has been resolved?

I
ItsDrAxel
Member
113
09-04-2016, 02:25 PM
#25
The problem still remains, as I clarified that the fix was only for that particular half of the screen. The black screen crashes continue to occur. They seem to happen more often in certain games than others.

I've also spoken with nVidia customer support, and they suggested checking GPU-Z and its log collector feature. They mentioned that the graphics card might be running at PCIe x16 1.1 instead of the ideal PCIe x16 4.0, which could mean another hardware component is using the GPU's PCIe lanes or that the connection isn't being used fully. I don’t understand how that could be happening—it should be plugged into the correct PCIe slot, though I suspect that. I’ll need to verify this.

Furthermore, they noted that the GPU’s clock speed exceeds the manufacturer’s maximum limit, which might point to a hardware issue. Although I haven’t overclocked the card intentionally, everything in my system should run at default speeds, but I need to confirm if it’s actually operating correctly.

I also overlooked mentioning that I replaced the thermal pads on the GPU about a year ago with some aftermarket "Kritikal" pads. They said this lowered temperatures by 5-7 degrees and that I hadn’t experienced any problems with the card for at least a year. I’m wondering if this change could be connected to the issue.
I
ItsDrAxel
09-04-2016, 02:25 PM #25

The problem still remains, as I clarified that the fix was only for that particular half of the screen. The black screen crashes continue to occur. They seem to happen more often in certain games than others.

I've also spoken with nVidia customer support, and they suggested checking GPU-Z and its log collector feature. They mentioned that the graphics card might be running at PCIe x16 1.1 instead of the ideal PCIe x16 4.0, which could mean another hardware component is using the GPU's PCIe lanes or that the connection isn't being used fully. I don’t understand how that could be happening—it should be plugged into the correct PCIe slot, though I suspect that. I’ll need to verify this.

Furthermore, they noted that the GPU’s clock speed exceeds the manufacturer’s maximum limit, which might point to a hardware issue. Although I haven’t overclocked the card intentionally, everything in my system should run at default speeds, but I need to confirm if it’s actually operating correctly.

I also overlooked mentioning that I replaced the thermal pads on the GPU about a year ago with some aftermarket "Kritikal" pads. They said this lowered temperatures by 5-7 degrees and that I hadn’t experienced any problems with the card for at least a year. I’m wondering if this change could be connected to the issue.

Pages (3): Previous 1 2 3