Windows 10: BSD's are pretty constant over the past few weeks...

Hi,

I don't post here much but I'm thankful for the help. I've followed the rules and did the download and have the zip ready to upload.

My issue, *I THINK*, may be causes by some faulty NVIDIA drivers. At first I thought it was my external hard drive set up but even with nothing attached the USB ports, front of the computer or the more stable ones in the back, I still just got one.

I've even uninstalled the NVIDIA drivers and upon rebooting they reinstalled from some hidden area on the system. Right now I'm OK but it's only a matter of time before the next one. If I were a casual user it would be an annoyance but I'm a graphics artist, so I need this fixed before I dare continue with a project in ZBrush or Photoshop, don't feel like loosing all my hard work.

Thanks so much. Hopefully someone can help me figure this out and get it fixed up.

Richard *Shock

:)

 

Random BSODs over the last few weeks

Uninstall networx, at least temporarily and see if the issue goes away.

 

Random BSODs over the last few weeks

Deleted the .tmp file.

I have tried to use Driver Verifier many times now but I can never get into Windows and end up having to do a restore. I see on the link you gave me it says to use safe mode, but considering my BSODs are happening almost weekly, am I expected to try and
use my PC normally in safe mode every day for as long as possible?

 

Did you uninstall the drivers from device manager or programs and features? Best to remove ALL Nvidia programs from the unit and download a fresh copy. Make sure you check Network Adaptors just incase you have a Nvidia nForce ethernet *Smile

 

Hi, I belong to a forum for making 3D stuff and asked there as well. They turned me on to this little program called DDU and yup, it took it all out and then rebooted again. I then allowed Windows to install the new NVIDIA drivers so it's really clean and without all the extra junk I get from the full download from NVIDIA. Things seem stable for now so fingers crossed once again!

 

Hi, Back again.

Not sure what to check now. I experienced another BSD last night. I plum forgot to to get the code but with the drivers minimally installed without all the other crap that NVIDIA likes to install not really thinking it's that now. I did get a new monitor and a new sound bar but I hardly think it's those. The HDMI cable from the TV/Monitor is a one of those fancy gold types. The sound bar only connects with a USB port for power and the usual green audio and pink mic inputs. I've done hd checks, all are checking out fine. Memory modules are also checking out. Not sure if I should check to see if I'm loosing power via my outlets ... been almost a week since my last post so it's not as often but something else is amiss here I think. I've turned off my back up drives for a while to see what happens with them off if it's going to start up again regularly.

Any input or ideas are appreciated.

Thank you,
Richard

 

Can you post a new set of logfiles? We can check to see if it is the same cause.

Your previous BSOD codes were 0x116: VIDEO_TDR_ERROR

A VIDEO_TDR_ERROR always relates to the system's graphics card (TDR = Timeout Detection Recovery). This could be down to a number of reasons including drivers, heat, power to the card, a faulty PCI-e slot or simply a defective GPU. It's in your best interests to employ common sense trouble shooting techniques in these situations.

• Try later and/or earlier drivers
• Measure the GPU's temperatures at idle and under load
• Ensure the GPU is free from dust build up and that the fan is working correctly
• Reseat the GPU and check all connections are securely made
• Check PSU voltages in BIOS
• Try a different card in the system

 

OK, will do. Something I just noticed. Not sure if this could be something to look into. My wireless Logitech Marble Mouse or what ever they are calling it these days, when this BSD that JUST NOT HAPPENED I touched the button and began using the mouse and then blue screen. So I switched it out with a new mouse (also a marble type) to see if newly loaded drivers and what not would work out..

 

OK, here is the new zipped info...

Thank you!

 

The crash dump from today shows the same error:

Code: BugCheck 116, {ffffba8e03416010, fffff8013a1c6b2c, 0, 1} Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys *** WARNING: Unable to verify checksum for win32k.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+176b2c )[/quote]

 

OMG. What now then. I have new drivers on board. Used that little program to completely dump ALL of the NVIDIA drivers to the point where the MS Updates module found them on the server to install. I'm blown away. This has to be on NVIDIA side then, they released this faulty mess. Grrrrrrrrrrr

 

Refer back to my earlier post #5 - there are several things to test related to the physical aspects of the GPU card and the temperature it runs at.

 

• Try later and/or earlier drivers - Will probably have to do that!
• Measure the GPU's temperatures at idle and under load - Idle temp, iirc, is nice and cool
• Ensure the GPU is free from dust build up and that the fan is working correctly - Yes
• Reseat the GPU and check all connections are securely made - Did that
• Check PSU voltages in BIOS - Not sure where to look for that info! *Shock
• Try a different card in the system - Only own the one card!

 

OK, seems OK for now after doing the whole "boot into Safe Mode" and uninstalling the NVIDIA drivers and reinstalling them. Then there was a huge update to Windows a day or so ago and from what was reported there was a time stamp issue for the drivers but perhaps that was on the MS side of things? Seems stable now in any case. Thanks for all the help!

 

In addition to the VIDEO_TDR_ERROR there were problems noted with the drive (paging errors, corruption of the MFT, etc.).
The RAM modules are mismatched.
The BIOS is version F4 and the latest version is F6

For all tests / steps please post images into the thread.
If there are problems posting images please use one drive or drop box share links.

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) 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 edit then copy > paste into the thread
5) chkdsk /x /f /r
This may take many hours so plan to run overnight
6) Use the information in this link to find the chkdsk report in the event viewer and post the report into the thread using a one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials
7) The BIOS: BIOS Version/Date American Megatrends Inc. F4, 7/13/2016 SMBIOS Version 3.0
8) Upgrade the BIOS: F4 > F6

The RAM modules are mismatched:
DDR4 3000 2OZ
CMK16GX4M4B3000C15
There are 4 GB modules in each DIMM with total RAM 32 GB.
This would take a lot of time to check during one continuous session.
The RAM modules could be checked as 16 GB at a time.
(Be sure to have the mismatched RAM modules tested simultaneously) (Use 2 RAM modules of each type during the test)
This way you could check the mismatched RAM modules at the same time and the multi-channel capability of the motherboard.

9) Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 32 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM BSOD Tutorials

10) Run HDTune:
HD Tune website
to check the health,
scan for errors, no quick scan but full scan
run a benchmark.
It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following
the health,
the error scan,
the benchmark incl. following
transfer rate,
access time,
burst rate,
cpu usage.
Take Screenshot in Windows 10 General Tips Tutorials