Two Random Blue Screen & restarts. Please help.

where do i post the zip file? it says to post it in the original post or something like that. is that safe? it has like information from my pc.

Code:

BugCheck 50, {fffff801dd25ea40, 10, fffff801dd25ea40, 2}Could not read faulting driver name*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : memory_corruption

Code:

BugCheck 139, {3, ffffa90052b6b770, ffffa90052b6b6c8, 0}Probably caused by : ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )

Code:

BugCheck A, {ffffc68d6be2c000, 2, 0, fffff80120223be5}*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : memory_corruption

OLDER BSOD 3/4/2017

Code:

BugCheck 80, {4f4454, 0, 0, 0}Probably caused by : intelppm.sys ( intelppm!MWaitIdle+18 )

2/6/2017

Code:

BugCheck 139, {3, ffffdc80e406f6f0, ffffdc80e406f648, 0}*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : memory_corruption

1/8/2016

Code:

BugCheck 1A, {41201, fffffd80f3e6c008, ffffffff, ffff9b0bc18b87b0}Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+260aa )

Event log:

Code:

{Registry Hive Recovered} Registry hive (file): '\??\C:\Users\Joshua\AppData\Local\Microsoft\Windows\UsrClass.dat' was corrupted and it has been recovered. Some data might have been lost.

Code:

The system failed to flush data to the transaction log. Corruption may occur in VolumeId: G:, DeviceName: \Device\HarddiskVolume6.(A device which does not exist was specified.)

Code:

File System Filter 'wcifs' (Version 10.0, ?2016?-?09?-?15T09:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy5'.  The filter returned a non-standard final status of 0xC000000D.  This filter and/or its supporting applications should handle this condition.  If this condition persists, contact the vendor.

Code:

The driver \Driver\WUDFRd failed to load for the device ACPI\INT3400\2&daba3ff&1.

Code:

Installation Failure: Windows failed to install the following update with error 0x80070430: Intel Corporation - Bluetooth - 4/7/2017 12:00:00 AM - 19.60.0.3.

Code:

{Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

Code:

{Delayed Write Failed} Windows was unable to save all the data for the file \:$I30:$INDEX_ALLOCATION. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

Open administrative command prompt and type or copy and paste:
1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan

When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread

5) Run memtest86+ version 5.01 for at least 8 runs. This may take hours so plan to run it overnight.Memtest86+ - Advanced Memory Diagnostic Tool

Memory problems. - Microsoft Community


For the memory testing please see the above link. Making at least 8 runs is important for memory testing. Sometimes it runs in the teens to find faulty ram.

If the memory test displays no errors the Windows application driver verifier is used to stimulate drivers and make misbehaving drivers produce bsods. The minidump files from the bsods are then debugged. Uninstalling drivers or applications is then performed. New drivers or applications are found that do not produce bsods. Eventually windows driver verifier is used for 36 hours of typical computer use. If there are no longer any bsod the troubleshooting will be completed and preventative maintenance will have been performed.

In order to use windows driver verifier you must back up your files, create a restore point, and become familiar with the windows recovery or advanced troubleshooting menu.

To become familiar with the windows advanced troubleshooting menu open administrative command prompt and type or copy and paste this command: shutdown /r /o /f /t 00
You will reboot to the windows recovery or advanced troubleshooting menu.
Then you will navigate to startup options (not startup repair) and in startup options you will restart and select #6 safe mode with command prompt. When you turn off windows driver verifier you will type or copy and paste: verifier /reset
Then you will reboot to the desktop. On the desktop you will use 2 software programs to analyze the bsod: Bluescreenview and Whocrashed. With their analysis you will then use device manager and/or control panel to uninstall any misbehaving drivers or applications.
To continue troubleshooting you can either find a driver to reinstall or continue using windows driver verifier to find the next misbehaving driver. It is personal preference whether to uninstall the install or uninstall all first and then reinstall later. The end result should be the same.
When bsod are produced by windows driver verifer they will display a stop code. The stop code is typically driver verifier detected violation. Sometimes the misbehaving is displayed in the form *.sys. If you see the misbehaving driver identified please record it for later use.

Before using windows driver verifer make sure you change the bsod so that automatic restart is unchecked allowing you time to view the bsod:
BSOD Finding and fixing them - Microsoft Community

This link has the customized settngs for using windows driver verifier:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community


The analysis of the bsod may vary. Each software may offer additional information.
These are the 2 software to download and install so that you can immediately process the bsod:


http://www.resplendence.com/whocrashed
Blue screen of death (STOP error) information in dump files.




After the bsod please upgrade the zip file or post a new one so that we can debug the bsod minidump files.


Commands to turn on and off windows driver verifier:
To turn on windows driver verifier: In the left lower corner search type: verifier
To turn off windows driver verifier: you must be able to move from a bsod to the windows advanced troubleshooting menu and then navigate to startup options then safe mode with command prompt and type or copy and paste: verifier /reset
At times the startup options safe mode command verifier /reset will not turn off windows driver verifier. There are two additional options. Option one is to navigate the windows advance troubleshooting menu to command prompt instead of startup options. This is command prompt that opens Administrator: X:\windows\system32\cmd.exe
You will type or copy and paste this command: verifier /bootmode resetonbootfail
If this second method does not turn off windows driver verifier you will need to use the windows advanced recovery menu to restore with the restore point that you created before using windows driver verifier.



We will wait for the results of the administrative command prompt commands and 8 runs of memory testing.

Again you must back up files, create a restore point, and be comfortable with the windows advanced recovery menu in order to use the windows driver verifier tool to find misbehaving drivers.