Windows 10: Random crashes and (seemingly) related issues

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.

:)

 

Constant Crashing / BSOD

Hey. I've been having issues with my computer crashing or bluescreening. The time inbetween the crashes are random, and the messages in the BSOD's are seemingly random. If you need anything to help ID the problem, please let me know.

Thanks for your time

 

LiveKernelEvent in reliability history "A problem with your hardware caused Windows to stop working correctly."

Method 1:

No issues were found.

Method 2:

The rash happens at random and I have no idea what's causing it. Sometimes it happens twice in an hour, sometimes i go days without crashing. So wouldn't this test be likely inconclusive since not crashing can be attributed to "chance" since it is seemingly
random?

 

Hello and welcome aboard. *Smile

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.

 

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

BSOD data attached.

 

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.[/quote] 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, seh 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.

 

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.

 

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.

 

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.

 

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 DisableRun 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.

 

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

 

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 ---------[/quote] 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)[/quote] 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.

 

Oh...That would explain a lot...I thought I got rid of it because that's actually the driver that destroyed my secondary drive a few months ago, but apparently not. I know it's unstable, and I don't need it at all. How can I get rid of it?

 

C:\Windows\System32\Drivers

Seh for it there and delete it.

Then continue with Driver Verifier for any such misbehaving driver.

 

Hey
I have been battling with random freezes on windows 10 for 7 months, and I finally might have found a solution that worked for me. I've noticed similar issues with many so I thought about it might be good to let you know what worked for me. (Usually I just got hard freezes, sometimes different kind of bluescreens, but the lockups seemed to be very random. Sometimes daily, sometimes there were several days without any issues)

Intel Turbo Boost Technology. My motherboard has it enabled by default, and after I disabled it, I have been able to run windows 10 now 7 days without a single problem. I have the problem with task manager that shows 100% cpu usage, so there is somekind of communication issue between windows 10 and some motherboards. Maybe that together with turbo boost technology is the cause for random freezes.

For some updating bios has solved both the freezes and cpu usage failure, but in some cases updating bios is not a good option. (like in my case the bios update is meant for ivy bridge cpu's while I run sandy bridge) Updating bios kind of makes sense, if the problem actually lies in motherboard settings.

Basically having that technology enabled, computer kept overclocking cpu's whole time, hopping between 3300 MHz to 3800 MHz even if I didnt do anything. After I disabled it, clocks went to normal and stayed steady. No crashes anymore. I did run this same computer overclocked with windows 7 without issues, so it's not a about hardware or temperature issue at least for me.

So I think it's worth for some to check if this option helps, or if I'm just having a 7 day lucky streak. Keeping my fingers crossed as this problem has been driving me nuts.