Upgraded to windows 10 lots of blue screens are now happening

[Prayqt]

Last night I upgraded my PC to have windows 10, from 8.1. I completely deleted the 8.1 files so I can't reboot to 8.1 now. I have been having lots of Memory Management BSOD. However I have kept getting random ones including, bad pool header, faulty hardware corrupted page, Page fault non paged area.

I have tried uninstalled and reinstalled my graphics drivers, which upon research online was the highest cause of most of these. In my device manager all of my devices all said that they were working properly.

My last option I feel like would just be doing a clean install of windows and deleting all the files I have. Any help would be appreciated

My rig:
Mobo: GIGABYTE G1 Gaming GA-Z97X-Gaming 5 (rev. 1.0) LGA 1150 Intel Z97 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard
GPU: EVGA GeForce GTX 960 02G-P4-2962-KR 2GB SC GAMING,
CPU: Intel Core i5-4690K
PSU: EVGA SuperNOVA 650
Ram: Corsair 8gb ddr3
SSD: Samsung 850 evo 128gb
HDD: 1TB seagate

I doubt it is any of my hardware since when I was on 8.1 yesterday and everything was working fine, but there it is anyways.


In the event Viewer here is an bugcheck,

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 4

Level 1

Task 63

Opcode 0

Keywords 0x8000400000000002

- TimeCreated

[ SystemTime] 2016-11-15T05:22:23.518507500Z

EventRecordID 1436

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Dylan-PC

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 26
BugcheckParameter1 0x41792
BugcheckParameter2 0xffffdfbffca2b038
BugcheckParameter3 0x2a0000
BugcheckParameter4 0x0
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
Checkpoint 0
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 0
CsEntryScenarioInstanceId 0

 

[Colif]

When windows restarts, it runs a report. If that report finds PC was shut down incorrectly the previous time, it will create an event 41. So event 41 isn't the cause, its just windows reaction. The memory management errors likely point to cause.

can you download and run who crashed: http://www.resplendence.com/whocrashed
it will look at errors and create a summary

Copy/paste results in here

Bug Check 0x1A: MEMORY_MANAGEMENT
0x41792 - A corrupted PTE has been detected. Parameter 2 contains the address of the PTE. Parameters 3/4 contain the low/high parts of the PTE.

memory management can be drivers, it also can be ram... can you run the free version of this? http://www.memtest86.com/

 

[Prayqt]

crash dump file: C:\WINDOWS\Minidump\111516-4734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x1A (0x41793, 0xFFFF82800006FEB8, 0x2, 0x1)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe


crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41793, 0xFFFF82800006FEB8, 0x2, 0x1)
Error: MEMORY_MANAGEMENT

crash dump file: C:\WINDOWS\Minidump\111516-4390-01.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2+0x14DC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF804E0274DC0, 0xFFFFB4818ECAC2A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys

crash dump file: C:\WINDOWS\Minidump\111516-4093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x19 (0xD, 0xFFFFD203993C7BF0, 0xEFC0C0BC1D0F7261, 0xEFC0C0BC1D647261)
Error: BAD_POOL_HEADER

crash dump file: C:\WINDOWS\Minidump\111516-4578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x573, 0xF469BC0, 0xFFFF96014075A000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
file path: C:\WINDOWS\system32\ntoskrnl.exe


There are the 5 most recent crashes,
at the bottom this is what was posted in the conclusion "5 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. "

I was also looking around in the BIOS and both of my ram sticks were working fine.

 

[Prayqt]

crash dump file: C:\WINDOWS\Minidump\111516-4078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xEF (0xFFFF80035BCC4800, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
file path: C:\WINDOWS\system32\ntoskrnl.exe

crash dump file: C:\WINDOWS\Minidump\111516-5218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xD7 (0xFFFF870744D70C00, 0x1, 0x0, 0x0)
Error: DRIVER_UNMAPPING_INVALID_VIEW
file path: C:\WINDOWS\system32\ntoskrnl.exe

These both happened right after I updated my graphics driver to the most recent that was released today.


I also attempted to wipe my harddrive and SSD to reinstall windows, however when I attempted to refresh my PC it said that it couldn't do it any just undid the process.

 

[Colif]

run memtest on your ram sticks. FAULTY_HARDWARE_CORRUPTED_PAGE + MEMORY_MANAGEMENT are ram errors. You don't want any errors in memtest, anything higher than 0 is too many. It makes a bootable USB and runs without windows. No point trying to put win 10 on a PC that has problems.

I still haven't got latest nvidia drivers, i only upgrade if it helps.

once you fix the memory you may want to fresh install since the reset failed. There are ways to try to fix reset otherwise

On another PC, download the Windows 10 media creation tool and use it to make a win 10 installer on USB << handy to have anyway

 

[Prayqt]

i pretty much scrapped it and got the windows 10 on a USB, and tried to install it and got a 0x8007025D. Which according to a youtube video I watched meant that it was a corrupted file It failed at 27%. So I deleted it off the FD and did it again and it got to 80% before it failed with the same error code again. I'll try it again tomorrow and hope for the best, if not I plan on buying a windows 10 key from a store and hoping for the best.

Any other suggestions you would think would help?

 

[Colif]

do the ram tests. I found a solution to that error and it mentions swapping ram sticks: http://www.tenforums.com/installation-setup/13475-failed-during-clean-install-error-code-0x8007025d-2.html

 

[Prayqt]

I will try it tomorrow, thank you for your help I'll post again tomorrow with updatees

 

[Colif]

Win 10 uses ram differently to previous versions of windows, so its obvious why it stresses ram more than previous versions if you know why.

Two ways:

1. In every version of windows prior to 10, when you turned PC off it shutdown. But in 10, instead of shutting down, it uses hibernate and saves half the files it needs to load at startup into ram, and the other hald into hdd, so when you restart PC its already got half of what it needs already.
2. IN old versions of windows, when you closed a program it would dump all the data on your hard drive right away. When you close a program in win 10, it compresses all of the data it used to run that program into ram instead. The reasoning being that if you want to reopen it again, it will be much faster to load direct from ram than slow storage.

These 2 reason contribute to ram being tested a lot harsher by win 10 compared to anything before, and why I keep seeing people upgrade and suddenly get memory errors.

Have a good sleep

 

[Prayqt]

Well i can't really do the ram test since I don't have an OS. BUT I guess I'll just buy sone to plug and test.

 

[Colif]

all you need is a PC to make the USB on, it boots from the USB and doesn't need windows to run the tests.

I would be surprised if buying new ram doesn't fix it for you. All the signs point at ram being the problem. Then windows should install.

 

[Prayqt]

Sorry to not have posted in a while, I had given up and was set on buying new parts.

I went to my friend's house who had some spare ram and slapped it in and so far it seems to be working as intended. I was able to update my windows updates that were failing to install before.

I will post back here after a while if my blue screens stop, thanks for your help!

 

[Colif]

No need to apologise, I am helping you, I answer lots of questions and don't sit around wondering about people not answering

 

[Prayqt]

Colif is confirmed a god amongst men, I'll just assume that after 2 days of it not blue screeening. Thanks for all your help man <3