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): Previous 1 2 3 Next
B
blondeminion
Senior Member
594
12-14-2016, 02:19 AM
#11
B
blondeminion
12-14-2016, 02:19 AM #11

P
pa55w0rd
Member
181
12-14-2016, 02:19 AM
#12
That’s the support for League of Legends on Riot Games, right? I don’t think it’s the issue—just don’t mind me deleting it if you play it occasionally.
P
pa55w0rd
12-14-2016, 02:19 AM #12

That’s the support for League of Legends on Riot Games, right? I don’t think it’s the issue—just don’t mind me deleting it if you play it occasionally.

D
DarkSkullYT
Junior Member
33
12-14-2016, 02:19 AM
#13
It triggered two system failures or was linked to them, so turn it off and observe the outcome. Additional crashes will appear if you upload the crash dumps.
D
DarkSkullYT
12-14-2016, 02:19 AM #13

It triggered two system failures or was linked to them, so turn it off and observe the outcome. Additional crashes will appear if you upload the crash dumps.

E
EpicMrPear
Junior Member
4
12-14-2016, 02:19 AM
#14
For those particular issues I encountered, installing League of Legends doesn't lead to crashes.
E
EpicMrPear
12-14-2016, 02:19 AM #14

For those particular issues I encountered, installing League of Legends doesn't lead to crashes.

S
Smileyman130
Junior Member
16
12-14-2016, 02:19 AM
#15
Windows didn't install smoothly, but if it does, the problems might be elsewhere. Use the PC normally, and when it fails, share the BSoD so we can check what the newest version provides.
S
Smileyman130
12-14-2016, 02:19 AM #15

Windows didn't install smoothly, but if it does, the problems might be elsewhere. Use the PC normally, and when it fails, share the BSoD so we can check what the newest version provides.

C
CampenBros
Junior Member
27
12-14-2016, 02:19 AM
#16
Sure, let me know if you're ready to proceed.
C
CampenBros
12-14-2016, 02:19 AM #16

Sure, let me know if you're ready to proceed.

P
151
12-14-2016, 02:19 AM
#17
The system stopped immediately. Driver verifier found a violation with ID 011322-37218-01.dmp.
P
PerritaMacrera
12-14-2016, 02:19 AM #17

The system stopped immediately. Driver verifier found a violation with ID 011322-37218-01.dmp.

D
Derpy_MC
Member
228
12-14-2016, 02:19 AM
#18
Hold on while I process.
D
Derpy_MC
12-14-2016, 02:19 AM #18

Hold on while I process.

Y
yona1234
Junior Member
42
12-14-2016, 02:19 AM
#19
A driver trying to damage the system has been identified. This happened because the administrator marked it as suspicious in the registry and the kernel now performs thorough checks on this driver. If the driver tries to harm the system, specific bugs 0xC4, 0xC1 and 0xA will likely occur. The crash count for this issue is 1. The process running is PEUpdater.exe, with symbol AsUpIO+2359, module AsUpIO. The image name is AsUpIO.sys. The stack command is .thread ; .cxr ; kb. The failure bucket ID is 0xc4_f6_VRFK_AsUpIO!unknown_function. I recommend examining AsUpIO.sys and PEUpdater.exe to understand their behavior.
Y
yona1234
12-14-2016, 02:19 AM #19

A driver trying to damage the system has been identified. This happened because the administrator marked it as suspicious in the registry and the kernel now performs thorough checks on this driver. If the driver tries to harm the system, specific bugs 0xC4, 0xC1 and 0xA will likely occur. The crash count for this issue is 1. The process running is PEUpdater.exe, with symbol AsUpIO+2359, module AsUpIO. The image name is AsUpIO.sys. The stack command is .thread ; .cxr ; kb. The failure bucket ID is 0xc4_f6_VRFK_AsUpIO!unknown_function. I recommend examining AsUpIO.sys and PEUpdater.exe to understand their behavior.

D
DrunkMemories
Member
74
12-14-2016, 02:19 AM
#20
It failed once more using IRQL <= code 011322-42343-01.dmp
D
DrunkMemories
12-14-2016, 02:19 AM #20

It failed once more using IRQL <= code 011322-42343-01.dmp

Pages (3): Previous 1 2 3 Next