Hi,
We have three bug checks:
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high. This bug check is usually caused by drivers that have used improper addresses.
Code:
1: kd> kv
Child-SP RetAddr : Args to Child : Call Site
fffff880`0d9539b8 fffff800`030d1169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0d9539c0 fffff800`030cfde0 : 00000000`00000000 fffffa80`0fea6830 fffffa80`1107b030 fffffa80`0ffc7000 : nt!KiBugCheckDispatch+0x69
fffff880`0d953b00 fffff880`09a5b1bf : fffff880`01b6e9a0 fffffa80`1109f7a0 00000000`00000011 fffff880`0d953ce0 : nt!KiPageFault+0x260 (TrapFrame @ fffff880`0d953b00)
fffff880`0d953c90 fffff880`01b6e9a0 : fffffa80`1109f7a0 00000000`00000011 fffff880`0d953ce0 fffff880`00000000 : 0xfffff880`09a5b1bf
fffff880`0d953c98 fffffa80`1109f7a0 : 00000000`00000011 fffff880`0d953ce0 fffff880`00000000 fffff880`0d953cc0 : tcpip!Ipv4Global
fffff880`0d953ca0 00000000`00000011 : fffff880`0d953ce0 fffff880`00000000 fffff880`0d953cc0 00000000`00000000 : 0xfffffa80`1109f7a0
fffff880`0d953ca8 fffff880`0d953ce0 : fffff880`00000000 fffff880`0d953cc0 00000000`00000000 fffff880`0d953cc0 : 0x11
fffff880`0d953cb0 fffff880`00000000 : fffff880`0d953cc0 00000000`00000000 fffff880`0d953cc0 00000000`00000000 : 0xfffff880`0d953ce0
fffff880`0d953cb8 fffff880`0d953cc0 : 00000000`00000000 fffff880`0d953cc0 00000000`00000000 fffff880`0d953cd0 : 0xfffff880`00000000
fffff880`0d953cc0 00000000`00000000 : fffff880`0d953cc0 00000000`00000000 fffff880`0d953cd0 00000000`00000000 : 0xfffff880`0d953cc0
From the call stack, it looks like we had
tcpip.sys attempt to access paged-out memory. I've never seen a Windows system driver call spoof memory addresses, so this is likely a hardware problem.
SYSTEM_SERVICE_EXCEPTION (3b)
This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
Code:
STACK_TEXT:
fffff880`0d5c3970 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0xe01a9
^^ nVidia video driver.
INTERRUPT_EXCEPTION_NOT_HANDLED (0x3D)
This bug check appears very infrequently.
Generally only occurs when a hardware fault is present.
1. AppleCharger.sys is listed and loaded which is the GIGABYTE On/Off Charge driver. See here for details -
GIGABYTE ON/OFF Charge
Very problem software, so please uninstall ASAP.
2. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.
3. Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.
4. Your Lycosa drivers are dated circa 2008, please update ASAP if available -
Razer Support
--- Be 100% sure the SSD firmware is at its latest version.
Regards,
Patrick
