[SOLVED] BSODs every 10 seconds. Replaced almost every component.

Toggle sidebar Toggle sidebar
S

spiffling

Dec 1, 2019
22
1
15
Minidump files: https://1drv.ms/u/s!Alk3aVYQMM1-ik6Qgz0XieJqdigF?e=oaTcLa

Hardware:
  • OS: Windows 10 1909
  • CPU: i9900k
  • Mobo: Asus Maximus XI Hero (Wifi)
  • GPU: Aorus RTX 2080 TI
  • RAM: Corsair Vengance RGB PRO 32GB (4x8GB) DDR4 3200MHz 15-15-15-36
  • Storage: 2x Silicon Power 1TB NVMe PCIe Gen3 x4 M.2 TLC
  • PSU: Corsair RM850x
I unplugged every thing from the mobo except monitor and keyboard
I swapped to different monitor and keyboard
I swapped RAM twice
I unplugged the GPU
I swapped hard drives to SATA
I reinstalled Windows... a lot
I swapped to an identical motherboard

The only consistent hardware at this point is the CPU and the PSU

Whats Happening:
PC will be fine for a couple days and then crash and reset every 10 seconds. Sometimes it shows a BSOD but mostly it doesn't. It makes a dmp file maybe 10% of the time. It will even crash while restarting from a crash. It will crash while doing the "Repairing your PC." I'm nearly out of hardware to replace so that makes me think it's software/driver related. But when I changed hard drives and was reinstalling windows from a USB stick it crashed. So I removed the hard drives completely and it still crashed at this point from the USB installer. Is there driver activity going on there? That makes me feel like its hardware but I'm making guesses outside my expertise. It has crashed maybe 5 times in safe mode.

On the BSODs I have seen

  • DRIVER_IRQL_NOT_LESS_OR_EQUAL
  • IRQL_NOT_LESS_OR_EQUAL
  • ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
  • SYSTEM_SERVICE_EXCEPTION
  • PAGE_FAULT_IN_NONPAGED_AREA
  • KMODE_EXCEPTION_NOT_HANDLED
Caused by:
  • hal.dll
  • ntoskrnl.exe
  • intelppm.sys
  • storport.sys
  • ndis.sys
  • wfplwfs.sys
  • stornvme.sys
  • NETIO.SYS
  • cng.sys
  • fileinfo.sys
  • iorate.sys
  • Ntfs.sys
  • dxgmms2.sys
  • win32kfull.sys
  • watchdog.sys
  • icrate.sys
  • nvlddmkm.sys
I've tried:
  • scf /scannow (no integrity violations found)
  • chkdsk /f /r on both drives (no problems found)
  • Full virus scan
  • Windows Memory Diagnostic (No memory errors detected)
  • Fresh reinstall of Windows
  • Windows Updates are up to date
  • Updated BIOS
  • Intel Processor Diagnostic Tool (pass)
  • Replaced all hardware except CPU and PSU
  • Windows Driver Verifier (can't get back into windows, had to reinstall)
  • Can't do Memtest or Prime95 because it crashes. I've tried 3 different brand memory anyway.
 
Solution
Colif
Dcopymope said:
Since its not allowing you to criticize your memory using more reputable tools, then that might be your main culprit, it has something to hide.
Click to expand...

Op has used multiple ram sticks already, refer:
spiffling said:
Can't do Memtest or Prime95 because it crashes. I've tried 3 different brand memory anyway.
Click to expand...

CPU & ram tests both didn't work, and since memory controller is on the CPU, it could be the cause. Until a test actually concludes, we cannot be certain.

Dcopymope said:
How many anti virus programs do you have installed? Having too many can cause problems in of itself.
Click to expand...

No AV showing in driver list which makes me suspect they are using Defender

at OP, I would be tempted to get PC looked at by repair store as they should have spare parts that...
Sort by date Sort by votes
spiffling said:
I don't think I have tried 2 DIMMS. I have tried singles in every slot and also one Gskill from a known working machine and a single Hyperx as well. Should I go ahead and try 2?
Click to expand...

as @drivinfast247 if they don't work as single dimms, they won't work in a pair.

Are you using XMP to set the speed? If so try set the timings/voltage of the DIMMS manually. It may be the DIMMS chosen might not be compatible with the mobo.
 
Upvote 0 Downvote
The DIMMs came as a 4 x 8 kit. I just now did a CMOS clear. All the pins in the socket look good. I don't really know my way around BIOS. Everything is set to factory and is mostly showing "Auto" for everything.
  • BCLK Frequency : DRAM Frequency Ratio___________Auto (100:133 and 100:100 are options)
  • DRAM Odd Ratio Mode________________________________Enabled
  • DRAM Frequency______________________________________Auto (Can choose 3200MHz from a list)
  • DRAM Voltage_________________________________________1.200V Auto
  • DRAM VTT Voltage____________________________________Auto
  • DRAM Timing Controls are all set to Auto
  • Realtime Memory Timing______________________________Disabled
  • DRAM REF Voltage Control is all Auto
Here is a video of me just scrolling around in BIOS
 
Last edited:
Upvote 0 Downvote
You can configure the ram manually by changing the Dram Frequency, and the Dram timings, and mem voltage. On the dimms, there should be a little sticker with 4 or 5 timings. I've listed them below. Sometimes the CMD, command rate is not adjustable. So the first 4 are the ones you change in the bios, and leave everything else on auto.


  • CL: CAS Latency. The time it takes between a command having been sent to the memory and when it begins to reply to it. It is the time it takes between the processor asking for some data from the memory and then returning it.
  • tRCD: RAS to CAS Delay. The time it takes between the activation of the line (RAS) and the column (CAS) where the data are stored in the matrix.
  • tRP: RAS Precharge. The time it takes between disabling the access to a line of data and the beginning of the access to another line of data.
  • tRAS: Active to Precharge Delay. How long the memory has to wait until the next access to the memory can be initiated.
  • CMD: Command Rate. The time it takes between the memory chip having been activated and when the first command may be sent to the memory. Sometimes this value is not announced. It usually is T1 (1 clock cycle) or T2 (2 clock cycles).

The voltage should be set to 1.35v on the mem. Then try again and see how you get on.
 
Upvote 0 Downvote
  1. My DIMMs say 16-18-18-36
  2. With everything set to Auto, HWiNFO shows timing 15-15-15-36
  3. I changed DRAM CAS# Latency to 16, DRAM RAS#to CAS# Delay to 18, and DRAM RAS# ACT Time to 36
  4. I changed DRAM Voltage from Auto to 1.350. Next to Auto it showed 1.200V
  5. I saved these changed in BIOS
  6. HWiNFO shows the timig as 16-18-18-36 now. The voltage was 1.35V before and after. I don't know where that 1.200V comes from

I haven't crashed in a couple hours before making these changes. It could take days to tell if these changes have an effect. Just gotta wait for the next crash. BTW I appreciate the help. I've posted in several forums for a couple months and this is the first someone has given me actual steps to take. Thank you.
 
Upvote 0 Downvote
scout_03 said:
use whocrashed to read minidump in plain text files and hwinfo to check all voltages and temp on sensor page report the readings .
Click to expand...
Thank you, those programs are super useful. The voltage for the memory looks like 1.35V. All the temps look in order. CPU averaging 34C. I changed some DIMM timings in BIOS per keith12's advice. Here is a before and after screenshot of HWiNFO.


On Thu 12/19/2019 10:08:32 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\121919-7468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xEF (0xFFFF968448B3D4C0, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 12/19/2019 10:08:32 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: bcryptprimitives.sys (bcryptPrimitives!GetKeyDerivationInterface+0x1B460)
Bugcheck code: 0xEF (0xFFFF968448B3D4C0, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bcryptprimitives.sys .
Google query: bcryptprimitives.sys CRITICAL_PROCESS_DIED



On Thu 12/19/2019 10:08:32 your computer crashed or a problem was reported
crash dump file: C:\Users\David\OneDrive\dmp\new mobo\121919-7468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xEF (0xFFFF968448B3D4C0, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 12/19/2019 07:50:05 your computer crashed or a problem was reported
crash dump file: C:\Users\David\OneDrive\dmp\new mobo\121919-7375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xA (0xFFFFF80275C22AED, 0xFF, 0x0, 0xFFFFF80277C22AED)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 12/19/2019 07:48:17 your computer crashed or a problem was reported
crash dump file: C:\Users\David\OneDrive\dmp\new mobo\121919-6828-01.dmp
This was probably caused by the following module: storport.sys (0xFFFFF8072A990B31)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8072A990B31, 0x0, 0x1F82)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Thu 12/19/2019 07:46:13 your computer crashed or a problem was reported
crash dump file: C:\Users\David\OneDrive\dmp\new mobo\121919-7437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xA (0xFFFFF80474FCF1F9, 0xFF, 0xE2, 0xFFFFF80476FCF1F9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 12/19/2019 07:38:08 your computer crashed or a problem was reported
crash dump file: C:\Users\David\OneDrive\dmp\new mobo\121919-4500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xA (0xFFFFF80528C23181, 0xFF, 0xD5, 0xFFFFF8052AC23181)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 12/19/2019 07:37:15 your computer crashed or a problem was reported
crash dump file: C:\Users\David\OneDrive\dmp\new mobo\121919-4593-01.dmp
This was probably caused by the following module: storport.sys (storport+0x4342)
Bugcheck code: 0xA (0xFFFFF804285D465C, 0xFF, 0x37, 0xFFFFF8042A5D465C)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Thu 12/19/2019 07:35:45 your computer crashed or a problem was reported
crash dump file: C:\Users\David\OneDrive\dmp\new mobo\121919-4343-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF8002A8B8333)
Bugcheck code: 0xA (0xFFFFF800288B8333, 0xFF, 0xE2, 0xFFFFF8002A8B8333)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 12/19/2019 07:30:55 your computer crashed or a problem was reported
crash dump file: C:\Users\David\OneDrive\dmp\new mobo\121919-4406-01.dmp
This was probably caused by the following module: storport.sys (0xFFFFF8022A56D3E2)
Bugcheck code: 0xD1 (0xFFFFF8022856D3E2, 0x2, 0x8, 0xFFFFF8022A56D3E2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
 
Upvote 0 Downvote
IF i see lots of different errors, my 1st go to is memtest.

If Prime95 crashes, it might still show results in the text file in its install directory.
You can make a bootable version of Prime95 and see if it works any better - https://www.infopackets.com/news/10113/how-fix-bootable-prime95-stress-test-hardware

spiffling said:
Caused by:
  • hal.dll
  • ntoskrnl.exe
  • intelppm.sys
  • storport.sys
  • ndis.sys
  • wfplwfs.sys
  • stornvme.sys
  • NETIO.SYS
  • cng.sys
  • fileinfo.sys
  • iorate.sys
  • Ntfs.sys
  • dxgmms2.sys
  • win32kfull.sys
  • watchdog.sys
  • icrate.sys
  • nvlddmkm.sys
Click to expand...

Some of these could be GPU drivers - dxgmms2.sys, nvlddmkm.sys & win32kfull.sys are often found in Nvidia driver errors.
hal.dll & ntoskrnl combined often show up in WHEA errors, as does intelppm.sys
storport.sys and stornvme.sys are storage drivers, 1st can be USB devices, 2nd is the NVME

rest aren't as common and so random I would once again look at ram.. but it could be CPU still since Prime crashes, and memory controller is on CPU.
 
Last edited:
Upvote 0 Downvote
Hi, I downloaded 8 dumps from the "New Mobo" folder. The 6 most recent dumps + 2 older ones. I ran them through the debugger and got the following results: https://untutoredpair.htmlpasta.com/ (This htmlpasta site is new for me, I hope it works out.)
File information:121919-8140-01.dmp (Dec 19 2019 - 10:14:14)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:memory_corruption (Process: iCUE.exe)
Uptime:0 Day(s), 0 Hour(s), 03 Min(s), and 13 Sec(s)

File information:121919-7625-01.dmp (Dec 19 2019 - 10:16:46)
Bugcheck:DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 00 Min(s), and 05 Sec(s)

File information:121919-7593-01.dmp (Dec 19 2019 - 04:04:20)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:memory_corruption (Process: iCUE.exe)
Uptime:0 Day(s), 1 Hour(s), 27 Min(s), and 55 Sec(s)

File information:121919-7562-01.dmp (Dec 19 2019 - 10:09:42)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 00 Min(s), and 16 Sec(s)

File information:121919-7484-01.dmp (Dec 19 2019 - 04:06:22)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 01 Min(s), and 25 Sec(s)

File information:121919-7468-01.dmp (Dec 19 2019 - 13:08:32)
Bugcheck:CRITICAL_PROCESS_DIED (EF)
Probably caused by:ntkrnlmp.exe (Process: csrss.exe)
Uptime:0 Day(s), 0 Hour(s), 03 Min(s), and 53 Sec(s)

File information:121519-6875-01.dmp (Dec 15 2019 - 08:05:09)
Bugcheck:ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (FC)
Probably caused by:memory_corruption (Process: Corsair.Service.exe)
Uptime:0 Day(s), 0 Hour(s), 01 Min(s), and 32 Sec(s)

File information:121419-7515-01.dmp (Dec 14 2019 - 11:37:30)
Bugcheck:DRIVER_PORTION_MUST_BE_NONPAGED (D3)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 47 Min(s), and 46 Sec(s)
Possible Motherboard page: https://www.asus.com/us/Motherboards/ROG-MAXIMUS-XI-HERO-WI-FI/
It appears you have the latest BIOS already installed.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Upvote 0 Downvote
new dump site looks good to me - might want to look at the driver names and dates on the Driver page, random odd character showing on each.

last error you got could be gpu drivers. I often see win32kfull with relation to GPU drivers
2 of them appear to be storage related.

crash on 15th mentions drivers associated with drives like iorate.sys which is the Disk I/O rate control Filter driver - http://batcmd.com/windows/10/services/iorate/
2nd crash on 19th mentions stornvme which is a win 10 driver,
also mentions storport.sys which is the Microsoft Storage Port Driver. Updating chipset driver might help it.
Have you run any scans on the 2 ssd?

it seems odd that there is no download on board for Intel Rapid Storage Technology driver as it might also fix the storage errors.

strange your bios number is newest but date on it is earlier than what it shows as being released on Asus site.

Update your chipset driver as your current one is from 2018 and it should match the bios. MIght help.
I assume Intel HD GPU drivers are running as you took GPU out at one stage.

https://www.asus.com/au/Motherboards/ROG-MAXIMUS-XI-HERO-WI-FI/HelpDesk_Download/


IRQ errors can be drivers or ram, 2nd one mentioning driver sure is a clue, all of those could be drivers except for critical process died as its not like the other errors, its a windows error but can be caused by hardware. csrss.exe = client services - The service your user runs in. If it crashes, windows follows. Its unclear what caused it.

Shame you probably don't want to run driver verifer again. I hate that boot loop it gets into, i did write a guide for it with precautions - see 2nd post if you interested - https://forums.tomshardware.com/thr...nclude-in-blue-screen-of-death-posts.3468965/
 
Upvote 0 Downvote
This might be a silly suggestion but years ago (back in the Windows Vista days) I kept getting BSOD's and it turned out to be the keyboard that was the culprit. It's extremely unlikely but worth trying different peripherals before buying a new CPU if you've swapped everything else.
 
Upvote 0 Downvote
pmjm said:
This might be a silly suggestion but years ago (back in the Windows Vista days) I kept getting BSOD's and it turned out to be the keyboard that was the culprit. It's extremely unlikely but worth trying different peripherals before buying a new CPU if you've swapped everything else.
Click to expand...
BSOD can be anything so no such thing as a silly suggestion :)
 
Upvote 0 Downvote
spiffling said:
Minidump files: https://1drv.ms/u/s!Alk3aVYQMM1-ik6Qgz0XieJqdigF?e=oaTcLa

Hardware:
  • OS: Windows 10 1909
  • CPU: i9900k
  • Mobo: Asus Maximus XI Hero (Wifi)
  • GPU: Aorus RTX 2080 TI
  • RAM: Corsair Vengance RGB PRO 32GB (4x8GB) DDR4 3200MHz 15-15-15-36
  • Storage: 2x Silicon Power 1TB NVMe PCIe Gen3 x4 M.2 TLC
  • PSU: Corsair RM850x
I unplugged every thing from the mobo except monitor and keyboard
I swapped to different monitor and keyboard
I swapped RAM twice
I unplugged the GPU
I swapped hard drives to SATA
I reinstalled Windows... a lot
I swapped to an identical motherboard

The only consistent hardware at this point is the CPU and the PSU

Whats Happening:
PC will be fine for a couple days and then crash and reset every 10 seconds. Sometimes it shows a BSOD but mostly it doesn't. It makes a dmp file maybe 10% of the time. It will even crash while restarting from a crash. It will crash while doing the "Repairing your PC." I'm nearly out of hardware to replace so that makes me think it's software/driver related. But when I changed hard drives and was reinstalling windows from a USB stick it crashed. So I removed the hard drives completely and it still crashed at this point from the USB installer. Is there driver activity going on there? That makes me feel like its hardware but I'm making guesses outside my expertise. It has crashed maybe 5 times in safe mode.

On the BSODs I have seen

  • DRIVER_IRQL_NOT_LESS_OR_EQUAL
  • IRQL_NOT_LESS_OR_EQUAL
  • ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
  • SYSTEM_SERVICE_EXCEPTION
  • PAGE_FAULT_IN_NONPAGED_AREA
  • KMODE_EXCEPTION_NOT_HANDLED
Caused by:
  • hal.dll
  • ntoskrnl.exe
  • intelppm.sys
  • storport.sys
  • ndis.sys
  • wfplwfs.sys
  • stornvme.sys
  • NETIO.SYS
  • cng.sys
  • fileinfo.sys
  • iorate.sys
  • Ntfs.sys
  • dxgmms2.sys
  • win32kfull.sys
  • watchdog.sys
  • icrate.sys
  • nvlddmkm.sys
I've tried:
  • scf /scannow (no integrity violations found)
  • chkdsk /f /r on both drives (no problems found)
  • Full virus scan
  • Windows Memory Diagnostic (No memory errors detected)
  • Fresh reinstall of Windows
  • Windows Updates are up to date
  • Updated BIOS
  • Intel Processor Diagnostic Tool (pass)
  • Replaced all hardware except CPU and PSU
  • Windows Driver Verifier (can't get back into windows, had to reinstall)
  • Can't do Memtest or Prime95 because it crashes. I've tried 3 different brand memory anyway.
Click to expand...



"To learn who rules over you, simply find out who you are not allowed to criticize" - Some guy

Since its not allowing you to criticize your memory using more reputable tools, then that might be your main culprit, it has something to hide. Others are saying your CPU may be the problem, but I see you already tested that out, although I'm not sure how reliable that test really is. How many anti virus programs do you have installed? Having too many can cause problems in of itself.
 
Upvote 0 Downvote
Dcopymope said:
Since its not allowing you to criticize your memory using more reputable tools, then that might be your main culprit, it has something to hide.
Click to expand...

Op has used multiple ram sticks already, refer:
spiffling said:
Can't do Memtest or Prime95 because it crashes. I've tried 3 different brand memory anyway.
Click to expand...

CPU & ram tests both didn't work, and since memory controller is on the CPU, it could be the cause. Until a test actually concludes, we cannot be certain.

Dcopymope said:
How many anti virus programs do you have installed? Having too many can cause problems in of itself.
Click to expand...

No AV showing in driver list which makes me suspect they are using Defender

at OP, I would be tempted to get PC looked at by repair store as they should have spare parts that they know do work, to isolate the part that doesn't
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom