F5F Stay Refreshed Hardware Desktop Desktop crash occurred yesterday due to BSOD.

Desktop crash occurred yesterday due to BSOD.

Desktop crash occurred yesterday due to BSOD.

Pages (2): 1 2 Next
K
KawiianMili
Posting Freak
786
02-21-2016, 02:18 AM
#1
Dear forum members, I own a Windows 10 machine with an i7 6700K processor, an ASUS ROG Strix Z270H motherboard, 2x8GB Corsair Vengeance 3200MHz RAM (XMP enabled), an X6600 CPU and an TX850 M.2 SSD from Corsair. After returning home from school, I powered on the PC and noticed the BIOS timer was set to 11:45 AM. I synced it and then the system booted, but I heard a BSOD several times. My mom told me she accidentally pressed the power switch on the wall while I was at school. Now I’m worried it will happen again. What should I do to prevent this?
K
KawiianMili
02-21-2016, 02:18 AM #1

Dear forum members, I own a Windows 10 machine with an i7 6700K processor, an ASUS ROG Strix Z270H motherboard, 2x8GB Corsair Vengeance 3200MHz RAM (XMP enabled), an X6600 CPU and an TX850 M.2 SSD from Corsair. After returning home from school, I powered on the PC and noticed the BIOS timer was set to 11:45 AM. I synced it and then the system booted, but I heard a BSOD several times. My mom told me she accidentally pressed the power switch on the wall while I was at school. Now I’m worried it will happen again. What should I do to prevent this?

C
ChristobalMC_
Member
102
02-21-2016, 08:42 AM
#2
What error appears when the system crashes? We need more details to investigate further. A permanent solution might not exist, but you can use BlueScreenView to capture additional data after a BSOD to provide better insights. It seems like a program from 1992 is still functional. https://www.nirsoft.net/utils/blue_screen_view.html
C
ChristobalMC_
02-21-2016, 08:42 AM #2

What error appears when the system crashes? We need more details to investigate further. A permanent solution might not exist, but you can use BlueScreenView to capture additional data after a BSOD to provide better insights. It seems like a program from 1992 is still functional. https://www.nirsoft.net/utils/blue_screen_view.html

R
RewarPlaysYT
Member
63
02-21-2016, 12:40 PM
#3
system_service_exception, critical process, driver_lrql_less_or_not_equal, several wdfilter.sys files, three dll bsods, and an event ID 41 in category 63 (kernel power)
R
RewarPlaysYT
02-21-2016, 12:40 PM #3

system_service_exception, critical process, driver_lrql_less_or_not_equal, several wdfilter.sys files, three dll bsods, and an event ID 41 in category 63 (kernel power)

I
IgorElCactus
Member
60
02-21-2016, 06:36 PM
#4
The CMOS was cleared. Afterward, I checked the BIOS settings but didn’t make any changes.
I
IgorElCactus
02-21-2016, 06:36 PM #4

The CMOS was cleared. Afterward, I checked the BIOS settings but didn’t make any changes.

A
AlexStudios
Junior Member
7
02-22-2016, 01:43 AM
#5
I used only XMP and Intel Virtual Technology, and I didn’t clear the CMOS.
A
AlexStudios
02-22-2016, 01:43 AM #5

I used only XMP and Intel Virtual Technology, and I didn’t clear the CMOS.

T
TheLogGFX
Junior Member
7
03-02-2016, 12:47 PM
#6
It seems the CMOS wasn't reset during the power loss. Did you verify the memory voltage settings after turning on XMP?
T
TheLogGFX
03-02-2016, 12:47 PM #6

It seems the CMOS wasn't reset during the power loss. Did you verify the memory voltage settings after turning on XMP?

R
ReDeR_Games
Member
194
03-04-2016, 11:21 AM
#7
It wasn't an issue, but I encountered the BIOS error screen during startup. The RAM voltages are accurate, and I used BluescreenView to investigate, though no crash reports appeared.
R
ReDeR_Games
03-04-2016, 11:21 AM #7

It wasn't an issue, but I encountered the BIOS error screen during startup. The RAM voltages are accurate, and I used BluescreenView to investigate, though no crash reports appeared.

T
Traqedyy
Junior Member
3
03-04-2016, 01:43 PM
#8
These unexpected crashes could stem from various issues like insufficient RAM, CPU problems, or driver conflicts. You might uncover more details by installing WinDbg, accessing C:\Windows\Minidump, and analyzing the dump files through it.
T
Traqedyy
03-04-2016, 01:43 PM #8

These unexpected crashes could stem from various issues like insufficient RAM, CPU problems, or driver conflicts. You might uncover more details by installing WinDbg, accessing C:\Windows\Minidump, and analyzing the dump files through it.

T
Towaii
Junior Member
5
03-07-2016, 03:04 AM
#9
No, your setup isn't overclocked.
T
Towaii
03-07-2016, 03:04 AM #9

No, your setup isn't overclocked.

F
FaZeDRZZL
Junior Member
20
03-09-2016, 03:47 AM
#10
Remove the battery and reset the entire CMOS, possibly causing damage if it was affected during the reset.
F
FaZeDRZZL
03-09-2016, 03:47 AM #10

Remove the battery and reset the entire CMOS, possibly causing damage if it was affected during the reset.

Pages (2): 1 2 Next