Windows 10: BSOD, SYSTEM_SERVICE_EXCEPTION and ATTEMPTED_EXICUTE_OF_NONEXICUTE_MEM

See these links:

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

 

I'm going to call it a semi success.

I left the battery out all day, popped it back in and booted up the computer.

good news it goes past POST, shows the splash screen briefly and then jumped to a screen with the spinning dots and said preparing automatic repair but that's where it froze up.

whats next?

 

1) see if you can launch the memtest86+
if you can please run 8 or more passes.
This will rule in or rule out problems with RAM / DIMM /Motherboard
Use a camera or smart phone camera to take a picture and post an image of the results into the thread.
2) see if you can launch the bootable windows 10 iso
if you can then plan on using the windows advanced troubleshooting menu

For dell computers the F12 key should enable you to choose a boot device:


List of PC brands with their corresponding hot-keys

 

Okay memtest is running, it's in its first run right now and has found 12 errors :/ what does that mean?

 

It means that there is malfunctioning RAM.
So you can abort testing now.
Remove all RAM modules except 1.
Test each RAM module in the same DIMM for 8 or more passes.
Use a camera or smart phone camera to post an image of the failure you just saw.
And post an image into the thread for each RAM module tested for 8 or more passes.

Just 1 error is a fail and you can abort testing.
You will test all RAM modules 1 at a time in the same DIMM.
This should differentiate good from bad RAM.
If all RAM pass when tested individually then move 1 RAM module to the next DIMM and test for 8 or more passes.
This will then differentiate RAM problems from DIMM /MB problems.

 

Okay so just pop out a stick of ram and start it again?

 

In the image I could not see Memtest86+ version 5.01. Usually it displays with a blue window.
Please confirm that you are using: Memtest86+ - Advanced Memory Diagnostic Tool

 

Uh the top of it says memtest86 version 7.4 free

 

The goal is to find out which stick of RAM is bad, so testing 1 at a time (keep testing even if you find errors with the first one) will allow us to find out which stick(s) is/are bad.

There is also the possibility that your motherboard's RAM slot is bad, so if all of your DIMMs test bad, try them again in another slot.

 

Each software product is different.
Please use Memtest86+ version 5.01 for testing the RAM /DIMM / Motherboard
Memtest86+ - Advanced Memory Diagnostic Tool

 

Okay I downloaded it, burnt it and popped it in but the computer doesn't seem to recognize it

 

Boot from USB Drive on Windows 10 PC Windows 10 Installation Upgrade Tutorials: Boot from USB Drive on Windows 10 PC Windows 10 Installation Upgrade Tutorials


Note
If you have fast boot or ultra fast boot enabled in your UEFI firmware settings, then you will need to temporarily disable fast boot or ultra fast boot to be able to boot from a USB.


How to Enable Fast Boot or Ultra Fast Boot in UEFI Firmware Settings for Windows: Enable or Disable Fast Boot in UEFI Firmware Settings for Windows Windows 10 Performance Maintenance Tutorials


1. Try another USB stick
2. Try all USB ports (2.0 and 3.0)
3. Maybe when using UEFI Bios u have temporarly switch to Legacy in BIOS settings
4. Turn off temporarily fast boot, secure boot, CSM if enabled

 

Alright little update, I'm nearly done testing ram stick 2 of 4 and so far no errors reported by the proper version of memtest86+

 

What were the steps that you made to use Memtest86+?

Please use a camera or smart phone camera to take pictures and post images of the results into the thread.

 

I downloaded the version that came with the usb installer, I pulled all the ram sticks except one, popped the use in and booted the computer up.

Memtest86+ launched on its own and started working.

Ive let it run 8 passes on each stick, I'm on the last stick right now and so far no errors have been found