BSOD from cold boot WIndows 10 1803 (17134)

Jul 6, 2018
8
0
10
When the computer is started from cold boot in the span of 5-10 minutes the keyboard and mouse stop responding and restarts. After the restart the computer is stable.

Power options high performance, fast boot turned off (bios and windows)

OS: Window 10 64 Bit
CPU: Intel core i7 4.00ghz 6700k
Motherboard: msi 7998
GPU: GTX 970 Nvidia
SSD: Samsung 850
HDD: WD 1TB
32 gig ram


Kernel Dump:
https://drive.google.com/open?id=1aW_-Rn8ULNu6aAVSonM1_wz_jLV1B1tu

Any suggestions?
 
Do you have Live Update 6 installed? You can find it on the utility page here IT is made by MSI and designed to make sure you have latest motherboard drivers and BIOS.

My 1st place to look would be drivers since you say it works fine after a restart., But then with fast start up off, that shouldn't make any difference.

What PSU do you have?
 
My PSU is EVGA SUPERNOVA 550 G2 80 PLUS GOLD. I installed live update 6, and it's just software stuff.
 
Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/CVBd.html

File: WATCHDOG-20180706-1046.dmp (Jul 6 2018 - 10:46:02)
BugCheck: [VIDEO_TDR_TIMEOUT_DETECTED (117)]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by: nvlddmkm.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 10 Min(s), and 47 Sec(s)

The nvlddmkm.sys file is a NVIDIA graphics card driver. There are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/ or you can allow Windows Update to download the driver for you, which might be a older/better version.

I can't help you with this. Wait for additional replies. Good luck.
 
Used DDU in safe mode. After the clean up it froze again (used reset button). Back again, let windows update handle it. It installed 22.21.13.8205 display driver (382.05). Time to test the results, will keep you posted.

Played a game for a bit and windows crashed 5minutes in. Tried looking for a dump file but none was created. Removed 382.05 and now trying 398.36 driver.
 
should remove super anti spyware from 2011

Is sentinel System driver for USB you need in PC to run software? Its from 2008, they really should upgrade it. I don't suppose there is a newer version?

Might need to test GPU works in another PC as it could be the cause and not drivers.
 
For the sentinel driver no.

Currently on 398.36, haven't experienced bsdo from cold boot, but a new weird problem arises. Sometimes from cold boot it will go straight to to the bios menu. Little corncering because when I was changing options it froze. (After 2 more times)The Factory setup was legacy+UEIF, I changed it to UEIF only.

Is it possible to factory reset the BIOS version?
 
from your manual

Resetting BIOS

You might need to restore the default BIOS setting to solve certain problems. There are several ways to reset BIOS:
● Go to BIOS and press F6 to load optimized defaults.
● Short the Clear CMOS jumper on the motherboard.
● Press the Clear CMOS button, on the rear I/O panel. (Only for the motherboard with clear CMOS button.)

You should only need to use the 1st one.
 
I ran the new dump files through the debugger and got the following information: https://pste.eu/p/EPiG.html

File: WATCHDOG-20180709-1856.dmp (Jul 9 2018 - 18:56:13)
BugCheck: [VIDEO_ENGINE_TIMEOUT_DETECTED (141)]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by: nvlddmkm.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 03 Min(s), and 28 Sec(s)

File: WATCHDOG-20180709-1858.dmp (Jul 9 2018 - 18:58:03)
BugCheck: [VIDEO_ENGINE_TIMEOUT_DETECTED (141)]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by: nvlddmkm.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 38 Sec(s)

I can't help you with this. Wait for additional replies. Good luck.
 
TDR stands for Timeout Detection and Recovery. This is a feature of the Windows operating system which detects response problems from a graphics card, and recovers to a functional desktop by resetting the card. If the operating system does not receive a response from a graphics card within a certain amount of time (default is 2 seconds), the operating system resets the graphics card.
Before TDR existed, problems of this nature would have resulted in a system freeze and required a reboot of the operating system. If TDR is enabled and you see the TDR error message, "Display driver stopped responding and has recovered," this means that the Windows operating system reset the display driver.

Need to see if GPU works in another PC. Its still blaming Nvidia drivers

I have a GTX 980, no problem with the drivers so I would look at hardware

check the power cables attaching GPU to PSU are attached firmly, perhaps try other cables if PSU has spares
 
Just a update:
The tdr now seems to be...inconstant now? I had days of cold boot startups with no resets and other days with.

Don't have a spare card around atm. I'll keep here posted when I do.
 
you should provide the most current memory dump. the old one has drivers that you should have removed by now.
(I would also remove PxHlpa64.sys Mon Oct 17 07:29:34 2011
old sonic cd driver)

and update the intel storage driver:
iaStorA.sys Wed Nov 4 02:27:49 2015

you should also change the memory dump type from a minidump to a kernel memory dump.
the kernel memory dump will provide more debug info and show all of the interrupts the hardware is using as well as info on the USB subsystem.

usb devices when removed will just have the device driver hidden. Some old drivers had programming mistakes and would respond to incorrect packets. this would cause devices to not receive there usb packet so it will look like a hardware failure. in newer machines the usb hardware is serviced by the pci/e bus. errors on this bus can cause delays to the GPU, if the delay is over 2 seconds then the TDR starts to kick in.

any way, at least go into control panel, check the option to show hidden usb drivers and remove devices that have been removed from the machine.
you could also download usbview.exe use this version https://www.uwe-sieber.de/usbtreeview_e.html to check for problems in usb

factory overclocked GPU can miss hardware signals and cause this error.
confirm the BIOS pci bus clock is running at 100Mhz (not over or under clocked)

could not read bios info from the memory dump, can indicate a out of date bios version or corruption while storing the memory dump. (update the storage drivers from the motherboard vendors website, or put the drive on a new SATA port (low port number and the sata controller supported by the cpu chipset is most likely to work)

 
overall i think the likely cause of the problem is going to be
SUPERAntiSpyware keeping files open and blocking the uninstall of the driver and triggering some power management issues because of the delay.

it could also be one of the other devices on the usb 3 bus taking packets that are not for that device. puting the mouse and keyboard on the slower USB 2 bus would isolate them from the other devices to rule out that as a cause.


i would still go to msi website and look for a update to the usb 3 driver and make sure your bios version is updated with the driver (if there is a update)
---------------

here are usb devices on usb 3
Logitech USB Keyboard Speed: Low
USB Receiver Speed: Full
Basic Optical Mouse Speed: Low
MX490 series Speed: High
TOURO Mobile Speed: Super


i would move the keyboard and mouse to a usb 2 port
look for a update for your usb3 driver
\SystemRoot\System32\drivers\asmthub3.sys Sun Jul 10 23:44:38 2016
(from your motherboard vendors website)

remove SUPERAntiSpyware it is from 2011 (too old and will cause problems)
you might remove your overclock software NTIOLib_X64.sys
(but i don't think it is the cause of the problem)
-----------
last bugcheck looked like it was coming from the power management code


will see if i can figure it out when I get back from breakfast
(system shows that you have two devices that they system is attempting to remove but the system is has to wake the device before it can remove the device since the driver is using resources)

info:
ServiceName is "i8042prt"
State = DeviceNodeRemoved (0x312)
Previous State = DeviceNodeRemovePendingCloses (0x311)
StateHistory[09] = DeviceNodeRemovePendingCloses (0x311)
StateHistory[08] = DeviceNodeStartPostWork (0x307)
StateHistory[07] = DeviceNodeAwaitingQueuedRemoval (0x30f)
StateHistory[06] = DeviceNodeStartPostWork (0x307)
StateHistory[05] = DeviceNodeStartCompletion (0x306)
StateHistory[04] = DeviceNodeStartPending (0x305)
StateHistory[03] = DeviceNodeResourcesAssigned (0x304)
StateHistory[02] = DeviceNodeDriversAdded (0x303)
StateHistory[01] = DeviceNodeInitialized (0x302)
StateHistory[00] = DeviceNodeUninitialized (0x301)
StateHistory[19] = Unknown State (0x0)
StateHistory[18] = Unknown State (0x0)
StateHistory[17] = Unknown State (0x0)
StateHistory[16] = Unknown State (0x0)
StateHistory[15] = Unknown State (0x0)
StateHistory[14] = Unknown State (0x0)
StateHistory[13] = Unknown State (0x0)
StateHistory[12] = Unknown State (0x0)
StateHistory[11] = Unknown State (0x0)
StateHistory[10] = Unknown State (0x0)
Flags (0x2c002030) DNF_ENUMERATED, DNF_IDS_QUERIED,
DNF_HAS_PROBLEM, DNF_NO_LOWER_DEVICE_FILTERS,
DNF_NO_LOWER_CLASS_FILTERS, DNF_NO_UPPER_DEVICE_FILTERS
UserFlags (0x00000002) DNUF_DONT_SHOW_IN_UI
CapabilityFlags (0x000000c0) UniqueID, SilentInstall
Problem = CM_PROB_DEVICE_NOT_THERE
Problem Status = 0x00000000




 
https://i.imgur.com/84oiyKS.png
https://i.imgur.com/uOhXtbV.png

Both of those are at the current version. No update release in 2018 so far. Deleted the sonic driver and remove super-antispyware (rip). Updated Bios to current release. Moved the m/kb to the usb 2.0 ports. Updating to the new nvidia driver (August release).

Let's see what happens now.
 

TRENDING THREADS