[SOLVED] Continual Crashing/Shut Off - No BSOD

Hawkguy · Oct 3, 2019

Hey All,

Over the past few days I have been experiencing random crashes/shut offs of my PC. It has not prompted a BSOD, it just simply turns off. I am having trouble pinpointing the source (hardware vs software) or going about how to fix it. I am attaching pictures of a few recurring errors I am seeing in the event log, which both seem to pop up around the crashes. Not sure if these are related, but I figured it was pretty coincidental.

Any help troubleshooting next steps would be appreciated.

System Info:
Windows 8.1 64-bit

x BlueRobot · Oct 3, 2019

Could you please post the zip file created from these posting instructions - Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 + Vista

The log files will contain some useful troubleshooting information. Is this a desktop or laptop machine?

Hawkguy · Oct 3, 2019

Thanks for getting back to me. I ran the app last night but got a message from my anti virus saying it contained a program that needed to be quarantined. I wasn't sure if this is normal/my anti virus was being over protective, or if it was something I should bring up.

I will be able to re run and upload later tonight.

x BlueRobot · Oct 3, 2019

Interesting, what AV are you running? Haven't had anyone mention that before. It was likely flagged by your AV program since it accesses %systemroot% to gather dump files etc.

Hawkguy · Oct 3, 2019

Avast was the AV that flagged something. I will run again when I am home later and will include a screen shot if it happens again.

Sorry, didn't think quickly enough last night when it originally happened.

I also wanted to ask, would you prefer a start a new thread once I am able to get the information, or just reply to you in this one with the file and system info?

x BlueRobot · Oct 3, 2019

Have you checked if avast has saved any scan logs? Would be interesting to see why it was flagged.

Please attach the logs in this thread.

Hawkguy · Oct 3, 2019

Hey,

I was able to run the BSOD program. Zip file is attached. Avast did flag it again, but I allowed it to run. I took a screen shot of the Avast message if that helps; was having trouble locating the Avast logs.

Here is the additional system information:

· OS: Windows 8.1
· x64
· What was the originally installed OS on the system? Windows 8.1
· Full Retail Version
· Age of system (hardware) 4.5 years on all except one of the HDD - 2 years on that one. (E drive)
· Age of OS installation - 3 years
· CPU - AMD FX-6350
· Video Card - Sapphire Radeon R9 270X 4GB
· MotherBoard - Gigabyte GA-970A-D3P
· Power Supply - Corsair CX600M

· System Manufacturer - N/A

· Desktop

x BlueRobot · Oct 4, 2019

Thanks, will take a look at the log files tonight.

That virus class appears to be a generic one used by avast, please see here - What is idp.generic? - Appuals.com

Sysnative Windows Update · Oct 5, 2019

Hi!

Is there a chance you could borrow another PSU to see how the machine behaves with another one?

Hawkguy · Oct 5, 2019

I don't at the moment, unfortunately, but I can ask around.

x BlueRobot · Oct 5, 2019

Code:

Event[49]:
  Log Name: System
  Source: Service Control Manager
  Date: 2019-10-02T22:52:40.592
  Event ID: 7022
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MeeseeksBox
  Description: 
The Razer Chroma SDK Server service hung on starting.

Code:

Event[139]:
  Log Name: System
  Source: Microsoft-Windows-DistributedCOM
  Date: 2019-10-02T22:36:44.121
  Event ID: 10010
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: S-1-5-21-4080539554-1439313610-3199883752-1001
  User Name: MEESEEKSBOX\Adrian
  Computer: MeeseeksBox
  Description: 
The server {4AA0A5C4-1B9B-4F2E-99D7-99C6AEC83474} did not register with DCOM within the required timeout.

Code:

Event[409]:
  Log Name: System
  Source: Service Control Manager
  Date: 2019-10-02T19:24:56.900
  Event ID: 7000
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MeeseeksBox
  Description: 
The Steam Client Service service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.

Looks like there is lots of errors similar to the above which seem to be related to hangs. I've also noticed that you seem to have quite a few BSODs in the past.

Could you please disable/remove McAfee and avast while we're troubleshooting and use Windows Defender?

Hawkguy · Oct 5, 2019

I'll go ahead and remove/disable them.

x BlueRobot · Oct 5, 2019

Thanks, due to the nature of some of your crashes and the past BSODs, it may be a good option to try and run Driver Verifier to eliminate any potential software issues - Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista

The DDI Compliance rules will be the most useful option, but please enable all the options that the guide suggests.

However, as @softwaremaniac hinted, this may be due to possible PSU problems as well.

Hawkguy · Oct 5, 2019

Got it. I will be able to run the Driver Verifier this evening and let you know how it goes.

x BlueRobot · Oct 6, 2019

Thanks, please let us know!

Hawkguy · Oct 6, 2019

I followed the directions on the Windows Verifier page. If I'm understanding correctly I just let it do its thing in the background for 24 hours and see if it prompts a BSOD?

Just wanted to make sure I'm getting the next step right and shouldn't do anything in the meantime.

Thanks again for all your help!

x BlueRobot · Oct 6, 2019

Yes, that's right, if it crashes then please stop Driver Verifier and upload the dump files.

You can check it is running correctly by entering the following command in Command Prompt:

Code:

verifier /query

HapaxOromenon · Oct 7, 2019

x BlueRobot said:
Yes, that's right, if it crashes then please stop Driver Verifier and upload the dump files.

You can check it is running correctly by entering the following command in Command Prompt:

Code:

verifier \query

You wrote a backslash (verifier \query) when presumably you meant a forward slash (verifier /query). In another thread I saw you similarly wrote sfc \scannow when you must have meant sfc /scannow. Not a good sign for someone who is supposed to be instructing others on how to troubleshoot Windows problems.

x BlueRobot · Oct 7, 2019

Thanks for noticing that, I'm used to always writing strings for directory paths and not command flags.

Hawkguy · Oct 7, 2019

Hey there,

I let verifier run for a little over 24 hours. It did not prompt a BSOD.

[SOLVED] Continual Crashing/Shut Off - No BSOD

Active member

Attachments

Administrator

Active member

Administrator

Active member

Administrator

Active member

Attachments

Administrator

Inactive

Active member

Administrator

Active member

Administrator

Active member

Administrator

Active member

Administrator

Well-known member

Administrator

Active member