Getting bsod about every 5 mins and have to reboot to use for about 5 more mins. Pretty sure that it is MB related and hoping your tool will help diag the problem. The bsod happens with both my win 10 OSs after about the same time frame.
For some reason you are not creating any crash dumps that we can analyse. There are no Windows error reports either.
Two things to try:
1. Make sure you are properly set up for BSOD crash dumps. See tutorial here
2. Run the system for a few more BSOD events and then try using the Beta log collector provided at the end of the BSOD Posting Instructions.
Added later: There is also a tutorial to check that Windows Error reporting is turned on
Last edited by philc43; 24 Oct 2018 at 04:00. Reason: additional info
Actually it's a GSOD and not bsod. but problem is stated "storport.sys". I have now logged in on my win 7 with same pc so guess its not the MB. Doesn't make sense that both win 10 OSs would suddenly become corrupt when the 10 pro has not been used since it was updated back 3 months ago. Also restoring has no effect on the error; still crashes with gsod. Ran DISM repair on the os and it said all fixed but then crashed again, cannot run completed SFC before crashes. Also very slow to boot, couple mins compared to 35 secs 2 days ago.
Last edited by csmdew; 24 Oct 2018 at 10:42.
In that case if you are getting a GSOD you must be on an insider build and that is going to complicate the situation. You can expect all sorts of problems on an insider build since there will be new drivers being tested that could have unexpected consequences on your system.
I'm not on inside builds, got the normal OS pro 1803 version with last update before the 1809 started to come out. Never got it. Tell the truth I don't remember if it's the green or blu but just looking at the error stated it shows green on internet. But I am using win 7 now so I will need to put 10 drive back in to see what color the error is, sorry. Will change drives as soon as I finish my morning banking let you know the color. Also I have gotten dump files in the past so I don't know how it could have turned itself off. Will post more soon.
Now win 7 has started crashing so back to thought that it is mb.
Last edited by csmdew; 24 Oct 2018 at 12:17.
Went back to win 10 and discovered in event viewer I was having hd problems so I check inside case and found sata cable loose to one drive which I think caused the crashes. After some case maintenance and restoring drive everything seems to be fine now. Been up for about 4 hrs now and ran 3 SFCs with no integrity problems. Guess you can mark as solved, thanks.
Oh and they were BSODs
Great news! Thanks for letting us know. You can mark it solved yourself, we can't do that.
Quote