Windows 10: BSOD ongoing since update 1609

hey guys,

this issue has been going on for weeks now and has been getting worse and worse no matter what i do.

The long story is around the time the windows 1607 update came out i downloaded it and let it install over night. i came back from work the next day to dins my pc would not power on... after a few days of troubleshooting I eventually found my power supply had somehow failed. Once i bought a new power supply and a new cpu cooler (H80i) i booted up windows to find the update and failed multiple times before my pc must have failed. all was going well i even overclocked my cpu with the new cooler and got a nice stable clock with great temps and voltages (or so i thought). i started to get BSOD so i ended up taking my CPU back to stock settings. This seemed to help at first but eventually the bluescreens returned and more frequent. NOTE!! it never bluescreens when just in idle or browsing web watching videos etc ONLY when playing games or stress testing. most common though is gaming get about 15-30mins in and usually fails. where as alot of the time can get through a IBT and prime95 fine although it has failed a few times.

i have run memtest and got 10 good passes, i have run disk check and passed, done sfc/scannow, completely reinstalled windows and BSOD persist.

i have attached a few of the mini dumps any help would be great! i currently suspect it is hardware that was possible damaged when the power supply went but who would know, graphics card i wouldn't suspect, im guessing cpu/ram or MOBO. Attachment 98073

:)

 

Windows 10 Creator update stalls at 33% after download configuration.

Windows 10 home (Lenovo Idea Centre purchased November 2014 running WIndows 8) updated to WIndows 10 1609, problems ever since. Currently working with Microsoft Level 2 Support to resolve, but so far no luck.

 

windows 10 1703

Where did you get the 1609 update?

 

The error appears to be related to the Numeric Processor Extension (NPX)

Code: UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000000000009, EXCEPTION_NPX_OVERRUN Arg2: 0000000080050033 Arg3: 00000000000406f8 Arg4: 00007ff711b653d4[/quote] This looks like it could be a hardware problem but I don't know enough about this error to be sure. There is a useful procedure you can run to check that all your drivers are working OK called Driver Verifier. You could run this for a while to see if it throws up any driver errors. The details for doing it are given system restore point so that you can get back to a working system if you run into any problems.

 

thanks will check it out now and see how it goes

 

This looks like it could be a hardware problem but I don't know enough about this error to be sure. There is a useful procedure you can run to check that all your drivers are working OK called Driver Verifier. You could run this for a while to see if it throws up any driver errors. The details for doing it are given system restore point so that you can get back to a working system if you run into any problems.[/quote] will leave it on over night to see how it goes, so far there has been no crashes. just played some games for a few hours and didnt get a crash either which is strange. just confuses me more TBH the crashes seem so random but i doubt they will stay away. might leave prime95 running aswell to see if that sets it off

 

alright had another bluescreen and attached minidump. this time it was when running prime95 for about 15mins not related to driver verifier. starting to suspect my cpu is damaged. the bluscreen viewer had an unknown_module error?

 

I can't extract anything from that file. Do you have another CPU (maybe an older one) you can swap in and test?

 

sadly no, worst part is my cpu is literally not available in my country anymore, so may have to get a new motherboard and RAM aswell*Sad
i may buy some new parts and see how it goes. if that doesn't work literally everything would have change since graphics card( which i'm fairly positive is fine)

is it possible for a motherboard to be damaged and only crash when under high loads from cpu etc? motherboard may have been damaged when powersupply went.

 

ended up getting a new cpu and motherboard, asus z170 AR and i5 6600k and now everything is working fine. may never know which one it was but im guessing it was the cpu. will mark as solved thanks for the help*Smile