F5F Stay Refreshed Hardware Desktop Screen turns black exclusively during gameplay

Screen turns black exclusively during gameplay

Screen turns black exclusively during gameplay

Pages (2): 1 2 Next
E
eel8
Member
177
10-24-2016, 11:48 PM
#1
I've tried various fixes and checks so far. My system runs smoothly during gaming, but it randomly shuts down with a black screen. It happens at unpredictable times, even though I'm not under stress. I've updated the hardware, reinstalled drivers, run diagnostics, and removed many programs. Still no clear cause. I haven't tested my power supply yet, but I want to rule that out too. Right now I'm playing Spider Man remastered and CSGO, which are causing frequent crashes. Any suggestions would be greatly appreciated.
E
eel8
10-24-2016, 11:48 PM #1

I've tried various fixes and checks so far. My system runs smoothly during gaming, but it randomly shuts down with a black screen. It happens at unpredictable times, even though I'm not under stress. I've updated the hardware, reinstalled drivers, run diagnostics, and removed many programs. Still no clear cause. I haven't tested my power supply yet, but I want to rule that out too. Right now I'm playing Spider Man remastered and CSGO, which are causing frequent crashes. Any suggestions would be greatly appreciated.

T
TheNextPlayer
Junior Member
27
10-25-2016, 03:49 AM
#2
Disable PBO in BIOS if possible. Restart your GPU immediately by pressing Win+Control+Shift+B. If the problem persists, roll back the GPU driver and ensure it won’t update automatically—adjust settings in System Settings > Hardware > Device Installation. Perform a clean boot to identify issues. Check if you receive a bug message in a debugger or if it remains blank.
T
TheNextPlayer
10-25-2016, 03:49 AM #2

Disable PBO in BIOS if possible. Restart your GPU immediately by pressing Win+Control+Shift+B. If the problem persists, roll back the GPU driver and ensure it won’t update automatically—adjust settings in System Settings > Hardware > Device Installation. Perform a clean boot to identify issues. Check if you receive a bug message in a debugger or if it remains blank.

I
Inf3rno
Member
186
10-25-2016, 04:29 AM
#3
PSU: 12V 5A, Model: XYZ Pro
I
Inf3rno
10-25-2016, 04:29 AM #3

PSU: 12V 5A, Model: XYZ Pro

_
_NeoBl0X_
Senior Member
635
10-25-2016, 05:27 AM
#4
corsair cv 750
_
_NeoBl0X_
10-25-2016, 05:27 AM #4

corsair cv 750

L
Linaldo
Junior Member
5
10-25-2016, 05:52 PM
#5
Turn it off. The PC restarts and doesn’t freeze. It’s using an outdated GPU driver, so tried a clean boot. To check for bugs, look for error messages or unusual behavior.
L
Linaldo
10-25-2016, 05:52 PM #5

Turn it off. The PC restarts and doesn’t freeze. It’s using an outdated GPU driver, so tried a clean boot. To check for bugs, look for error messages or unusual behavior.

P
PVPMaster2003
Junior Member
12
10-31-2016, 08:16 AM
#6
Not the best PSU but should suffice enough
P
PVPMaster2003
10-31-2016, 08:16 AM #6

Not the best PSU but should suffice enough

R
ReborntoKill
Posting Freak
821
10-31-2016, 10:15 AM
#7
Launch the event viewer, navigate to system, and on the right side select 'filter current log' with ID number 1001. Review the filepath in the description. Launch a browser, download Bluescreenview, run it as administrator, and enable 'bug check string'. Ensure it shows a value; otherwise proceed. Reopen the event viewer, choose system again, pick 'filter current log', and set filters to Critical, error, and warning. Apply the changes. Examine the events leading up to the crash. Reset the filter and compare the results with the three referenced details. Also verify in the Application tab.
R
ReborntoKill
10-31-2016, 10:15 AM #7

Launch the event viewer, navigate to system, and on the right side select 'filter current log' with ID number 1001. Review the filepath in the description. Launch a browser, download Bluescreenview, run it as administrator, and enable 'bug check string'. Ensure it shows a value; otherwise proceed. Reopen the event viewer, choose system again, pick 'filter current log', and set filters to Critical, error, and warning. Apply the changes. Examine the events leading up to the crash. Reset the filter and compare the results with the three referenced details. Also verify in the Application tab.

M
MetabolizmLT
Member
103
10-31-2016, 10:28 AM
#8
Looking for a video tutorial? The specific section about the "far right" isn't visible in the current materials.
M
MetabolizmLT
10-31-2016, 10:28 AM #8

Looking for a video tutorial? The specific section about the "far right" isn't visible in the current materials.

E
E_Swizzle_567
Junior Member
9
10-31-2016, 01:28 PM
#9
On the right side of Event Viewer Actions System Open Saved Log Create Custom View Import Custom View Clear Log Filter Current Log is listed here. Also, open Windows PowerShell as Administrator and run winget install Microsoft.WinDbg, press Enter, type WinDbg and click Run as Admin, then select file and import a 32-bit minidump from the Windows system. Enter and press Analyze. If anything is unclear, refer to YOUTUBE. Updated February 10, 2025 by MewMew
E
E_Swizzle_567
10-31-2016, 01:28 PM #9

On the right side of Event Viewer Actions System Open Saved Log Create Custom View Import Custom View Clear Log Filter Current Log is listed here. Also, open Windows PowerShell as Administrator and run winget install Microsoft.WinDbg, press Enter, type WinDbg and click Run as Admin, then select file and import a 32-bit minidump from the Windows system. Enter and press Analyze. If anything is unclear, refer to YOUTUBE. Updated February 10, 2025 by MewMew

M
Milad_PvP
Member
116
10-31-2016, 02:13 PM
#10
Uncertain if this matches your needs, but you encountered these issues. The security policy check using virtualization failed because Virtual Secure Mode isn't set up. It seems the hypervisor or VSM might be missing or disabled. Attempted to start the hypervisor, but it couldn't launch—either SVM wasn't found or not enabled in BIOS. A critical hardware error occurred. Reported by component: Processor Core Error. Source: Machine Check Exception. Error Type: Cache Hierarchy. APIC ID: 4. Additional details available in the full view.
M
Milad_PvP
10-31-2016, 02:13 PM #10

Uncertain if this matches your needs, but you encountered these issues. The security policy check using virtualization failed because Virtual Secure Mode isn't set up. It seems the hypervisor or VSM might be missing or disabled. Attempted to start the hypervisor, but it couldn't launch—either SVM wasn't found or not enabled in BIOS. A critical hardware error occurred. Reported by component: Processor Core Error. Source: Machine Check Exception. Error Type: Cache Hierarchy. APIC ID: 4. Additional details available in the full view.

Pages (2): 1 2 Next