Mini Dump Help

[MaStA819]

Could someone possibly help me with this mini dump? I started receiving this a couple months ago after getting a new SSD. I RMA'd the SSD (Crucial M4) thinking it was causing it. I received a new one today and still received the same blue screen. The blue screen is random. It happens randomly at idle, while browsing the web, and playing games. I ran memtest with no errors as well. I've set the BIOS to defaults and still have blue screens, etc. I've tried the latest Intel network driver and the network driver from the ASUS cd and both give me the errors.

I called ASUS and they gave me some bs about if it posts and boots then it isn't the motherboard. I don't buy that obviously because I know things can somewhat work, but still be faulty. Right now I'm at the point of RMA'ing the motherboard which they have sent me, but I figured I would seek assistance from the great member base of this forum and see if someone can shed a little more light on it.

I did have to take some colons out here and there since the forum said I had too many smileys or something, but I don't think that will affect the outcome of what you are looking at.

ASUS P8P67 Pro 3.0
Intel 2500k
G.Skill 8GB ram
Corsair TX750 PSU

Thank you for any help you can provide,
Jared

BugCheck 1000007E, {ffffffffc0000005, fffff880015237ba, fffff880031bd708, fffff880031bcf60}

*** WARNING: Unable to verify timestamp for epfwwfp.sys
*** ERROR: Module load completed but symbols could not be loaded for epfwwfp.sys
TRIAGER: Could not open triage file : C Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
Probably caused by : NETIO.SYS ( NETIO!NetioCompleteCloneNetBufferListChain+9a )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880015237ba, The address that the exception occurred at
Arg3: fffff880031bd708, Exception Record Address
Arg4: fffff880031bcf60, Context Record Address

Debugging Details:
------------------

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
NETIO!NetioCompleteCloneNetBufferListChain+9a
fffff880`015237ba 488b01 mov rax,qword ptr [rcx]

EXCEPTION_RECORD: fffff880031bd708 -- (.exr 0xfffff880031bd708)
ExceptionAddress: fffff880015237ba (NETIO!NetioCompleteCloneNetBufferListChain+0x000000000000009a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

CONTEXT: fffff880031bcf60 -- (.cxr 0xfffff880031bcf60)
rax=fffffa8008a863b0 rbx=fffffa8006e36160 rcx=0000000000000000
rdx=0000000000001000 rsi=00000000fffffe0d rdi=fffff880031bd900
rip=fffff880015237ba rsp=fffff880031bd940 rbp=fffffa800807e000
r8=fffff78000000320 r9=0000000000000002 r10=fffff88002f65e80
r11=fffffa800808a5e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
NETIO!NetioCompleteCloneNetBufferListChain+0x9a:
fffff880`015237ba 488b01 mov rax,qword ptr [rcx] ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: NULL_DEREFERENCE

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c6100
GetUlongFromAddress: unable to read from fffff800030c61c0
0000000000000000 Nonpaged pool

FOLLOWUP_IP:
NETIO!NetioCompleteCloneNetBufferListChain+9a
fffff880`015237ba 488b01 mov rax,qword ptr [rcx]

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff88001515336 to fffff880015237ba

STACK_TEXT:
fffff880`031bd940 fffff880`01515336 : 00000000`00000000 fffffa80`06e36030 00000000`00000000 fffff880`031bd900 : NETIO!NetioCompleteCloneNetBufferListChain+0x9a
fffff880`031bd9b0 fffff880`01897256 : fffffa80`06e36030 fffffa80`0a218c90 fffffa80`0a218c90 fffffa80`06e36100 : NETIO!NetioDereferenceNetBufferList+0x86
fffff880`031bd9e0 fffff880`04607018 : fffff880`0460c7e0 fffffa80`06e36160 00000000`00000000 00000000`00000000 : fwpkclnt!FwpsDereferenceNetBufferList0+0xaa
fffff880`031bda30 fffff880`0460c7e0 : fffffa80`06e36160 00000000`00000000 00000000`00000000 fffff880`0460c7e0 : epfwwfp+0x7018
fffff880`031bda38 fffffa80`06e36160 : 00000000`00000000 00000000`00000000 fffff880`0460c7e0 fffff880`0460705a : epfwwfp+0xc7e0
fffff880`031bda40 00000000`00000000 : 00000000`00000000 fffff880`0460c7e0 fffff880`0460705a 00000000`00000000 : 0xfffffa80`06e36160


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: NETIO!NetioCompleteCloneNetBufferListChain+9a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME: NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79381

STACK_COMMAND: .cxr 0xfffff880031bcf60 ; kb

FAILURE_BUCKET_ID: X64_0x7E_NETIO!NetioCompleteCloneNetBufferListChain+9a

BUCKET_ID: X64_0x7E_NETIO!NetioCompleteCloneNetBufferListChain+9a

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1 ffffffffc0000005, The exception code that was not handled
Arg2 fffff880015237ba, The address that the exception occurred at
Arg3 fffff880031bd708, Exception Record Address
Arg4 fffff880031bcf60, Context Record Address

Debugging Details:
------------------

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
NETIO!NetioCompleteCloneNetBufferListChain+9a
fffff880`015237ba 488b01 mov rax,qword ptr

EXCEPTION_RECORD: fffff880031bd708 -- (.exr 0xfffff880031bd708)
ExceptionAddress: fffff880015237ba (NETIO!NetioCompleteCloneNetBufferListChain+0x000000000000009a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

CONTEXT: fffff880031bcf60 -- (.cxr 0xfffff880031bcf60)
rax=fffffa8008a863b0 rbx=fffffa8006e36160 rcx=0000000000000000
rdx=0000000000001000 rsi=00000000fffffe0d rdi=fffff880031bd900
rip=fffff880015237ba rsp=fffff880031bd940 rbp=fffffa800807e000
r8=fffff78000000320 r9=0000000000000002 r10=fffff88002f65e80
r11=fffffa800808a5e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
NETIO!NetioCompleteCloneNetBufferListChain+0x9a:
fffff880`015237ba 488b01 mov rax,qword ptr ds: 002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: NULL_DEREFERENCE

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

READ_ADDRESS: 0000000000000000 Nonpaged pool

FOLLOWUP_IP:
NETIO!NetioCompleteCloneNetBufferListChain+9a
fffff880`015237ba 488b01 mov rax,qword ptr

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff88001515336 to fffff880015237ba

STACK_TEXT:
fffff880`031bd940 fffff880`01515336 : 00000000`00000000 fffffa80`06e36030 00000000`00000000 fffff880`031bd900 : NETIO!NetioCompleteCloneNetBufferListChain+0x9a
fffff880`031bd9b0 fffff880`01897256 : fffffa80`06e36030 fffffa80`0a218c90 fffffa80`0a218c90 fffffa80`06e36100 : NETIO!NetioDereferenceNetBufferList+0x86
fffff880`031bd9e0 fffff880`04607018 : fffff880`0460c7e0 fffffa80`06e36160 00000000`00000000 00000000`00000000 : fwpkclnt!FwpsDereferenceNetBufferList0+0xaa
fffff880`031bda30 fffff880`0460c7e0 : fffffa80`06e36160 00000000`00000000 00000000`00000000 fffff880`0460c7e0 : epfwwfp+0x7018
fffff880`031bda38 fffffa80`06e36160 : 00000000`00000000 00000000`00000000 fffff880`0460c7e0 fffff880`0460705a : epfwwfp+0xc7e0
fffff880`031bda40 00000000`00000000 : 00000000`00000000 fffff880`0460c7e0 fffff880`0460705a 00000000`00000000 : 0xfffffa80`06e36160


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: NETIO!NetioCompleteCloneNetBufferListChain+9a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME : NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79381

STACK_COMMAND : .cxr 0xfffff880031bcf60 ; kb

FAILURE_BUCKET_ID : X64_0x7E_NETIO!NetioCompleteCloneNetBufferListChain+9a

BUCKET_ID: X64_0x7E_NETIO!NetioCompleteCloneNetBufferListChain+9a

Followup: MachineOwner
---------

 

[paul878]

run memory test for a few pass and see what happen.

 

[Bubbaleone]

Could someone possibly help me with this mini dump? ..............
ASUS P8P67 Pro 3.0
Intel 2500k
G.Skill 8GB ram
Corsair TX750 PSU

Thank you for any help you can provide,
Jared

epfwwfp.sys is a component of your ESET Personal Firewall. When it tries to access the web for an update, NETIO.SYS is causing the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) fault. Your BSOD is networking related, but as you've already updated to the latest Intel LAN drivers, I suspect your problem is ESET.

Uninstall ESET and see if the BSOD's stop. If they do, go to ESET and get the latest program version. ESET's firewall works directly with the native TCP/IP stack and, depending on the ESET Personal Firewall program version, some don't play so nice.

 

[MaStA819]

epfwwfp.sys is a component of your ESET Personal Firewall. When it tries to access the web for an update, NETIO.SYS is causing the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) fault. Your BSOD is networking related, but as you've already updated to the latest Intel LAN drivers, I suspect your problem is ESET.

Uninstall ESET and see if the BSOD's stop. If they do, go to ESET and get the latest program version. ESET's firewall works directly with the native TCP/IP stack and, depending on the ESET Personal Firewall program version, some don't play so nice.

That sounds like it could definitely be the issue. I will get rid of ESET and try things again. Thank you!

 

[MaStA819]

Bubbaleone,

So far so good, but I haven't been on the computer too long since removing eset nod32. I've read somewhere that sometimes software may trigger a blue screen, but there may still be an underlying problem with the hardware that is truly at fault. I'm just concerned there is something wrong with my motherboard causing this to happen. I am using the latest eset nod32 software and it is on a clean installation of windows. It just seems weird I would have this problem and no one else does that I can find. My computer was working fine with no issues when I had my OCZ SSD and as soon as I switched to my Crucial M4 these issues started.

Do you think I should be safe and RMA the motherboard or do you think I would be wasting my time with that?

Thank you,
Jared

 

[Bubbaleone]

You should dig into this a little further before you RMA a (perfectly good) mobo. As I said previously, the memory dump shows a networking issue. If you've saved dumps from previous BSOD's you should compare them and see if the same system files are always involved.

Was EPFW already installed before you installed the original SSD? Was EPFW the same version your running now? If so, were you seeing any problems then?...think carefully.

 

[MaStA819]

You should dig into this a little further before you RMA a (perfectly good) mobo. As I said previously, the memory dump shows a networking issue. If you've saved dumps from previous BSOD's you should compare them and see if the same system files are always involved.

Was EPFW already installed before you installed the original SSD? Was EPFW the same version your running now? If so, were you seeing any problems then?...think carefully.

I've used the same version of eset nod32 on both my older OCZ SSD and my current Crucial SSD. When I replaced my OCZ SSD with the Crucial SSD I started having the netio.sys blue screens. I have never seen this blue screen prior to my changing to a Crucial SSD.

I guess all I can do is wait a few days and see if I experience the blue screen again. If I don't then I assume I won't be able to use nod32 on my system? That just seems strange to me...considering it worked fine when I had my OCZ SSD.

Thanks again,
Jared

 

[Bubbaleone]

I had another thought. Did you set your BIOS to AHCI mode when you installed the OCZ SSD? If, by chance, the BIOS was (and still is) in IDE mode it might be a case of the OCZ was OK with IDE, and the Crucial isn't. If that's the case, you can fix it with this:

GUIDE - Enabling AHCI mode AFTER Windows 7 Installation

 

[MaStA819]

I had another thought. Did you set your BIOS to AHCI mode when you installed the OCZ SSD? If, by chance, the BIOS was (and still is) in IDE mode it might be a case of the OCZ was OK with IDE, and the Crucial isn't. If that's the case, you can fix it with this:

GUIDE - Enabling AHCI mode AFTER Windows 7 Installation

I've been using AHCI since building this computer and it is still enabled in the BIOS.

Another thing just came to mind...I believe I upgraded to the 2303 BIOS around the time of going to the new SSD. I wonder if that is causing this...seems like a PITA to revert back to a previous BIOS on these boards.

Thank you very much for your time and input,
Jared

 

[MaStA819]

So far so good without nod32. Thanks again Bubbaleone.