Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {1, 1e00, fffff800074e9378, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
Hi,
nice job with the bios update.
Although the above dump file isn't opening properly I can see enough details via whats called a stack trace to see that the Nvidia gpu driver was the cause with this bsod.
You sent three dump files, one is a bugcheck 124 and two are like the above.
You may have some corruption within the gpu driver and Windows 10.
To clear the gpu corruption, uninstall the current driver using the DDU or
Display Driver Uninstaller.
You must run this in safe mode (disconnect from the net too just so windows won't install a driver via Windows updates)
Once back in windows pop your driver (update to the latest version if need be) back on windows.
Run these scans which hopefully will cure any corruption within the system:
Open an administrators command prompt (you can find command prompt in the start menu under 'windows system', simply right click on it and run as admin). Type (or copy and paste):
sfc /scannow
Press enter and await results.
In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).
If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.
Hope this helps. Please post any new dump files after making the above changes.
If you ran Furmark ok then chances are your card is fine, we just need to find the culprit.
