Windows 10: BSOD at random times, mostly when playing. Various error codes

OK, I must have missed the posts. Sorry, I'll take a look at the dumps now. If you set it to small memory dumps, and configure it like the picture in the tutorial at Small Memory Dumps, and the location as %SystemRoot%\Minidump, it won't overwrite files. But, Go to C:/Windows and make sure there is a file there named Minidump. If there is not one there, create one. Just create a new folder and name it Minidump.

Attachment 29542

 

There were no new dump files. But there were several Windows Update Failures, Windows Desktop Manager and One Drive Errors. If you can't get the DOS Version to run, you can use the from the same link I gave earlier

 

Ok, so I ran the SeaTools DOS (I managed to do it) and it passed in the short test, but the long test failed at somewhere near 12%.

Here are the pics:
Attachment 29663

Attachment 29664

Should I verify the RAM too?

 

Good job on getting it to work for you. You could test the ram, just so you will know. If the hard drive is still under warranty, I would call Seagate. Copy all your information from the drive and wipe it clean. That may have been most, if not all of your problem.

 

Nice!

New BSOD happened, here is the dump file, I hope it is not the same as the others, if it is, please tell me then I will have to figure why.

Attachment 29694

Thanks!

Thought I think that it is the HD problem, should I run a memtest too? And why the BSOD mostly happens when I try to play games?

 

You still only have the same 2 dump files dated 08/02, so nothing new to look at. I looked at some errors and nothing new there. I am guessing it is the drive. and just a guess, but games are doing a lot of constant reads and writes to it. I would think you need to change the hard drive soon. As far as ram, you could run it just to be sure if you wanted to. But, right now we know your hard drive is bad.

 

Ok, let me add some things up.

Today the PC just froze, no BSOD, and glitched the sound while I was playing, then I was forced to reset it by powering it off.

Then, I got this screen:

Attachment 29866

Ok, when the computer started, it froze again, when I reseted it, the computer kept trying to initiate but entered in a loop of failures, like, it was powered on, then tried to initiate, powered off, repeat. So I turned it off by cable, when it initiated again, I got this message (this time, I disabled Driver Signature Enforcement, I read somewhere that it is bad):

Attachment 29863

So, should I be concerned about my power unit, motherboard, something else or is it just a HD thing? I am getting more worried than ever.

 

The first pic is in portuguese, but you can see the error code and the archive reported.

 

I replied, I guess I forgot to press post. But, I suspected the hard drive really, but can't prove it. But, with that error message about a power surge would make me concerned about the PSU. All good quality PSUs, such as yours, have surge protection. So, I would borrow a known good power supply from someone right away and test it out. A power surge is not something you want to take a chance with. A power surge can ruin a whole computer. But, I wouldn't buy another one or try to RMA that one unless I tested it first to make sure that is the problem.

 

Ok, NOW I have got a new dump file, could you please analyse it?

Attachment 29891

Thanks!

 

Code: Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc0000005, fffff8011a085f44, 0, ffffffffffffffff} Probably caused by : memory_corruption Followup: memory_corruption[/quote] I'll look some more

 

Ok, this is what else I found from the dump file

Code: ffffd001`229e4578 fffff801`1a993668Unable to load image e1d64x64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for e1d64x64.sys *** ERROR: Module load completed but symbols could not be loaded for e1d64x64.sys e1d64x64+0x23668[/quote] Which is your Intel(R) Gigabit Adapter NDIS 6.x driver

 

How do I find that information?

 

Is this it?

Attachment 29946

Hope to hear from you!

 

New BSOD! Other error, this time

Do you want me to exclude the other dumps?

Here it is:

Attachment 29950

I really hope it is ONLY the Hard Drive.