Random crashes and (seemingly) related issues

hadesflames · 19 May 2016

I've been experiencing for a while an issue where my laptop will randomly freeze completely. At that point I'm left with no alternative but to hard reboot the laptop by holding the power button. Usually when this happens, any sound that might have been playing will freeze as well leaving that "stuck" (for lack of a better word) noise we're all probably used to. Sometimes the sound will keep playing normal even though the laptop won't accept any input. Other times the sound will "slow down" sort of as if the entire pc were experiencing massive lag. I have no idea what causes this and can't reproduce it at will. But I have had it happen to me in quick succession (within an hour or so) before.

When I scan through the event viewer, I notice this:

https://i.imgur.com/WL69YGI.png

Each time. Each of those warnings is for a different thread in the processor, 0-7.

Another strange thing that I suspect is related that happens from time to time is that I won't be able to click anywhere on my screen but the system isn't completely frozen as it will still take input from the keyboard. A quick ctrl + alt + del "resolves" this issue temporarily, but it always happens again eventually of course.

I contacted MSI about this but they told me it had to be a windows issue and they couldn't help me with that.

Arc · 19 May 2016

Hello and welcome aboard. :)

Please post a reply following the Blue Screen of Death (BSOD) Posting Instructions ? Well, a Kernel Power event is not always a BSOD issue, but those files will help us to have a closer look to the issue and the overall system.

Also, publish a Speccy snapshot: Speccy - Publish Snapshot of your System Specs. It will help to to see the areas which will not be covered by the above, like system temps.

hadesflames · 19 May 2016

Speccy: http://speccy.piriform.com/results/3...vl3GAlkbumqfhU

BSOD data attached.

Arc · 19 May 2016

Well, there was BSODs ....

Code:

Event[6538]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2016-04-14T03:03:35.354
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: AldoBarreras-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x000000000002e0cf, 0x0000000000000002, 0x0000000000000000, 0xfffff8039ad45212). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 8b9a4b4a-5f27-46a6-898c-65ba8c8b55ce.

It says that the dump was recorded, but the zip you uploaded does not contain any crash dump. It will be needed.

Follow it: BSOD Minidump - Configure to Create in Windows 10
Go to Option Two, "Small Memory Dump". Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any disc cleanup tool before you upload another zip.

hadesflames · 19 May 2016

It has to be unrelated. That BSOD was well over a month ago and I honestly didn't even remember it. The freezing thing happens on a daily basis.

Arc · 19 May 2016

That may not be unrelated. The event log reports a number of abnormal shutdowns .... may be some forced shutdowns by you due to the freezes, but as there is/was hints of BSODs, IMHO it would be the best place to start with.

hadesflames · 19 May 2016

Sure. I'll enable the minidumps and wait for a BSOD that might never come. In the meantime, let's proceed as if there were no hint of a BSOD. If a BSOD happens I'll post it.

As for the abnormal shut downs, considering the PC freezes at least once a day, forcing me to hard reboot it, it's only natural that the event log would contain a lot of abnormal shut downs.

Arc · 19 May 2016

The job starts from enabling dump recording.

Now, what may cause a system freeze? Broadly we may categorize it in two fields: hardware related causes and software/driver related causes.

First of all, we will concentrate on finding any failing driver. In order to do it, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Now the crash dump recording becomes important. If Driver Verifier causes a BSOD, let us see the dumps.

hadesflames · 19 May 2016

Alright, just experienced another crash with minidumps and DV enabled. Dump is attached, not sure if you need anything else.

Arc · 19 May 2016

It is pointing to Scarlet Crush Scp DS3 Driver.

Code:

BugCheck C9, {21f, fffff800c8ffb174, ffffe0011efc5a70, 0}

Unable to load image ScpVBus.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ScpVBus.sys
*** ERROR: Module load completed but symbols could not be loaded for ScpVBus.sys
Probably caused by : ScpVBus.sys ( ScpVBus+b174 )

Followup:     MachineOwner
---------

It seems that the driver is old.

Code:

    Image name: ScpVBus.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon May 06 03:01:26 2013 (5186CFAE)

Make it sure that this driver supports Windows 10. If not, get a driver that is windows 10 compatible. Unfortunately I dont know a source to get it.

Let us know the situation after making this change.