Windows 10: Have had 2 BSOD's today relating to memory how do I fix them?

Today I have had 2 BSOD's one with error irql_not_less_or_equal and the other was page_fault_in_non_paged_area.Link to Minidump files : https://www.dropbox.com/scl/fi/g5bv9128tn6pu7htlexge/Minidump.zip?rlkey=op2vxrqwhtsgb44pwojyt2tsz&dl=0

:)

 

Windows BSOD Memory Crash

Hi,

I'm Mohammed Shuaib, an Independent advisor here to help resolve the issue your facing and I suggest you apply all the below troubleshooting steps to fix the BSOD errors.

Fix #1

Step 1:

Go to search box next to Windows icon

Step 2:

Search for Command Prompt, right-click, and select the Run as administrator option.

Step 3:

Type msdt.exe -id DeviceDiagnostic & press Enter

Fix #2:

Step 1:

Go to search box next to Windows icon and type Troubleshoot

Step 2:

Click on Troubleshoot

Step 3:

Then under Find and Fix other problems select Program Compatibility Troubleshooter

Step 4:

Click on Run the Troubleshooter

Step 5:

Select the Game after which you saw the bluescreen & click Next

Fix # 3

Step 1:

Go to Search box next windows icon

Step 2:

Search for Command Prompt, right-click, and select the Run as administrator option.

Step 3:

Type the following command and press Enter:

SFC /scannow

Fix#4: Check drivers

Make sure there are no errors or yellow exclamations marks in device manager

To do so, follow these steps:

Go to search box next to Windows icon

Type Device Manager in the search box

Determine if there are any corrupt drivers installed (any errors reported) from the list of drivers installed. If there are no errors reported in Device Manager, update the software of your most recently installed driver. To do so, expand & right-click on the
list of devices shown under and click Update Driver.

Fix #5: Run chkdsk

To run chkdsk, follow these steps:

Press the Windows and C keys to open Charm Bar

Type cmd in the search box

Right-click on Command Prompt from the results list

Click Run as Administrator

Once Command Prompt has loaded, type:

chkdsk C: /f

Replace C: with the letter of the drive where your Windows is installed.

Fix #6:

To run the Windows Memory Diagnostic, follow these steps:

Press the Windows and C keys to open the search box from Charm Bar

Type Windows Memory Diagnostic in the search box

Click on Windows Memory Diagnostic from the search results list

Continue with the Windows Memory Diagnostic wizard to complete the process and wait for the results

Fix #7: Disable overclocking from BIOS

In order to fix the BSOD errors on Windows 10 systems, make sure the Overclocking feature from your computer’s BIOS is disabled.

To do so, follow these methods to open BIOS.

Method #1: Complete shutdown

Switch to login screen

Hold the Shift key while also pressing the Shutdown button

Select Restart

After your computer restarted, it should open into the BIOS menu automatically:

Go to Advanced tab

Go to Performance

Look for a Overclocking option

Make sure it’s disabled

If it’s enabled, disable it

Save the settings and exit BIOS by hitting the F10 key. Choose Yes if you’re asked to exit with saving the changes

Regards

Shuaib

Independent Advisor

 

Windows BSOD Memory Crash

Thanks for the super fast reply Shuaib,

I have completed all of these steps to no avail. (EXCEPT FOR FIX #5). Because I had a 512gb Sabrent SSD and not a HDD.

"Fix #5: Run chkdsk

To run chkdsk, follow these steps:

Press the Windows and C keys to open Charm Bar

Type cmd in the search box

Right-click on Command Prompt from the results list

Click Run as Administrator

Once Command Prompt has loaded, type:

chkdsk C: /f

Replace C: with the letter of the drive where your Windows is installed."

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.