Windows 10: Several different BSOD errors

I'm attaching the BSOD from May 2, and a bunch of new ones too. Everything from Chrome to Overwatch has caused a BSOD. I will try the memory test again and post a picture.

I am also getting Red SOD's. How concerned should I be about that?

 

Greenburrito, when you run memtest86+, please follow these instructions.

Please Run Memtest86+





Information Please download from this site only Memtest86+ - Advanced Memory Diagnostic Tool in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask

Please also check fo firmware updates for your SSD. I think you can find them here, Z400s SSD Firmware Upgrade

Thease are the last several dump files. A code 7E is in many cases a hard drive problem, but we also keep coming up with the same memory error.

Code: Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff801da1ad7be, ffffd0004e797408, ffffd0004e796c20} Probably caused by : NTFS.sys ( NTFS!NtfsDeleteFcb+7e ) Followup: MachineOwner[/quote] Code: MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of the PTE. Parameters 3/4 contain the low/high parts of the PTE. Arg2: fffff68000291b18 Arg3: 0000000100000000 Arg4: 0000000000000000[/quote] Code: Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff8032779073d, ffffd0008d76b098, ffffd0008d76a8b0} *** WARNING: Unable to verify checksum for win32k.sys Probably caused by : memory_corruption ( nt!MiDemoteCombinedPte+39 ) Followup: MachineOwner[/quote] Code: Use !analyze -v to get detailed debugging information. BugCheck A, {ffffe0046261cf98, 2, 0, fffff801ee4c1426} Probably caused by : memory_corruption ( nt!MiOffsetToProtos+156 ) Followup: MachineOwner[/quote] Also, the Red Screen is usually a graphics card problem.

 

Here is the SSD screenshot, I have already upgraded my firmware and it did not help.

 

Here is the memtest screenshot - 14 passes and no errors.

 

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask

Please also check fo firmware updates for your SSD. I think you can find them here, Z400s SSD Firmware Upgrade

Thease are the last several dump files. A code 7E is in many cases a hard drive problem, but we also keep coming up with the same memory error.

Code: Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff801da1ad7be, ffffd0004e797408, ffffd0004e796c20} Probably caused by : NTFS.sys ( NTFS!NtfsDeleteFcb+7e ) Followup: MachineOwner[/quote] Code: MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of the PTE. Parameters 3/4 contain the low/high parts of the PTE. Arg2: fffff68000291b18 Arg3: 0000000100000000 Arg4: 0000000000000000[/quote] Code: Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff8032779073d, ffffd0008d76b098, ffffd0008d76a8b0} *** WARNING: Unable to verify checksum for win32k.sys Probably caused by : memory_corruption ( nt!MiDemoteCombinedPte+39 ) Followup: MachineOwner[/quote] Code: Use !analyze -v to get detailed debugging information. BugCheck A, {ffffe0046261cf98, 2, 0, fffff801ee4c1426} Probably caused by : memory_corruption ( nt!MiOffsetToProtos+156 ) Followup: MachineOwner[/quote] Also, the Red Screen is usually a graphics card problem. Is there anything I should do next?

 

Greenburrito, I apologize. I must have overlooked the notification. If I do not respond to your post within 24 hours, send me a Visitors message or a Private message. Sorry again. I would like you to try reinstalling your graphics drivers again. Please manually download the newest driver from AMD ( Download Drivers
) and save it to your desktop. Uninstall your current driver and run the setup program. If given the opportunity, select uninstall first. When you reboot, run it again and select the custom install option. Install only the Display Driver and nothing else. See if that helps any. Once you have had a chance to try it out, let me know if things have improved any.

 

When I tried to uninstall the drivers, I received an error stating it was not properly uninstalled - I rebooted and tried to uninstall but it said there were no drivers on the system. I tried to reinstall the drivers and it gave me an error stating it could not complete. I tried to repair my Windows 10 but that ALSO gave me an error, so I ended up formatting the drive and reinstalling Windows 10. I installed the drivers from scratch and no improvements from what I can tell. I played Overwatch for ~ 20 minutes before I received a Red Screen of Death.

 

Fair enough, I understand this has been a large process of elimination test. I'm going to just bring it into a computer repair shop; my friends either don't have a spare card or are unwilling to let me use their main card for the swap. *Sad

Thank you, essenbe and Arc for your help. I will post the solution/problem for others once they've figured it out.

 

Can you borrow a spare card? I hate for you to spend money for something we could rule in or out fairly easily. If you decide to take it to a computer Shop, I hope you will let us know the results.

 

As I said no one will let me borrow their card, so I'm kinda stuck with going to a shop. I will post here to let you know.

 

Wow, so they ran diagnostics on it and said that it was fine. They also realized my CPU fan was not set properly, so they cleaned it and re-added thermal paste, and set the CPU fan properly. For some reason it's even worse now. I am attaching the dump files just from this past 40 minutes. Overwatch now won't even play, it freezes before I can do anything, and now I'm getting 2 errors, VIDEO_TDR_FAILURE, and THREAD_STUCK_IN_DEVICE_DRIVER.

 

So I took it back to the repair guy, and after doing more testing, he said that the graphics card was overheating, and it was not able to rest properly because the heat sink on the MOBO blocks it from "clicking" into place. I'm going to get it refunded/replaced by XFX under warranty.

However, I still got some weird BSODs tonight, sans graphics card. The errors without graphics card are from June 2 2016. What could possibly still be causing these BSODs?

 

Please upload the BSOD Posting instructions Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums.

I will take a look at the files. if you are still having BSODs after removing a supposed faulty graphics card, I would be suspect of what the computer shop told you. If you have removed the problem, you shouldn't still be having the same issues. That is only logic. Also, didn't we monitor the Graphics card temps before? Plus, another card will still have the same space issues, if that was in fact a problem.

 

The temps were around 79° in the store, granted the case was open and the store was extremely cool. When I ran it at my place, the card was at 83° after a minute, and were continuing to increase. I stopped it before damaging the card...didn't want it to get to 90 or higher. I think there is some validity to it running hot in my small case.

I did see him trying to put in the card, and it does not "click" like the test card he used, so it doesn't fit due to the heat sink so close by. It seems like most of the pins are in, but it can't lock so that may cause concern.


The BSODs from May 31 and June 1 are from the repair guy with the gfx card in. "pci.sys", "memory_corruption" "dxgkrnl.sys" for another,. The June 1 at 21:00 is me, and it says "memory_corruption". It was a PAGE_FAULT_IN_NON PAGED AREA BSOD
The two June 2 BSODS are memory_corruption and "dxgmms2.sys" which I think is DirectX, PAGE FAULT IN NONPAGED AREA and SPECIAL POOL MEMORY CORRUPTION (while running driver verifier). I know the repair guy used a Nvidia 610 so maybe there are still drivers from the card on the computer??

It's weird, my RAM has passed the memtest about 3 times now but I keep getting the error. Could RAM be faulty but still pass that test? Can a SDD, CPU or MOBO cause a memory_corruption error? I'm really at a loss here.

 

Grenburrito, I am beginning to be at a loss as well. The answer to could any of those things cause it is yes, they all could. I am going to ask you to do a couple of things. We may have done them before, but lets try again.
Next please right click on the start icon and select Command prompt administrator, give admin permissions and copy/paste this into the window that opens and press enter sfc /scannow . If you decide to type it in, please notice the space between the sfc and the /. We want it to say no integrity violations were found. If it says there where corrupt files that could not be repaired, please reboot and run it again. You may have to run it 3 times with reboots in between each time.

If that works, could you get your computer guy to loan you some known good working ram and replace the ram you have installed with what he gives you. Hopefully, that may answer the question about ram. You could even run with just 1 stick just for a test.