Windows 10: Random BSOD's every 45 min or so, usually while playing games

Please post a screenshot/photo of taskmanager, filtered on disk usage, when the system is getting slow.

Does it happen too when you only have 1 program open?

 

Hey all, well looks like the internet slowing down was a temporary thing, seems to be fine now. I can still post screenshots if you'd like however. Anything else I should do in regards to the BSOD's?

 

It is appreciated to run the DM Log Collector, upload the new zip and give a description of what happened.

 

Hiya axe0, well I crashed a couple times a few days ago and I didn't get any responses on what happened for those three crashes. Here's a DM log I ran just now, the crashes haven't happened for maybe ~2 days sort of now. I haven't been on my computer much during this but it has been on without crashing for extended periods of time.

 

Another crash occured, this time I had a couple tabs open. Just started a video and it froze then crashed like usual. Before this crash though, Cortana and microsoft explorer stopped working, it said critical error and asked me to sign out. So I did that, when I was working microsoft word stopped responing. I restarted that and everything was fine up until the crash. Don't know if any of these are related but it feels like my computer is falling apart *Sad.

 

This is important.
To make it more understandable, below are a few logs talking about corruption in the file system structure.
This causes boot problems which could either make the hard drive unbootable and thus your system will say no boot device is connected or you get a BSOD because the file system structure has been damaged.
Code: Event[10799]: Log Name: System Source: Ntfs Date: 2015-11-08T17:08:18.914 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Ash-PC Description: A corruption was discovered in the file system structure on volume C:. The exact nature of the corruption is unknown. The file system structures need to be scanned online. Event[10802]: Log Name: System Source: Ntfs Date: 2015-11-08T17:08:19.753 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Ash-PC Description: A corruption was discovered in the file system structure on volume C:. The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x100000003568a. The name of the file is "\Windows\servicing\Packages\Microsoft-Windows-Multimedia-RestrictedCodecs-WOW64-Package~31bf3856ad364e35~amd64~~10.0.10240.16384.cat".[/quote] I would like to see a screenshot of the disk management and of the disk management from an admin command prompt
For the admin command prompt, enter following commands
Code: diskpart list disk sel disk {0} {0} is the disk number that contains the system, if your disk containing the system files is 0, enter "0" (without quotes) instead of {0} list partition[/quote]

 

Heya axe0, looks like you were spot on about the C drive corruption. I got home today and decided to do what you asked, while I was reading this post however I got a message from windows saying C drive has corruptions and I should restart so Windows can repair it. Oh sweet I thought, this'll be easy. When Windows restarted, it got to the windows 10 loading page and started the process of repairing C drive. Here's the problem though, as soon as it starts to say "Repairing C Drive, some%" the computer would BSOD with a critical service or process failure error code (not sure of the exact one). Now the computer would then restart like with all BSOD's but this time into a "failed to boot" service. Windows trying to figure out why the computer couldn't boot and all that. So it said I should restart to fix it. When I do that the computer goes back to trying to repair the C drive. However, it BSOD's yet again. Then I restart into "failed to start", restart again and go into C drive repair and subsequently BSOD. The cycle continues like so. I decided to use that linux USB and changed the drive to boot from in my UEFI. Not sure where to go from here... any ideas? I'd heard about the BSOD loop of death, never thought it would've happened to me :/

 

Do you have recovery media?

 

Aside from my Windows 8 disc I'm afraid not *Sad My C: disk only had program files, most of my data is on my HDD. What should I do from here?

 

Do you have (temporary) access to another Windows 10 pc?

 

No Windows 10 PC's but I have access to a windows 7 and 8 PC.

 

I am not sure that if you create a recovery media from Windows 8/7 installation the recovery media will work for Windows 10. I have never tried it at least.

Recovery Drive - Create in Windows 10 - Windows 10 Forums

 

Hmm, been meaning to update my brother's laptop to windows 10. Maybe I'll try later tonight and get the recovery media off of that. Just to clarify, does this mean the SSD has failed and I need a new one or files just spontaneously corrupted?

 

which should contain many of the recovery options.Have you tried to boot into Media Creation Tool. If you fail to boot three times in a row, it should automatically boot into many of the recovery options.

I don't know about the SSD. If it is able to be seen in BIOS, it hasn't completely failed.

 

Heya Essen, yah I can see it in the BIOS. So my brother's laptop has to stay windows 8 so I can't get a recovery drive. Is there a way to make a recovery drive without another computer?