RAM Troubleshooting - BSOD Error

propsmc90

Honorable
Oct 25, 2012
39
0
10,530
Hey everyone,

On Monday (May 1st 2017) I accepted the Windows 10 mandatory update. Prior to this update everything was running fine, and I did not get any BSODs.

After it went through the update that's when the problems started. I would get the error message:
ATTEMPTED EXECUTE OF NO-EXECUTE MEMORY and it would restart, sometimes I could get into the Windows and sometimes I couldn't because of the constant BSODs.

How I replicated the error: Often times how it would cause a BSODs is when I type something into Cortana or click the Windows button on the task bar and or touch the Windows key on my keyboard and that's when it'll freeze and give me the error. If I don't touch any of that, my system runs fine.

The tests I've run:
- "sfc /scannow" - no errors
- memtest86 (free edition) ran for 8 hours 5/10 passes (I got impatient so I cancelled the test) but there were no errors when I let it run overnight, I also ran all the Test Settings: 0-13 (I enabled everything). I am definitely no expert and this was my first time running memtest, but I personally think what I set to was overkill.
- Premium Trial MalwareBytes: only threat that came up and a known threat was a crack file, that was safe and used before with no problems
- Windows Defender: No errors
- Windows Memory Diagnostics Tool: I'm pretty there was no errors.
- Samsung Magician, Piriform Defraggler, Date Lifeguard for Windows (Western Digital): all have said HDD/SDD are in good condition
- CCleaner: Cleaned the registry
- Defragment/Optimize Drives: De-fragged and optimized all my drives

I also reset my computer a few times, I selected the option "Keep my files" but wipe everything. That didn't seem to fix anything eventually the problem came back again.

I eventually gave up and decided to do a clean reinstall - I formatted all the drives, deleted any partitions I could delete, and I re-installed my Windows 10 64 bit to Home Edition instead of Pro and so far it's okay...

Conclusion:

My gut is telling me this is not a RAM/HD problem.

I've had this computer since July or August of last year. I also took it to shop to get it fixed because I didn't build it correctly so they did all the stress testing for me. So none of my parts are "new" anymore and they have been tested.

I decided to bring this up to TomsHardware and hopes someone who has a more in-depth knowledge regarding computers can tell me if I missed something or maybe it was just a Windows Update issue that was corrupted or screwed something up with other programs in my computer. I do not know. Thank you for reading!

My computer specs:

- i7-6700 3.4Ghz Quad Core Processor
- Corsair - H100i v2 70.7 CFM Liqiud CPU Cooler
- Arctic Silver- 5 High-Density Polysynthetic Silver 3.5g Thermal Paste
- Asus Z170I Pro Gaming Mini ITX LGA1151
- G.Skill Ripjaws V Series 32GB (2x16GB) DDR4-2133 Memory
- Sandisk X110 128GB 2.5 SSD
- Samsung 850 EVO Series 250GB 2.5 SSD
- Western Digital Caviar Blue 1 TB 3.5 7200 RPM (I have two)
- MSI Geforce GTX 970 4GB Twin Frozr V
- SeaSonic - S12II 620W 80+ Bronze ATX Power Supply
- Windows 10 Pro OEM 64 Bit


 
Solution
It might just be a driver

Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)
I can't read them but there are a few around who can

Colif

Win 11 Master
Moderator
It might just be a driver

Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c/windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)
I can't read them but there are a few around who can
 
Solution