[SOLVED] BSOD will not auto restart

beefboy2

Distinguished
Oct 6, 2013
34
1
18,535
0
Every time the Blue Screen of Death appears, which is too frequently for my taste, it becomes stuck at 100% and will refuse to restart. I uploaded a the minidump folder to google drive for that information. Thanks for any help!
 

PC Tailor

Judicious
Ambassador
tried to update some windows updates as suggested and now i can not access the start menu. restarted several times and still persisting.
Did you test your storage drive also?
Based on what I saw with the collection, I'd say your updates are failing and there is some corruption in the OS.

You can run CHKDSK and SFC to sort this, but there will be something likely causing the corruption. Tie that in with the dump files previously, one could suspect your drive is faulting.
 
Reactions: beefboy2

Lutfij

Titan
Moderator
When you say too frequent, can you state what triggers the issue? Please include your system's specs like so:
CPU:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Case:
OS: version for Windows 10

How old is the PSU and what is the make and model of the unit?
 

Colif

Win 10 Master
Moderator
The BSOD.,.. I wish there was just 1 code, it would make solving them way easier.

I will ask someone to convert dumps so I can read them.

Lutfi... you should be more clear about windows version, do you want Home/Pro or the version number?
 

gardenman

Admirable
Moderator
Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/mn3vp0t1/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.
File information:093020-8562-01.dmp (Sep 30 2020 - 12:38:49)
Bugcheck:UNEXPECTED_STORE_EXCEPTION (154)
Probably caused by:hardware_disk (Process: MemCompression)
Uptime:1 Day(s), 11 Hour(s), 41 Min(s), and 20 Sec(s)

File information:092920-10250-01.dmp (Sep 28 2020 - 18:51:54)
Bugcheck:UNEXPECTED_STORE_EXCEPTION (154)
Probably caused by:hardware_disk (Process: MemCompression)
Uptime:27 Day(s), 17 Hour(s), 28 Min(s), and 41 Sec(s)

File information:090120-7968-01.dmp (Sep 1 2020 - 01:12:30)
Bugcheck:KERNEL_DATA_INPAGE_ERROR (7A)
Probably caused by:memory_corruption (Process: wuauclt.exe)
Uptime:4 Day(s), 12 Hour(s), 03 Min(s), and 07 Sec(s)

File information:082720-10015-01.dmp (Aug 27 2020 - 11:29:41)
Bugcheck:UNEXPECTED_STORE_EXCEPTION (154)
Probably caused by:hardware_disk (Process: MemCompression)
Uptime:21 Day(s), 18 Hour(s), 17 Min(s), and 10 Sec(s)

File information:062520-10406-01.dmp (Jun 16 2020 - 14:11:00)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process: MemCompression)
Uptime:3 Day(s), 17 Hour(s), 55 Min(s), and 47 Sec(s)

File information:061020-6921-01.dmp (Jun 10 2020 - 11:43:53)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: Registry)
Uptime:1 Day(s), 18 Hour(s), 32 Min(s), and 43 Sec(s)

File information:020920-10296-01.dmp (Feb 9 2020 - 02:12:15)
Bugcheck:UNEXPECTED_STORE_EXCEPTION (154)
Probably caused by:hardware_disk (Process: MemCompression)
Uptime:8 Day(s), 4 Hour(s), 42 Min(s), and 42 Sec(s)

File information:013120-5890-01.dmp (Jan 30 2020 - 14:11:09)
Bugcheck:CRITICAL_PROCESS_DIED (EF)
Probably caused by:memory_corruption (Process: svchost.exe)
Uptime:0 Day(s), 0 Hour(s), 18 Min(s), and 27 Sec(s)

File information:010520-12468-01.dmp (Jan 5 2020 - 20:45:40)
Bugcheck:KERNEL_DATA_INPAGE_ERROR (7A)
Driver warnings:*** WARNING: Unable to verify timestamp for msrpc.sys
Probably caused by:memory_corruption (Process: stacsv64.exe)
Uptime:12 Day(s), 7 Hour(s), 54 Min(s), and 33 Sec(s)

File information:103019-7859-01.dmp (Oct 30 2019 - 09:00:59)
Bugcheck:SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:memory_corruption (Process: Registry)
Uptime:0 Day(s), 13 Hour(s), 10 Min(s), and 53 Sec(s)
System: HP Pavilion dv6 Notebook
There is a BIOS update available for your system. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 10 Master
Moderator
wishes it was only 1 BSOD now...

its possible using LAN drivers from 2011 is cause of some problems.
Aug 23 2011Rt64win7.sysRealtek 64 bit Windows 7 driver http://www.realtek.com/
See if the newer ones help - https://www.realtek.com/en/component/zoo/category/network-interface-controllers-10-100-1000m-gigabit-ethernet-pci-express-software

@Lutfij specs
CPU - Intel(R) Core(TM) i5-3210M
Motherboard - well, its a HP so I assume that won't help really.
HP Pavilion dv6 Notebook PC
RAM - 8gb F3-12800CL9-4GBSQ 2 x 4gb sticks
Storage info actually interests me as many of the actions occurred while PC was talking to storage.
GPU - NVidia (I can't tell what)
PSU/Case = its a Notebook.

I can't see any drivers mentioned in crashes but lan could be part of problem based on drivers age
 

PC Tailor

Judicious
Ambassador
If you do encounter another error (wait at least 48 hours or however long you usually went without a BSOD we want to make sure it doesn't reappear) - then please post your dump files as per this guide


The guide is for Sysnative, but run the collectionapp and then post that instead of just the dump file. As some of the other info collected could be useful for this one.
 

PC Tailor

Judicious
Ambassador
I have run the dump file(s) and you can see the full report(s) in the link below.
If you are prompted to "Run only if trusted" simply click play/run and the html will be viewed. This warning is always present.

Report: https://jsfiddle.net/agw5hv14/show/

Summary of findings:
SYSTEM_SERVICE_EXCEPTION
Probably caused by : ntkrnlmp.exe ( nt!HvpGetCellPaged+a2 )
I can also see from the event viewer items there are quite a few errors relating to failed Windows updates. This one as well as some of the previous ones point to an I/O error. As well as some errors relating to reading/writing to write protected storage.

I'll leave this one for @Colif to look through still but personally I'd recommend also running SeaTools LONG test to check your storage drives also (guide below) - assuming your windows and all optional updates (button underneath check for updates in Windows Update settings) have been installed?


Rich (BB code):
1: kd> .trap ffffd684`87bf0520
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000007
rdx=0000000000010ea8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80509fd81b2 rsp=ffffd68487bf06b8 rbp=ffffd68487bf07f9
r8=000000000000001c  r9=ffff99096350c080 r10=000001bae03e1ea8
r11=0000000000000ea8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!HvpGetCellPaged+0xa2:
fffff805`09fd81b2 418b02          mov     eax,dword ptr [r10] ds:000001ba`e03e1ea8=????????
 
Last edited:

Colif

Win 10 Master
Moderator
PC, in your 3rd party drivers listing, have you somehow marked Nviddmkm.sys as a Microsoft driver? I can't see it in your listing but it does show in gardenman's and I noticed it was absent from another dump I did earlier, which seemed strange.

its is possible the PC runs off Intel CPU while on desktop but then the drivers show in https://jsfiddle.net/mn3vp0t1/show from 2 days before.
 
Last edited:

PC Tailor

Judicious
Ambassador
PC, in your 3rd party drivers listing, have you somehow marked Nviddmkm.sys as a Microsoft driver? I can't see it in your listing but it does show in gardenman's and I noticed it was absent from another dump I did earlier, which seemed strange.
No it wasn't, but what you did find was an error as the program was pulling through all the third party modules. Not sure what is causing the issue because it is coded correctly, just not doing what it should be doing.

I've rectified the link above for now though, there are more modules than originlly posted.
 

Colif

Win 10 Master
Moderator
So the ryzen drivers were just a mirage? glad you fixed it before op had to wonder why AMD drivers were showing on their system :)

damn, I thought i had it with those too

odd last time it was saying 5 of 5 dumps... seems adding more pages is confusing the script?

these could be a problem due to age and fact lots of wireless cards are becoming problems
netr28x.sysMediatekRalink RT2860 series Wireless LAN Card29/05/2015In 1 of 1 dumps

really, anything older than June 2015 could be problem and you have a few of those
iusb3hcs.sysIntelIntel USB 3 Host Control Switch Driver05/12/2011In 1 of 1 dumps
PxHlpa64.sysSonic SolutionsPx Enginer Device Driver24/04/2012In 1 of 1 dumps
GEARAspiWDM.sysGear SoftwareCD-ROM Class Filter Driver (iTunes also)03/05/2012In 1 of 1 dumps
HECIx64.sysIntelIntel Management Engine Interface driver02/07/2012In 1 of 1 dumps
rikvm_38F51D56.sysCyberlinkCyberLink file?05/07/2012In 1 of 1 dumps
hpdskflt.sysHPHP Mobile Data Protection System Disk Filter24/09/2012In 1 of 1 dumps
Accelerometer.sysHPHP Mobile Data Protection System Accelerometer24/09/2012In 1 of 1 dumps
stwrt64.sysOEMSigmaTel High Definition Audio Codec16/08/2013In 1 of 1 dumps
netr28x.sysMediatekRalink RT2860 series Wireless LAN Card29/05/2015In 1 of 1 dumps
iwdbus.sysIntelWIDI Bus Enumerator Driver - Wireless Display08/06/2015In 1 of 1 dumps


You can't do much about USB, its sort of built into windows anyway. There won't be new drivers.
Cyberlink might be removable, not sure about the rest.

which wireless do you use? Railink or HP?
 

PC Tailor

Judicious
Ambassador
tried to update some windows updates as suggested and now i can not access the start menu. restarted several times and still persisting.
Did you test your storage drive also?
Based on what I saw with the collection, I'd say your updates are failing and there is some corruption in the OS.

You can run CHKDSK and SFC to sort this, but there will be something likely causing the corruption. Tie that in with the dump files previously, one could suspect your drive is faulting.
 
Reactions: beefboy2

beefboy2

Distinguished
Oct 6, 2013
34
1
18,535
0
Did you test your storage drive also?
Based on what I saw with the collection, I'd say your updates are failing and there is some corruption in the OS.

You can run CHKDSK and SFC to sort this, but there will be something likely causing the corruption. Tie that in with the dump files previously, one could suspect your drive is faulting.
Yes I believe this along with the updates did the trick for now. Been using the computer a bit everyday and have not run into a BSOD since the disk was fixed and the updates finished! Thanks so much everyone who jumped on this to help me!
 

ASK THE COMMUNITY

TRENDING THREADS