Windows 10: Computer rebooted from a bugcheck

Hello,

Looks like my computer is rebooting seems from a bug check. I have seen it do this before seems to happen when left idle overnight never happens during use.

Please let me know if more information is required than what is in the logs.

:)

 

The computer has rebooted from a bugcheck. bugcheck was: 0x00000050

I keep getting this error code while starting up my PC. I tried searching online for help but couldn't find anything. How can I fix this?

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffffdb8aa2af2ffe, 0x0000000000000000, 0xfffff802e132414d, 0x0000000000000002). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 182a8abe-364f-4371-8a0f-cba22de2146a.

 

The computer has rebooted from a bugcheck. bugcheck was: 0x00000050

Hi SebastianCaraveo,

Based on the information that you provided, we suggest that you perform a repair upgrade of your Windows 10 computer. Refer to the link below for instruction and guidelines on how to repair your system.

How to: perform a repair upgrade using the Windows 10 ISO file

Let us know if you need further assistance.

 

It looks like there is something not quite right with your CPUID CPU-Z installation. A driver is triggering the crash:

Code: FAILURE_BUCKET_ID: AV_cpuz138_x64!unknown_function BUCKET_ID: AV_cpuz138_x64!unknown_function PRIMARY_PROBLEM_CLASS: AV_cpuz138_x64!unknown_function BugCheck A, {a67e78c, f, 1, fffff800064331a7} *** WARNING: Unable to verify timestamp for cpuz138_x64.sys *** ERROR: Module load completed but symbols could not be loaded for cpuz138_x64.sys *** WARNING: Unable to verify checksum for win32k.sys Probably caused by : cpuz138_x64.sys ( cpuz138_x64+2084 )[/quote] Try reinstalling CPU-Z or uninstall it if you no longer use it.

 

Thanks, just removed it, will monitor of the next few days!

 

Please run the beta log collector and post a new zip into this thread:
log collector v2-beta08.zip
(extract > open)

 

Unfortunately it appeared to happen again.

Is there a specific tool that I should use to traverse the logs myself?

 

It looks like it is the same driver so you are going to have to manually find the file and remove it. There must be an entry somewhere in the start-up sequence that calls for the driver to load.

There is a useful program called Autoruns that you can use to find startup tasks on your PC and disable them.

Here is the driver file location: cpuz138_x64.sys 26/02/2015 6:04:34 PM
\??\C:\Users\Matt\AppData\Local\Temp\cpuz138\


I use WinDBG to examine the mini-dump file created by the BSOD crash event. You can read up how to use it here.

 

Thanks Phil!

Found the culprit to be Corsair Link reinstalling the file and blocking deletion but got it all sorted now.

Thanks for the tools and info, will keep an eye to see what happens after I install the latest version of Link