hello
a number of weeks ago (sometime in november) my system started experiencing frequent blue screen errors, particularly when doing memory intensive things like rendering in blender or other 3d apps. nothing about my computer was changed immediately prior to this (no hardware/software updates) so i was stumped. the last changes i made to my computer were a new motherboard/cpu/extra RAM i added over the summer (around july) but i understand that that doesnt necessarily mean theyre not at fault.
i tried a number of things, most of the standard troubleshooting instructions (disk repair, sfc scannow, updating drivers, removing drivers and reinstalling, making sure no overclocking is enabled, updating BIOS, etc) and nothing seemed to be working. i tried using driver verifier and each time it would crash with a different driver as the culprit -- i started removing them one by one but eventually got so frustrated i just decided to completely reinstall windows. this lessened the number of blue screens i get, but i still get them every 2 days or so, especially if i leave my computer running overnight. sometimes they will happen while i am playing a game, but this is rare.
the problem im having is that every time i get a blue screen, the stop code is different. sometimes its SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, sometimes its KMODE_EXCEPTION_NOT_HANDLED, sometimes its WHEA_UNCORRECTABLE_ERROR, sometimes its something else, and the module thats "at fault" is usually different too (sometimes its ntfs.sys, sometimes ntkrnlmp.sys, sometimes svchost.exe, etc) though ntkrnlmp.sys seems to be the culprint about 50% of the time. i cannot figure out what the heck the problem is! its driving me nuts. i am not that great at reading these dumps, though, so maybe ive missed something.
ive been trying to test my memory and while ive been able to successfully run passmark's memtest86 gui for 8+ loops with no errors, i have not been able to create a memtest bootable USB because each time i try the USB is either not recognized by the computer or the program is unable to create the bootable usb (ive tried 4 different usb sticks, maybe i just need to buy a new one, i dont know).
i have 0 overclocking enabled so i am assuming that one of my memory sticks is bad but i find it difficult to verify because i cant force it to crash. i cant even get it to crash by using blender anymore; it happens completely at random, and leaving the computer on for 2+ days at a time so i can test 1 stick of memory seems excessive.
ive attached the most recent minidumps below; if anyone has any insight i would REALLY appreciate it.
https://drive.google.com/drive/folders/1koVkEkDIHxwGA6egJxxjrF0apJHV71IH?usp=sharing
a number of weeks ago (sometime in november) my system started experiencing frequent blue screen errors, particularly when doing memory intensive things like rendering in blender or other 3d apps. nothing about my computer was changed immediately prior to this (no hardware/software updates) so i was stumped. the last changes i made to my computer were a new motherboard/cpu/extra RAM i added over the summer (around july) but i understand that that doesnt necessarily mean theyre not at fault.
i tried a number of things, most of the standard troubleshooting instructions (disk repair, sfc scannow, updating drivers, removing drivers and reinstalling, making sure no overclocking is enabled, updating BIOS, etc) and nothing seemed to be working. i tried using driver verifier and each time it would crash with a different driver as the culprit -- i started removing them one by one but eventually got so frustrated i just decided to completely reinstall windows. this lessened the number of blue screens i get, but i still get them every 2 days or so, especially if i leave my computer running overnight. sometimes they will happen while i am playing a game, but this is rare.
the problem im having is that every time i get a blue screen, the stop code is different. sometimes its SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, sometimes its KMODE_EXCEPTION_NOT_HANDLED, sometimes its WHEA_UNCORRECTABLE_ERROR, sometimes its something else, and the module thats "at fault" is usually different too (sometimes its ntfs.sys, sometimes ntkrnlmp.sys, sometimes svchost.exe, etc) though ntkrnlmp.sys seems to be the culprint about 50% of the time. i cannot figure out what the heck the problem is! its driving me nuts. i am not that great at reading these dumps, though, so maybe ive missed something.
ive been trying to test my memory and while ive been able to successfully run passmark's memtest86 gui for 8+ loops with no errors, i have not been able to create a memtest bootable USB because each time i try the USB is either not recognized by the computer or the program is unable to create the bootable usb (ive tried 4 different usb sticks, maybe i just need to buy a new one, i dont know).
i have 0 overclocking enabled so i am assuming that one of my memory sticks is bad but i find it difficult to verify because i cant force it to crash. i cant even get it to crash by using blender anymore; it happens completely at random, and leaving the computer on for 2+ days at a time so i can test 1 stick of memory seems excessive.
ive attached the most recent minidumps below; if anyone has any insight i would REALLY appreciate it.
https://drive.google.com/drive/folders/1koVkEkDIHxwGA6egJxxjrF0apJHV71IH?usp=sharing
took them out and replaced them with the EVGA sticks and haven't had a blue screen since. thanks all for your help!
Facebook
Twitter
Instagram