Result of !analyze -v
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80c82926304, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Unable to load image Netwtw04.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Netwtw04.sys
*** ERROR: Module load completed but symbols could not be loaded for Netwtw04.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
FAULTING_MODULE: fffff802cca92000 nt
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
fffff80c`82926304 8b8098000000 mov eax,dword ptr [rax+98h]
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
LAST_CONTROL_TRANSFER: from fffff802ccc5ff52 to fffff802ccbe07c0
fffff802`cf05d118 fffff802`ccc5ff52 : 00000000`0000001e ffffffff`c0000005 fffff80c`82926304 00000000`00000000 : nt+0x14e7c0
fffff802`cf05d120 00000000`0000001e : ffffffff`c0000005 fffff80c`82926304 00000000`00000000 ffffffff`ffffffff : nt+0x1cdf52
fffff802`cf05d128 ffffffff`c0000005 : fffff80c`82926304 00000000`00000000 ffffffff`ffffffff fffff80c`82a1da55 : 0x1e
fffff802`cf05d130 fffff80c`82926304 : 00000000`00000000 ffffffff`ffffffff fffff80c`82a1da55 fffff802`cf05d290 : 0xffffffff`c0000005
fffff802`cf05d138 00000000`00000000 : ffffffff`ffffffff fffff80c`82a1da55 fffff802`cf05d290 fffff802`ccbe6bbd : Netwtw04+0x36304
*** Memory manager detected 79304 instance(s) of page corruption, target is likely to have memory corruption.
Please try our latest driver as suggested by al.hill and let us know if the issue is resolved. Additionally you may want to run a RAM test, as faulty RAM is one of the top misdiagnosed BSOD triggers.
NOTE: Any links provided for third party tools or sites are offered for your convenience and should not be viewed as an endorsement by Intel® of the content, products, or services offered there. We do not offer support for any third party tool mentioned here.
We heaven't heard from you in a while, has your issue been resolved?
Please let us know if you would like further assistance.
We're glad to hear that your problem has been resolved.
Please keep in mind that our driver software will not automatically notify you when new drivers are released. This process is expected to be performed manually.
However we do have a tool to help you keep the drivers for the Intel® components on your system up to date. If you're interested in this, feel free to give the Intel® Driver Update Utility a try.