Jump to content

How to fix netio.sys BSOD issue?


Recommended Posts

Guest AlexDominik
Posted

Hi everyone, i searched on the web but i didn't find anything that could help me.

 

This is my situation.

 

 

I have this configuration:

 

 

-OS: Win 7 64 Bit Professional

 

-MB: Asus P8P67 DELUXE

 

-GPU: Nvidia GTX 750Ti (bought 1 months ago because my old gpu gave me lots of freezes and didn't reconize the monitor)

 

-CPU: Intel i7 2700K

 

-RAM. 12 gb Kingston (can't remember the name)

 

 

 

So, i had random freezes issues months ago, i brought the pc to the assistance and they changed my GPU because they told that it was broken.

 

New GPU, seems ok. Yesterday the pc freezes when i was simply browsing (i played 3-4 hours but it freezed when i was browsing).

 

 

Whocrashed gave me this dump analisys:

 

 

 

Crash dump file: C:\Windows\Minidump\062714-8970-01.dmp

Date/time: 27/06/2014 01:08:59 GMT

Uptime: 06:45:28

Machine: ALEX-SAN-PC

Bug check name: KMODE_EXCEPTION_NOT_HANDLED

Bug check code: 0x1E

Bug check parm 1: 0x0

Bug check parm 2: 0x0

Bug check parm 3: 0x0

Bug check parm 4: 0x0

Probably caused by: netio.sys

Driver description: Network I/O Subsystem

Driver product: Microsoft® Windows® Operating System

Driver company: Microsoft Corporation

OS build: Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144

Architecture: x64 (64 bit)

CPU count: 8

Page size: 4096

 

Bug check description:

This indicates that a kernel-mode program generated an exception which the error handler did not catch.

 

Comments:

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

 

 

Crash dump file: C:\Windows\memory.dmp

Date/time: 27/06/2014 01:08:59 GMT

Uptime: 06:45:28

Machine: ALEX-SAN-PC

Bug check name: KMODE_EXCEPTION_NOT_HANDLED

Bug check code: 0x1E

Bug check parm 1: 0x0

Bug check parm 2: 0x0

Bug check parm 3: 0x0

Bug check parm 4: 0x0

Probably caused by: netio.sys

Driver description: Network I/O Subsystem

Driver product: Microsoft® Windows® Operating System

Driver company: Microsoft Corporation

OS build: Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144

Architecture: x64 (64 bit)

CPU count: 8

Page size: 4096

 

Bug check description:

This indicates that a kernel-mode program generated an exception which the error handler did not catch.

 

Comments:

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

 

I also had this some days ago:

 

 

Crash dump file: C:\Windows\Minidump\062214-12027-01.dmp

Date/time: 22/06/2014 16:42:34 GMT

Uptime: 00:34:00

Machine: ALEX-SAN-PC

Bug check name: BAD_POOL_HEADER

Bug check code: 0x19

Bug check parm 1: 0x20

Bug check parm 2: 0xFFFFF8A003EEA580

Bug check parm 3: 0xFFFFF8A003EEA7E0

Bug check parm 4: 0x5260358

Probably caused by: dxgkrnl.sys

Driver description: DirectX Graphics Kernel

Driver product: Microsoft® Windows® Operating System

Driver company: Microsoft Corporation

OS build: Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144

Architecture: x64 (64 bit)

CPU count: 8

Page size: 4096

 

Bug check description:

This indicates that a pool header is corrupt.

 

Comments:

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

This is the analisys of the same two errors but given by bluescreenviewer:

 

 

2a5d72a4fe81a370f8cb233e71ace4e4._.jpg.d92ad2305e588c8256ac01bd9c535b81.jpg

 

7825e1feaa5f4befc0e74e575c037787._.jpg.cd8701d9d7acd4bf1bc6792ca894d712.jpg

 

 

I'm now going to start a memstest just to be sure.

 

 

Thank you in advance for the help.

 

Continue reading...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...