F5F Stay Refreshed Hardware Desktop Irql failed due to ntoskrnl.exe stopping after removing a memory stick, but it continues to crash every few hours.

Irql failed due to ntoskrnl.exe stopping after removing a memory stick, but it continues to crash every few hours.

Irql failed due to ntoskrnl.exe stopping after removing a memory stick, but it continues to crash every few hours.

Pages (3): 1 2 3 Next
B
BookMix
Member
207
12-14-2016, 02:18 AM
#1
I've done everything possible; even resetting the system didn't help. It kept crashing every 10-20 minutes, sometimes starting at boot. After removing one of my two memory sticks, it improved a bit, but it still bluescreens every 3-4 hours. The files provided are: 011322-39531-01.dmp, 011322-28156-01.dmp, 011322-34843-01.dmp.
B
BookMix
12-14-2016, 02:18 AM #1

I've done everything possible; even resetting the system didn't help. It kept crashing every 10-20 minutes, sometimes starting at boot. After removing one of my two memory sticks, it improved a bit, but it still bluescreens every 3-4 hours. The files provided are: 011322-39531-01.dmp, 011322-28156-01.dmp, 011322-34843-01.dmp.

U
UnleqitWizard
Member
122
12-14-2016, 02:18 AM
#2
System details are available? An IRQ value not lower than equal often signals a poor overclock on the CPU or memory.
U
UnleqitWizard
12-14-2016, 02:18 AM #2

System details are available? An IRQ value not lower than equal often signals a poor overclock on the CPU or memory.

B
blondeminion
Senior Member
594
12-14-2016, 02:18 AM
#3
No need for heavy overclocking with your GTX 1060 setup. It runs smoothly on the 6GB RAM and 16GB DDR4 3000MHz configuration. The 750W Corsair power supply should provide enough energy for your components.
B
blondeminion
12-14-2016, 02:18 AM #3

No need for heavy overclocking with your GTX 1060 setup. It runs smoothly on the 6GB RAM and 16GB DDR4 3000MHz configuration. The 750W Corsair power supply should provide enough energy for your components.

C
ChickenPhoYou
Posting Freak
850
12-14-2016, 02:18 AM
#4
XMP/DOCP enabled? This is an overclock.
C
ChickenPhoYou
12-14-2016, 02:18 AM #4

XMP/DOCP enabled? This is an overclock.

C
Coudz
Junior Member
13
12-14-2016, 02:18 AM
#5
It seems like XMP was still causing issues even after disabling it. I followed a suggestion from someone who fixed it by turning off the XMP profile and then manually tweaking the settings. That worked for me.
C
Coudz
12-14-2016, 02:18 AM #5

It seems like XMP was still causing issues even after disabling it. I followed a suggestion from someone who fixed it by turning off the XMP profile and then manually tweaking the settings. That worked for me.

S
Siph18
Member
97
12-14-2016, 02:18 AM
#6
Download memtest86, prepare a USB drive, install it, and test for RAM issues. One pass should take roughly an hour to complete.
S
Siph18
12-14-2016, 02:18 AM #6

Download memtest86, prepare a USB drive, install it, and test for RAM issues. One pass should take roughly an hour to complete.

B
ByFeNix1350
Senior Member
502
12-14-2016, 02:18 AM
#7
Review the crash logs for analysis.
B
ByFeNix1350
12-14-2016, 02:18 AM #7

Review the crash logs for analysis.

Z
Zoe783
Member
180
12-14-2016, 02:18 AM
#8
First crash log: IRQL_NOT_LESS_OR_EQUAL (a) A try was made to reach a pageable or invalid memory location during an interrupt request. This typically results from drivers using wrong addresses. PROCESS_NAME: RiotClientServices.exe MODULE_NAME: tcpip IMAGE_NAME: tcpip.sys ___ 2nd crash log: Same as the first ___ 3rd crash log: IRQL_NOT_LESS_OR_EQUAL (a) A try was made to reach a pageable or invalid memory location during an interrupt request. This usually stems from drivers using incorrect addresses. BUGCHECK_CODE: A BUGCHECK_P1: 3134 BUGCHECK_P2: ff BUGCHECK_P3: a0 ___ As others mentioned, begin with your RAM testing. Non-repeating crash dumps indicate faulty RAM. Please reply, we'll proceed from there
Z
Zoe783
12-14-2016, 02:18 AM #8

First crash log: IRQL_NOT_LESS_OR_EQUAL (a) A try was made to reach a pageable or invalid memory location during an interrupt request. This typically results from drivers using wrong addresses. PROCESS_NAME: RiotClientServices.exe MODULE_NAME: tcpip IMAGE_NAME: tcpip.sys ___ 2nd crash log: Same as the first ___ 3rd crash log: IRQL_NOT_LESS_OR_EQUAL (a) A try was made to reach a pageable or invalid memory location during an interrupt request. This usually stems from drivers using incorrect addresses. BUGCHECK_CODE: A BUGCHECK_P1: 3134 BUGCHECK_P2: ff BUGCHECK_P3: a0 ___ As others mentioned, begin with your RAM testing. Non-repeating crash dumps indicate faulty RAM. Please reply, we'll proceed from there

D
DeathBeastDB
Senior Member
337
12-14-2016, 02:18 AM
#9
It might be a faulty RAM chip or an incompatibility issue. I experienced similar problems, but no faulty RAM was found. A BIOS update resolved it, though the main concern seemed to be the MSI BIOS rather than the RAM itself.
D
DeathBeastDB
12-14-2016, 02:18 AM #9

It might be a faulty RAM chip or an incompatibility issue. I experienced similar problems, but no faulty RAM was found. A BIOS update resolved it, though the main concern seemed to be the MSI BIOS rather than the RAM itself.

E
emstay26
Senior Member
441
12-14-2016, 02:18 AM
#10
The memtest confirmed success with no errors. Occasionally, the system freezes and emits a static noise instead of a clean pass. This might be related to the same problem.
E
emstay26
12-14-2016, 02:18 AM #10

The memtest confirmed success with no errors. Occasionally, the system freezes and emits a static noise instead of a clean pass. This might be related to the same problem.

Pages (3): 1 2 3 Next