Windows 10: BSOD has happened a few times now

I was streaming a video and playing a game today when I got a BSOD IRQL_NOT_LESS_OR_EQUAL. This has happened a couple other times as well, mostly while doing the same types of things.

Thank you in advance for the assistance.

Attachment 74387

:)

 

I have random BSOD on my windows 10 machine. Here is the last DUMP file analysis. Please if anyone can advice?

It was an ongoing issue. Reinstalled few times but still BSOD is happening randomly.

 

So this has happened to me 3 times within a weeks time if anyone can help ill be forever grateful

We appreciate the information that you have provided. Since the issue occurred after your hardware changes, we recommend that you contact the manufacturer of your PC. This is for them to verify if your PC is compatible with the video card that you have
installed. You may refer to this article on how to contact the manufacturer of your computer:

Computer manufacturers' contact information.

Let us know if you need further help with any Windows issue.

 

Do three things.

► First of all, uninstall AVG. It is either the main source of the issue or adding up to it.
Code: ffffd000`2363e288 fffff800`05cc84e7Unable to load image \SystemRoot\system32\DRIVERS\avgidsdrivera.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for avgidsdrivera.sys *** ERROR: Module load completed but symbols could not be loaded for avgidsdrivera.sys avgidsdrivera+0x184e7[/quote] Code: ffffd000`2363e1d8 fffff800`06296919Unable to load image \SystemRoot\system32\DRIVERS\avgwfpa.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for avgwfpa.sys *** ERROR: Module load completed but symbols could not be loaded for avgwfpa.sys avgwfpa+0x6919[/quote]
► Next, The DeathAdder 3.5G driver is also reported to be failing.
Code: ffffd000`2e8d49b0 fffff801`119c8453Unable to load image \??\C:\Windows\system32\drivers\rzpnk.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for rzpnk.sys *** ERROR: Module load completed but symbols could not be loaded for rzpnk.sys rzpnk+0x8453[/quote] Uninstall the installed version. Get it from the manufacturer's site: Razer Synapse 2.0 (PC) - Cloud-based configurator and manager for Razer devices

► And, Test your RAM modules for possible errors.MemTest86+ - Test RAM Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Take a camera snap of the memtest86+ window before closing the program. Let us see it.
Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums

Let us know the results.

 

021316-21531-01.dmp-AnalysisModsAndVersion.txt
Code: Deferred srv*Symbol information 0: kd> !Analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: > Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of the PTE. Parameters 3/4 contain the low/high parts of the PTE. Arg2: fffff680d3580b80 Arg3: 0000000200000000 Arg4: 0000000000000000 Debugging Details: ------------------ DUMP_CLASS: 1[/quote] 022116-18546-01.dmp-AnalysisModsAndVersion.txt
Code: Deferred srv*Symbol information 1: kd> !Analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* FAULTY_HARDWARE_CORRUPTED_PAGE (12b) This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error. Arguments: > Arg1: ffffffffc00002c4, virtual address mapping the corrupted page Arg2: 00000000000007e4, physical page number Arg3: 000001eb0bbe75f0, zero Arg4: ffffd00024888000, zero Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 400[/quote] 022516-20921-01.dmp-AnalysisModsAndVersion.txt
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: > Arg1: 0000000000000000, Machine Check Exception Arg2: ffffe0019d403038, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 400[/quote]
030516-17359-01.dmp-AnalysisModsAndVersion.txt
Code: Deferred srv*Symbol information 5: kd> !Analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: > Arg1: 0000000000005003, The subtype of the bugcheck. Arg2: fffff58010804000 Arg3: 00000000000003cc Arg4: 0000003c50002614 Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 400[/quote] 030616-26718-01.dmp-AnalysisModsAndVersion.txt
Code: Deferred srv*Symbol information 1: kd> !Analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* FAULTY_HARDWARE_CORRUPTED_PAGE (12b) This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error. Arguments: > Arg1: ffffffffc00002c4, virtual address mapping the corrupted page Arg2: 0000000000000f6e, physical page number Arg3: 0000016d880a1f90, zero Arg4: ffffd00022563000, zero Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 400[/quote]
031316-18453-01.dmp-AnalysisModsAndVersion.txt
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: > Arg1: 0000000000000000, Machine Check Exception Arg2: ffffe000d247c8f8, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 400[/quote] 031716-17453-01.dmp-AnalysisModsAndVersion.txt
Code: Deferred srv*Symbol information 4: kd> !Analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* FAULTY_HARDWARE_CORRUPTED_PAGE (12b) This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error. Arguments: > Arg1: ffffffffc00002c4, virtual address mapping the corrupted page Arg2: 0000000000000612, physical page number Arg3: 000001e58c0cd160, zero Arg4: ffffd00036427000, zero Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 400[/quote]
032016-24656-01.dmp-AnalysisModsAndVersion.txt
Code: Deferred srv*Symbol information 3: kd> !Analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* FAULTY_HARDWARE_CORRUPTED_PAGE (12b) This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error. Arguments: > Arg1: ffffffffc00002c4, virtual address mapping the corrupted page Arg2: 000000000000082c, physical page number Arg3: 000001eca5851210, zero Arg4: ffffd00022406000, zero Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 400[/quote]
032616-15312-01.dmp-AnalysisModsAndVersion.txt
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: > Arg1: 0000000000000000, Machine Check Exception Arg2: ffffe001271d08f8, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 400[/quote]
032616-16640-01.dmp-AnalysisModsAndVersion.txt
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: > Arg1: 0000000000000000, Machine Check Exception Arg2: ffffe0012f521038, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 400[/quote]
032716-16593-01.dmp-AnalysisModsAndVersion.txt
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: > Arg1: 0000000000000000, Machine Check Exception Arg2: ffffe001657b58f8, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 400[/quote] 032716-23843-01.dmp-AnalysisModsAndVersion.txt
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: > Arg1: 0000000000000000, Machine Check Exception Arg2: ffffe001919d88f8, Address of the WHEA_ERROR_RECORD structure. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 400[/quote] 040216-20906-01.dmp-AnalysisModsAndVersion.txt
Code: Deferred srv*Symbol information 0: kd> !Analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: > Arg1: 0000000000041289, The subtype of the bugcheck. Arg2: 00000201afc8b000 Arg3: 00000000000000e3 Arg4: 000002012fc8b215 Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 400[/quote] 040916-22140-01.dmp-AnalysisModsAndVersion.txt
Code: Deferred srv*Symbol information 0: kd> !Analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_MODE_HEAP_CORRUPTION (13a) The kernel mode heap manager has detected corruption in a heap. Arguments: > Arg1: 0000000000000003, A corrupt entry header was detected. Arg2: fffff90140600000, Address of the heap that reported the corruption Arg3: fffff9014061bdb0, Address at which the corruption was detected Arg4: 0000000000000000 Debugging Details: ------------------ DUMP_CLASS: 1 DUMP_QUALIFIER: 400[/quote] So i ran some basic analysis against all your dump-files.
I did this by script so i haven't looked at the details (Arc already did that for you).
Many of the dumps are pointing at a possible hardware failure (probably memory).
As suggested by Arc, i would strongly recommend to use memtest86+ to see if there are issues with your memory-module.

 

I did as Arc suggested and got rid of AVG and reinstalled the other device driver, however, I'm having issues getting my PC to run memtest86+. I have it installed to a usb, but I can't seem to get my pc to boot from the usb. I've tried holding shift+restart, but the usb does not show up there for me to restart from the usb, and for some reason when I do a normal restart it doesn't show what Fkey to hit to go into BIOS.

 

well this can be because of two thinks:

1) your USB stick is not a bootable USB stick

I'll link you how to make a bootable USB stick : How To Make Bootable USB

The only condition is that you'll need to have an windows-iso laying around for the last part.
Maybe someone else here can teach you an easier way, this is the only way i know of doing is.

2) If after you have made your USB bootable, still can't boot from the stick, check in the BIOS if your stick is being detected and make sure that bootfromusb is not disabled.

 

I have looked at two of the WHEA_UNCORRECTABLE_ERROR (124) files.
022516-20921-01.dmp and 032716-16593-01.dmp

They both show the following error
Code: =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffe0019d4030b8 Section @ ffffe0019d403190 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : BUS error Operation : Generic Flags : 0x00 Level : 3 CPU Version : 0x0000000000600f20 Processor ID : 0x0000000000000000 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe0019d403148 Section @ ffffe0019d4032d0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4) Status : 0xfa000010000b0c0f[/quote] This point to Bank 4 (or Dimm Slot 4)
So i would start with that slot and module to test.
Might save you some time.

 

Actually it is usually being caused by the fast startup being enabled and sometimes also that the boot mode needs to be in legacy mode.
Fast Startup - Turn On or Off in Windows 10 - Windows 10 Forums

The core and bank are from the CPU, that line says what part of the CPU made the CPU reporting the problem.

 

For MSI motherboards, the "Boot Menu" key of the BIOS is F11.
Restart the computer with the Memtest86+ USB attached, Tap the F11 key during the POST screen, it will show the list of possible devices to boot from. Select the desired USB using the Up/Down arrow keys and hit enter. It will boot from the USB.

This video will give you a fair idea about using the Boot Menu Key.
[youtube]v9KbPpkno9U[/youtube]

Hope it helps.