[SOLVED] BSODs over the last week

[Plsgod99]

Over the last week I've had multiple BSODs. Most are DPC_WATCHDOG_VIOLATION but there's two others - one labeled MEMORY_MANAGEMENT and one IRQL_NOT_LESS_OR_EQUAL

In all the errors they point to ntoskrnl.exe

I just need some help figuring this out . . .

Here are the dmp files produced from the BSODs : https://drive.google.com/file/d/1PEmEr1Rc6oE4xc8V4BYjfEGofWvbwNWB/view?usp=sharing

 

[Colif]

NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause

I will ask a friend to convert dumps but he is asleep now so it won't be right away

 

[Plsgod99]

NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause

I will ask a friend to convert dumps but he is asleep now so it won't be right away

I ran the Windows Memory Diagnostic and it says “there’s a hardware error, contact the manufacturer”

The thing is the BSODs started happening on the 13th and my most recent windows update was on the 12th... I’m not sure if that’s just coincidence or if I’m having multiple issues at once considering I have multiple BSOD messages

 

[gardenman]

Remove any RAM overclocks. Then download memtest86 and recheck your RAM. https://www.overclockersclub.com/guides/memtest86_memory_guide/ If this confirms the RAM issue, then your RAM is bad and needs to be replaced.

I don't think these may be needed, but here are the dump file results: https://jsfiddle.net/h4xbwmay/show

Spoiler

File information:	111920-8156-01.dmp (Nov 19 2020 - 15:00:00)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	memory_corruption (Process: SearchApp.exe)
Uptime:	0 Day(s), 18 Hour(s), 30 Min(s), and 50 Sec(s)

File information:	111920-7187-01.dmp (Nov 19 2020 - 16:53:57)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Probably caused by:	memory_corruption (Process: WerFault.exe)
Uptime:	0 Day(s), 1 Hour(s), 53 Min(s), and 29 Sec(s)

File information:	111820-7531-01.dmp (Nov 18 2020 - 12:38:28)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Probably caused by:	memory_corruption (Process: chrome.exe)
Uptime:	1 Day(s), 17 Hour(s), 54 Min(s), and 10 Sec(s)

File information:	111820-7312-01.dmp (Nov 18 2020 - 20:28:41)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Probably caused by:	memory_corruption (Process: NortonSecurity.exe)
Uptime:	0 Day(s), 2 Hour(s), 20 Min(s), and 53 Sec(s)

File information:	111620-7296-01.dmp (Nov 16 2020 - 18:43:50)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Driver warnings:	*** WARNING: Unable to verify timestamp for SYMEFASI64.SYS
Probably caused by:	memory_corruption (Process: MemCompression)
Uptime:	1 Day(s), 8 Hour(s), 54 Min(s), and 10 Sec(s)

File information:	111320-11218-01.dmp (Nov 13 2020 - 15:14:30)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Probably caused by:	memory_corruption (Process: MBAMService.exe)
Uptime:	0 Day(s), 6 Hour(s), 00 Min(s), and 32 Sec(s)

Symantec caused one of the crashes.

 

[Plsgod99]

Thanks, I might try memtest86 and It'll probably show some errors. Is it normal for RAM to die eventually? The computer has run perfectly for years now.

Also, if memtest86 shows no errors what should I try next?

 

[gardenman]

Also, if memtest86 shows no errors what should I try next?

I have a feeling that memtest86 will confirm that you have at least 1 bad RAM module. Since you have 2 RAM modules, you really should test them one at a time. It's often the case that 1 is bad and the other is good. To test them one at a time, you have to remove the 2nd one and run memtest86 while only the first one is installed. Then you switch them out to test again for the 2nd one.

If it doesn't find bad RAM we'll look at other things.

 

[Colif]

If its not ram, Norton is mentioned in at least 2 of the crashes , victim in one and cause in another.

and updating the drivers for Wi-Fi adapter might help

Oct 18 2018

rtwlane01.sys

Realtek PCI-E Wireless LAN driver