Random restarts

agoodall · Jul 2, 2020

Hi,

PC Spec below
Case
FRACTAL DEFINE S NANO GAMING CASE
Processor (CPU)
AMD Ryzen 5 3600X Six Core CPU (3.8GHz-4.4GHz/36MB CACHE/AM4)
Motherboard
Gigabyte B450 I AORUS PRO Wi-Fi AC (DDR4, USB 3.1, 6Gb/s) - RGB Ready!
Memory (RAM)
16GB Corsair VENGEANCE DDR4 3000MHz (2 x 8GB)
Graphics Card
8GB NVIDIA GEFORCE RTX 2070 SUPER - HDMI, 3x DP GeForce - RTX VR Ready!
1st Storage Drive
2TB SEAGATE BARRACUDA SATA-III 3.5" HDD, 6GB/s, 7200RPM, 256MB CACHE
1st M.2 SSD Drive
512GB INTEL® 660p M.2 NVMe PCIe SSD (up to 1500MB/sR | 1000MB/sW)
Power Supply
CORSAIR 650W VS SERIES™ VS-650 POWER SUPPLY
Power Cable
1 x 1 Metre UK Power Cable (Kettle Lead)
Processor Cooling
STANDARD AMD CPU COOLER
Thermal Paste
STANDARD THERMAL PASTE FOR SUFFICIENT COOLING
Extra Case Fans
2x 120mm Black Case Fan (configured to extract from rear/roof)
Sound Card
ONBOARD 6 CHANNEL (5.1) HIGH DEF AUDIO (AS STANDARD)
Wireless/Wired Networking
GIGABIT LAN PORT + Wi-Fi (Wi-Fi excluded on H310I-PLUS)
USB/Thunderbolt Options
MIN. 2 x USB 3.0 & 4 x USB 2.0 PORTS @ BACK PANEL + MIN. 2 FRONT PORTS
Operating System
Windows 10 Home 64 Bit - inc. Single Licence [KK3-00002]
Operating System Language
United Kingdom - English Language
Windows Recovery Media
Windows 10 Multi-Language Recovery Image - Unlimited Downloads from Online Account
Office Software
FREE 30 Day Trial of Microsoft 365® (Operating System Required)
Anti-Virus
NO ANTI-VIRUS SOFTWARE
Browser
Firefox™
Speakers
Creative GigaWorks T40 Series II 2.0 High End Speakers
Surge Protection
6 Socket 2m Surge Protector

I'm having multiple restarts, computer often at idle, not gaming or working hard at all, sometimes I'm doing something on it, sometimes not, sometimes 3 or 4 in 1 day, under event viewer they're Kernel 41 restarts, I've had 2 with:

BugcheckCode

59

BugcheckParameter1

0xc0000005

BugcheckParameter2

0xfffff804438a13fc

BugcheckParameter3

0xfffffb05c81bbf60

BugcheckParameter4

0x0

SleepInProgress

0

PowerButtonTimestamp

0

BootAppStatus

0

Checkpoint

0

ConnectedStandbyInProgress

false

SystemSleepTransitionsToOn

0

CsEntryScenarioInstanceId

0

BugcheckInfoFromEFI

false

CheckpointStatus

0

But the others have 0 as bugcheckcode.

All drivers up to date, advice on various other websites around power settings followed, temps are good don't really know the next step. PC only 2 months old, no restarts at all to start with.

Any ideas?

Rice0603 · Jul 2, 2020

I'm having the same issues with my 1700x has yours only started in the last month or so?

agoodall · Jul 2, 2020

Yes mate

Rice0603 · Jul 2, 2020

I've got the same issue kernel 41 bug check code 63. I'm starting to think it's a driver of some kind.... I have messaged tech support if I get any joy I will let you know

agoodall · Jul 2, 2020

cool thanks

agoodall · Jul 2, 2020

Critical 02/07/2020 12:58:25 Kernel-Power 41 (63)
Critical 02/07/2020 09:12:49 Kernel-Power 41 (63)
Critical 01/07/2020 18:40:21 Kernel-Power 41 (63)
Critical 01/07/2020 16:46:51 Kernel-Power 41 (63)
Critical 01/07/2020 13:58:14 Kernel-Power 41 (63)
Critical 01/07/2020 12:49:22 Kernel-Power 41 (63)
Critical 01/07/2020 10:27:48 Kernel-Power 41 (63)
Critical 30/06/2020 22:59:24 Kernel-Power 41 (63)
Critical 30/06/2020 14:26:11 Kernel-Power 41 (63)
Critical 27/06/2020 16:54:16 Kernel-Power 41 (63)
Critical 24/06/2020 10:03:27 Kernel-Power 41 (63)
Critical 24/05/2020 20:15:07 Kernel-Power 41 (63)
Critical 24/05/2020 17:58:17 Kernel-Power 41 (63)
Critical 01/05/2020 21:44:05 Kernel-Power 41 (63)
Critical 01/05/2020 14:07:31 Kernel-Power 41 (63)

Becoming more and more frequent

Rice0603 · Jul 2, 2020

Critical 02/07/2020 12:49:19 Kernel-Power 41 (63)
Critical 01/07/2020 16:08:22 Kernel-Power 41 (63)
Critical 01/07/2020 10:44:22 Kernel-Power 41 (63)
Critical 30/06/2020 17:05:15 Kernel-Power 41 (63)
Critical 30/06/2020 15:27:34 Kernel-Power 41 (63)
Critical 30/06/2020 13:57:24 Kernel-Power 41 (63)
Critical 28/06/2020 08:24:10 Kernel-Power 41 (63)
Critical 27/06/2020 08:01:38 Kernel-Power 41 (63)
Critical 26/06/2020 12:13:36 Kernel-Power 41 (63)
Critical 21/06/2020 08:47:03 Kernel-Power 41 (63)
Critical 20/06/2020 11:59:20 Kernel-Power 41 (63)
Critical 20/06/2020 07:59:03 Kernel-Power 41 (63)
Critical 19/06/2020 17:39:52 Kernel-Power 41 (63)
Critical 19/06/2020 12:11:40 Kernel-Power 41 (63)
Critical 14/06/2020 12:25:54 Kernel-Power 41 (63)
Critical 14/06/2020 09:08:18 Kernel-Power 41 (63)
Critical 13/06/2020 10:11:34 Kernel-Power 41 (63)
Critical 12/06/2020 10:33:56 Kernel-Power 41 (63)
Critical 09/06/2020 16:52:31 Kernel-Power 41 (63)

I feel your pain mate

ubuysa · Jul 2, 2020

One at a time please, @Rice0603 please start a new thread.

@agoodall, the SYSTEM-SERVICE-EXCEPTION BSOD with the 0xc0000005 error code (STATUS_ACCESS_VIOLATION) is typically a driver problem, though it could also be flaky RAM. The Kernel-Power event 41 errors are simply telling you that Windows didn't shutdown probelrly, that's all. They are a symptom not a cause.

Since it fails even when idle it's important to check your RAM. Download Memtest (free), use the extracted file to make a bootable USB stick (1GB is plenty big enough) and then boot that USB stick. Memtest will start running, leave it overnight. This free version only does 4 iterations of the various tests but that's enough to find most problems.

If you get even a single error, pull each RAM stick in turn and re-run Memtest on each stick individually.

If you have any minidumps, either in C:\Windows\Minidumps or a single memory dump in C:\Windows\MEMORY.DMP please upload it/them to the cloud somewhere and post a link to it/them here. We'll take a look and see whether we can identify the component responsible.

agoodall · Jul 2, 2020

Thanks UBUYSA,

link to minidump files (no file exists for MEMORY.DMP)

minidump

Folder

1drv.ms

I'll run memtest tonight.

ubuysa · Jul 2, 2020

In both dumps the BSOD happens at the same location, the failing module is WDBackupService.exe which is part of the Western Digital backup tool. I would suggest you uninstall this (even temporarily) and see whether the BSODs stop.

Since both dumps show the same failure at different times I think you can hold off on Memtest for now.

agoodall · Jul 2, 2020

Thanks mate, have uninstalled and reinstalled WD software but for now not let it start on startup, will see if that fixes it, if so then I will allow it to start again. Thanks for the help

agoodall · Jul 3, 2020

The PC restarted again this morning at around 4am, obviously just idling.

WDBackup was not running.

I ran memtest yesterday evening and no errors were found - it ran all 4 tests.

System

-	Provider

[ Name]

Microsoft-Windows-Kernel-Power

[ Guid]

{331c3b3a-2005-44c2-ac5e-77220c37d6b4}

EventID

41

Version

6

Level

1

Task

63

Opcode

0

Keywords

0x8000400000000002

-	TimeCreated

[ SystemTime]

2020-07-03T02:54:38.193559500Z

EventRecordID

33045

Correlation

-	Execution

[ ProcessID]

4

[ ThreadID]

8

Channel

System

Computer

Goodall-Desktop-PC

-	Security

[ UserID]

S-1-5-18

-	EventData

BugcheckCode

0

BugcheckParameter1

0x0

BugcheckParameter2

0x0

BugcheckParameter3

0x0

BugcheckParameter4

0x0

SleepInProgress

0

PowerButtonTimestamp

0

BootAppStatus

0

Checkpoint

0

ConnectedStandbyInProgress

false

SystemSleepTransitionsToOn

0

CsEntryScenarioInstanceId

0

BugcheckInfoFromEFI

false

CheckpointStatus

0

There are no new dmp files.

Any other ideas?

ubuysa · Jul 3, 2020

That kernel-power 41 is not a problem. As I mentioned it just tells you that Windows didn't shut down properly. Nothing more.

Have a look in the Event Viewer to see whether there are any Critical or Error entries just before that Error 41 message time.

TBH I would uninstall WD Backup and leave it uninstalled whilst testing. You don't know what components it has running in the background and it was the cause of the two dumps you got. It's not wise to have it installed at all if you suspect it.

agoodall · Jul 3, 2020

Ok I'll completely uninstall all the WD software.

There are no error events before the kernel 41, a couple after

Error 03/07/2020 03:54:45 PrintService 512 Initialising a print provider (after the shutdown)
Error 03/07/2020 03:54:44 Service Control Manager 7000 None - The GLCKIO2 service failed to start (after the restart)
Warning 03/07/2020 03:54:44 e1rexpress 27 None - (Internet reconnection after the shutdown)
Error 03/07/2020 03:54:43 Eventlog 1101 Event processing - Audit events have been dropped by the transport. 0
Critical 03/07/2020 03:54:38 Kernel-Power 41 (63) - Details say due to the shutdown
Error 03/07/2020 03:54:43 EventLog 6008 None - Details say due to the shutdown

Nothing before this until 9pm

No events before the shutdown under Windows Logs

Is it worth try a reseat of the RAM and unplugging the PSU cables and reseating?

That kernel-power 41 is not a problem

Appreciate that, but whatever's causing it is.

agoodall · Jul 3, 2020

Also - have just realised the NVidia driver 451.48 was released on the 24th June - when these events started. Might try a rollback

ubuysa · Jul 3, 2020

agoodall said:
Ok I'll completely uninstall all the WD software.

I think that's wise, just to be sure.

There are no error events before the kernel 41, a couple after

Events after the restart can't be the cause.

Is it worth try a reseat of the RAM and unplugging the PSU cables and reseating?

Also - have just realised the NVidia driver 451.48 was released on the 24th June - when these events started. Might try a rollback

Both of those are good ideas and useful things to try. BUT, when troubleshooting it's important to try only one thing at a time. See how it goes without the WD backup tool installed, only you know how long to leave it before confirming it's not restarting.

If it still restarts, you can try rolling the graphics driver back. That is always a prime candidate for BSODs, that was well spotted.

If that doesn't help you can try reseating the RAM but I'd have expected Memtest to identify any problem there. Worth doing though. Also reseat the graphics card and any other PCIe cards you have. Generally connectors tend not to come loose - but there's no harm in checking.

One thing at a time though. Softly softly catchee monkey......

agoodall · Jul 4, 2020

2 new restarts - WD software all uninstalled. This time I got bugcheckcodes and 2 new minidumps, the dmp files can be found here

minidump

Folder

1drv.ms

The details are:

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 04/07/2020 20:41:11
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: Goodall-Desktop-PC
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-07-04T19:41:11.175623600Z" />
<EventRecordID>33808</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Goodall-Desktop-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">32</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0xffff0000</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">0</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">0</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">false</Data>
<Data Name="CheckpointStatus">0</Data>
</EventData>
</Event>

and

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 04/07/2020 08:52:02
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: Goodall-Desktop-PC
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-07-04T07:52:02.143523000Z" />
<EventRecordID>33623</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Goodall-Desktop-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">313</Data>
<Data Name="BugcheckParameter1">0x3</Data>
<Data Name="BugcheckParameter2">0xffff850a64ace6f0</Data>
<Data Name="BugcheckParameter3">0xffff850a64ace648</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">0</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">0</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">0</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
<Data Name="BugcheckInfoFromEFI">false</Data>
<Data Name="CheckpointStatus">0</Data>
</EventData>
</Event>

Running a sfc at the moment. Next step will be a reseat of the RAM.

ubuysa · Jul 5, 2020

There's no need to keep listing the error 41 failures. Error 41 is not a problem, it's a symptom.

In your first dump (070420-10937-01.dmp) the error (KERNEL_SECURITY_CHECK_FAILURE) and the failure parameter (3) indicates a driver problem (it's a LIST-ENTRY corruption). The process at fault was RGBFusion.exe.

In your second dump (070420-10937-01.dmp) the error (KERNEL_APC_PENDING_DURING_EXIT) is another driver error but in this case the IRQL of 0 indicates a third party driver. The failing process is 64driverload.exe which after a bit of research seems to be associated with an Epson printer.

I'm, now beginning to suspect your entire system. All the dumps I've looked at for your system show diver failures so I'm starting to think a reinstall may be your best way forward. I suspect you have a serious kernel issue there, possibly from something left over from a driver uninstall in the past.

I would recommend a backup of all your data and a clean reinstall from bootable media deleting all existing system partitions.

agoodall · Aug 9, 2020

Hi all

Restarts have started again. Getting really fed up with this.

I reinstalled windows and everything was good for a little while.

I'm now getting random resets when not doing anything, computer is not under load, temps are fine, exactly as above. I never reinstalled the Western Digital files so it can't be that. Never reinstalled the RGB driver. The printer I did install but I had to to get it to work. I don't have any minidumps this time but do have one MEMORY.DMP, I've uploaded it into the folder above (4th July).

Graphics driver wise I have the latest from 09 July so different to the previous one I was using. The resets occur without using grpahics card anyway (firefox or even idle).

Don't really want to have to reinstall windows every month and neither should I have to. It takes most of a day to reinstall all the apps. Any other way to diagnose the issues?

TIA

ubuysa · Aug 9, 2020

agoodall said:
Hi all

Restarts have started again. Getting really fed up with this.

I reinstalled windows and everything was good for a little while.

I'm now getting random resets when not doing anything, computer is not under load, temps are fine, exactly as above. I never reinstalled the Western Digital files so it can't be that. Never reinstalled the RGB driver. The printer I did install but I had to to get it to work. I don't have any minidumps this time but do have one MEMORY.DMP, I've uploaded it into the folder above (4th July).

Graphics driver wise I have the latest from 09 July so different to the previous one I was using. The resets occur without using grpahics card anyway (firefox or even idle).

Don't really want to have to reinstall windows every month and neither should I have to. It takes most of a day to reinstall all the apps. Any other way to diagnose the issues?

TIA

I'll take a look at your latest dump tomorrow (Monday) and let you know?

Later: The failing module this time is dwm.exe. That's the Windows Desktop Manager, it's responsible for handling the GUI. However, that BSOD (like many) is almost always a driver failure and the driver the DWM uses most is of course the graphics driver.

I've just had to look back to remind myself what we've done already. You could try earlier versions of the graphics driver - use DDU to uninstall each driver and go back four or five versions to see whether you can find one that doesn't BSOD. I see you've already gone back to at least one earlier version though. Other than that, and looking back at the BSODs you've had, I think we'd have to start to suspect the graphics card itself - it seems to be something of a common denominator in many of your BSODs. It's a pity we can't run without it as a test, but we can't (unless you have a spare graphics card lying around?).

I note that you see the BSODs 'without using graphics card anyway (firefox or even idle)' and even at idle the graphics card is still being used otherwise the screen would be blank.

I'm at a loss to know where to go from here other than to suspect hardware. I think your best option is to contact PCS and point them to this thread so they can see all the problem determination you've already done. Meanwhile it would be good if you can find a technique that always (or usually) makes it BSOD because you'll need to tell PCS how to make it fail so they can make it fail on their test bench.

I'm sorry I can't help more.

Random restarts

Active member

Member

Active member

Member

Active member

Active member

Member

The BSOD Doctor

Active member

The BSOD Doctor

Active member

Active member

The BSOD Doctor

Active member

Active member

The BSOD Doctor

Active member

The BSOD Doctor

Active member

The BSOD Doctor