PC keeps crashing.

-Hotplate-

-Hotplate-

-Hotplate-

Associate
Joined
1 Feb 2006
Posts
215
Hello
Very recently, probably only started happening this month - April, my PC crashes to BSOD and then restarts. It is happening every night (PC is home server and is on 24/7), but when I wake every morning the start up screen is waiting for my login password to finish reboot.
I did google this and apparently a recent Windows Update (Win 10 x64) is the likely cause as is stopping some PC's from even booting up.
Anyone else having these problems?

Also is there anyway of finding out what time the PC crashed at? Or even better is the some log I can look at to give me more of an idea what happened just before the Crash?
Windows does the gathering date before reboot, so where is it looking for this information?
Any help would be appreciated. I have installed some games recently (BF4,BF1, Elite Dangerous and Crysis 3) , but apart from that noting else is different.
Also every restart sees Origin crash too. Every time. Awful software. Can't believe they still haven't sorted this after all these years.
Cheers
 
First thing I would do is look under event viewer > Windows Logs > System.

post back what you find in there and it should narrow down what is crashing or causing the PC to crash
 
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 28/04/2020 01:46:08
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ByTheLakeServer
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000be (0xffffa86006d41957, 0x8a00000000200021, 0xfffffb08edcdd580, 0x000000000000000a). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 1f6fba29-c0a5-4d1a-808f-b0fe4cb5e0e8.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-04-28T00:46:08.729338800Z" />
<EventRecordID>92219</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>ByTheLakeServer</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x000000be (0xffffa86006d41957, 0x8a00000000200021, 0xfffffb08edcdd580, 0x000000000000000a)</Data>
<Data Name="param2">C:\WINDOWS\MEMORY.DMP</Data>
<Data Name="param3">1f6fba29-c0a5-4d1a-808f-b0fe4cb5e0e8</Data>
</EventData>
</Event>
 
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 28/04/2020 01:45:52
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: ByTheLakeServer
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
<EventID>41</EventID>
<Version>6</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2020-04-28T00:45:52.250908300Z" />
<EventRecordID>92171</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>ByTheLakeServer</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">190</Data>
<Data Name="BugcheckParameter1">0xffffa86006d41957</Data>
<Data Name="BugcheckParameter2">0x8a00000000200021</Data>
<Data Name="BugcheckParameter3">0xfffffb08edcdd580</Data>
<Data Name="BugcheckParameter4">0xa</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">41</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">25</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">false</Data>
<Data Name="CheckpointStatus">0</Data>
</EventData>
</Event>
 
Log Name: System
Source: EventLog
Date: 28/04/2020 01:46:01
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ByTheLakeServer
Description:
The previous system shutdown at 01:03:15 on ‎28/‎04/‎2020 was unexpected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-04-28T00:46:01.959709500Z" />
<EventRecordID>92161</EventRecordID>
<Channel>System</Channel>
<Computer>ByTheLakeServer</Computer>
<Security />
</System>
<EventData>
<Data>01:03:15</Data>
<Data>‎28/‎04/‎2020</Data>
<Data>
</Data>
<Data>
</Data>
<Data>38985</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>E407040002001C00010003000F004603E407040002001C00000003000F004603600900003C000000010000006009000001000000B00400000000000000000000</Binary>
</EventData>
</Event>
 
Hi there are 5 dump files and 4 different comments in the Bug Check String. 1 Bug Check String is blank, the 4 filled in say this
PAGE_FAULT_IN_NONPAGED_AREA
ATTEMPTED_WRITE_TO_READONLY_MEMORY
Blank
IRQL_NOT_LESS_OR_EQUAL
MEMORY_MANAGEMENT

I have run the Windows 10 Memory Checker and no faults where found.
What next?
THanks
 
Do you have any overclocks on the ram or the system at all?

what ram are you using and speeds?

check windows update and see if any new updates where installed at the time the issues started

maybe try and re seat the ram modules or try and run memtest for a good few hours as the windows one may not run long enough to find any issues.

maybe run the system with one stick of ram in and if it happens again remove it and try another until you find the module with the problem

what’s the pc specs and is your running?
 
Last edited:
No over clocks at all. I took the side off to install my new 1660 Super. Previously didnt have a GFX for 6 years.
Whilst the side was open I did give it a good clean, blowout and hoover. I will check everything is still seated correctly. TBF these issues have only happened since I installed the 1660.
I put it down to the game software I have installed. Maybe its hardware.

Old System now
Z87X-OC
i7-4770K (never been clocked!!!!)
Corsair Vengance Ram 2 x 4G
H80i GT AIO Cooler
Samsung 1TB EVO SSD
3 HDD's - 2x3TB and 1x 1.5TB
1.5TB is my download drive and probably gets the most use.
2 x 3TB are storage drives. I run my own PLEX server so that I can watch what I want where I want. I stay away a lot with work and hotel TV is shocking.
So this rig is on 24/7 and has behaved perfectly for years now. I live alone too. So no one else can bugger it up but me :)
 
Ok, this is what I would do.

- Re seat the ram, take them out and then put them back in again.
- if issues still happen remove one stick, if you still have issues swap them over and again if you have problems try the other ram slot.
- run memtest, this will require a usb stick and you then boot from this and allow it to run for a good 2 hours.
- if you have another pc you can swap the ram over then try this.
 
Hi I thought I should update this. I tried every possible combination of ram stick(s) in every slot and BSOD crashes kept on happening. Maximum time was 23 hours before it occurred. Actually started to get worse too. Was once a day buy increased to 3 times a day. In the end I thought "what has changed". So before I removed my new GFX card I uninstalled all MSI software that I downloaded from the MSI website. I remembered whilst installing it I got an error message on screen but it flashed up and was gone. I now think it was MSI SDK software.
Since I uninstalled all that my PC hasn't fallen over once!!!!!
However its now developed a new fault. File transfer between drives has slowed to a snails pace. I just tried to install MW2 Remastered from a virtual iso and it slowed to a stop and even Task Manager wouldn't kill it.
So I have decided to format and reinstall Windblows and everything else too. Its been a while so shouldn't be a bad thing.
 
You must log in or register to reply here.
Back
Top Bottom