Windows 10: PC reboots before dumping minidump after BSOD

Hi everyone!

I've been having some random BSODs lately, they seem to happen regardless of activity (when idle, browsing internet, games, etc.). I'm trying to diagnose the problem but windows isn't creating minidump files.

When a BSOD happens, the usual sad face screen with "Windows is collecting error info" flashes for a moment. The % complete never rises from 0, and the PC shuts down. It doesn't reboot by itself - HDs stop spinning, the mouse turns off, etc. Only the case "power on" light keeps blinking. Pressing the reset button does nothing. When i press the power button, the pc turns on normally.

I don't know if the BSOD and the shutting down before minidumps problems are one or two different issues. Having no memory dumps makes it hard for me to diagnose. Any ideas?

- Not overclocking
- Minidumps are enabled, proper path, paging file enabled, microsoft error reporting service enabled
- Ran SFC, all ok
- Ran chkdsk, all ok
- Ran windows memory diagnostic tool 2 times, 2 passes each, all OK. Ran memtest+86 once, all ok.
- BIOS up to date
- Windows defender says i'm clean

Attached is the data collection thing. There are 3 minidumps that may be related to the cause of my problems, but none from the past 2 weeks (and plenty of BSODs in that period!).

:)

 

BSOD when resuming from suspend on win10 x64 (CRITICAL_PROCESS_DIED)

Replacing the SATA cable with a new one didn't help. This time however BSODs were different. After the pc was woken from sleep mode it froze for ~15 seconds, then it returned KERNEL_STACK_INPAGE_ERROR and immediately rebooted (didn't produce minidump for
that one unfortunately). After it rebooted it instantly crashed producing MEMORY_MANAGEMENT error and then rebooted. Please find dumps with event log below.

Sendspace.com Mobile File

 

Windows Stopcode Error: Blue Screen 3 to 4 times a day. Microsoft Support guide does not help.

Hi,

There are not any files located at C:/Windows/Minidump, and there isn't a MEMORY.DMP file located at C:/WINDOWS as well. I have used this link to setup the dumps appropriately though, by checking ''Small memory dump'' which was not checked before:

NirBlog » Blog Archive » How to configure Windows to create MiniDump files on BSOD

I will look after next crash whether there are dump files present.

 

The 1/20 8:06 dump shows Nvidia in the active stack trace: nvlddmkm+0x116541

You currently have driver version 376.33 dated 10/12/2016. There is a newer version available from Nvidia, version 378.49 dated 2017.1.24. GeForce Game Ready Driver

 

Well, i updated the driver but still got a couple more bsods. Still no minidums created.

 

Checked this?:

BSOD Minidump - Configure to Create in Windows 10
How to configure Windows 10 to configure Dump Files to be written in the event of a Blue Screen of Death (BSOD).

 

Oh yes, the advanced systems settings is configured to create minidumps and not to automatically reboot, but it doesn't create any and the pc reboots (or "shuts down") regardless. Confirmed the settings via registry, and it's all there.

Tried setting for kernel dumps yesterday, same deal.

 

There are a few drivers shown in den dumps (e2xw10x64.sys, nvlddmkm.sys,...) but I think it goes in the defective Hardware direction.

Den BSOD Codes show causes like "Defective Hardware" and RAM. But u run Memtest right?

Maybe the BSODs are "energy cut off" related. Problems with PSU Voltage or high temps could be the cause. I see error messages in event log too regarding your hard disk (but the are from 2016):

The IO operation at logical block address 0x733f for Disk 3 (PDO name: \Device\00000093) failed due to a hardware error.

The could be the cause that the system can not write the dmp to disk, because the disk ist crashing.

Try to test the disk:






Diagnostic Test

HDD TEST


Run HDTune to check health and scan for errors.







Note It may take some time, but look for signs of any errors or failure.

You can also run a disk check using chkdsk. Refer to the tutorial for details of how to do this.

 

Heya,

Yes, i ran memtest a few times and everything passed. But i'll try to run it again tonight, see what happens. I've got 4 sticks of 4 gb each, would running memtest for each stick individually somehow improve error detection? Or it doesn't matter?

I don't think it's temperature related. I've ran cpu and gpu stress tests, they peak at 68 °C and 81 °C, respectively. Not so bad, considering the ambient temperature was 36°C, hehe. Besides, the pc crashes even when idle.
Could be PSU, yeah. I don't have another one to try right now, unfortunately. It definitely would explain the "shutdowns". But can PSU failure cause blue screens (I've no idea to be honest)?

Oh and Disk 3 was a knowingly about to fail disk from another computer, that i plugged in to recover data. I only kept it in for a couple days or so. Either way, i ran HD tune SMART and error scan checks on my proper disks, and everything seems to be OK.

 

hard to pinpoint the problem because the bsod codes are so different. I analysed again and now I say its 50 % drivers and 50 % hardware related.

Did u run memtest with 8 passes?

Here my results from the analysis, one directs to drivers the other to defective hardware. Its now on you to diagnose yourself. Im out for now, sorry.

Code: 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED (19.01.2017 16:07:06) [Windows 10] CAUSED BY: ntoskrnl nvlddmkm.sys [11.12.2016] * nVidia Video drivers * => Download Drivers | NVIDIA iaStorA.sys [3.06.2015] * Intel RST (Rapid Storage Technology) driver * => Drivers & Software XP e2xw10x64.sys [14.09.2016] Killer e2400 PCI-E Gigabit Ethernet Controller PROCESS: System Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS[/quote] Please update or roll back the red marked drivers.



Code: 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA (19.01.2017 21:59:53) [Windows 10] CAUSED BY: memory_corruption storport.sys [16.07.2016] * Microsoft Storage Port Driver (Windows System File) PROCESS: System CPU STOCK: 3.40GHz MAX: 3800MHz CURRENT: 3400MHz Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS[/quote] Please run memtest again with at least 8 passes. Try to change memory completely with an other model. Check compatibilty on the mainboard manfacturer site. Maybe this RAM ist not officially supported.