BSOD maby 3 times a day. Comes usually when installing or in internet

[Kampiakseli]

So, hello (again)
I have BSOD sometimes even 3 times a day. Im going insane because my PC
BSOD comes always when gaming, installing or when Im just in internet. I dont have any idea what would cause the BSODs so, please help me.

 

[Dinesh]

Hi and welcome to the forums.

It seems Avast anti virus is causing BSODs for you.
Uninstall Avast anti virus completely using the Avast! Removal Tool and then restart the computer.

We recommend using Microsoft Security Essentials - Microsoft Windows along with Malware Bytes.

Also, run System File Checker to verify/repair the integrity of system files.
Full tutorial here: http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Let us know if this works.

The below is for information purpose only:

BugCheck Analysis:

Probably caused by : NETIO.SYS ( NETIO+3ffb )

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

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

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 00000000, A single DPC or ISR exceeded its time allotment. The offending
	component can usually be identified with a stack trace.
Arg2: 00000281, The DPC time count (in ticks).
Arg3: 00000280, The DPC time allotment (in ticks).
Arg4: 00000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:  
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

MODULE_NAME: NETIO

FAULTING_MODULE: 81a6d000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  505aa973

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x133

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 81baf2cd to 81b24218

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
818e48f4 81baf2cd 00000133 00000000 00000281 nt+0xb7218
818e4964 81ad792a 03a92854 03a92855 022e9602 nt+0x1422cd
818e49d0 81a34ffe 818e49e8 81a93505 818e4adc nt+0x6a92a
818e49f0 81a4660d 818e4b02 000000d1 818e4b00 hal+0x1cffe
818e4a00 81a93505 badb0d00 818e4adc 006dfa97 hal+0x2e60d
818e4b00 826e1ffb 00000014 818e4fac 818e4fd0 nt+0x26505
818e4bd8 826e0801 00000014 818e4fac 818e4fd0 NETIO+0x3ffb
818e4e08 827142c6 00000014 818e4fac 818e4fd0 NETIO+0x2801
818e4eac 827107d7 0012ffa9 00000014 818e4fac NETIO+0x362c6
818e4f78 827104a3 00000014 818e4fac 818e4fd0 NETIO+0x327d7
818e51d0 8270fcb1 875d6ca8 00000014 818e51fc NETIO+0x324a3
818e5200 822e5182 875d6ca8 00000014 818e53b8 NETIO+0x31cb1
818e521c 8229a1f1 88dd7df8 818e54d0 85cd1480 tcpip+0xab182
818e538c 822851d7 85d27430 818e53f8 85cd1480 tcpip+0x601f1
818e5440 82279984 88dd7df8 818e54d0 00000000 tcpip+0x4b1d7
818e54c4 8228573b 85d27430 85d57000 00000000 tcpip+0x3f984
818e554c 82295b1b 85d27430 85d57000 00000001 tcpip+0x4b73b
818e5574 822b7462 818e5584 8237bfc8 85d27430 tcpip+0x5bb1b
818e55a0 822b70d0 00000006 00000000 8237bfc8 tcpip+0x7d462
818e55dc 822b6bc9 8237bfc8 818e563c 818e5634 tcpip+0x7d0d0
818e5668 822b5dc9 8237bfc8 818e56c8 00000000 tcpip+0x7cbc9
818e5764 822beb83 84a43360 86e88190 00000001 tcpip+0x7bdc9
818e57bc 822bed5e beca33f8 00000000 822bed8e tcpip+0x84b83
818e57ec 81a7e536 86e88190 8e3eb7f0 00000000 tcpip+0x84d5e
818e5864 81a7e195 822becf0 818e58ac 00002400 nt+0x11536
818e5884 822beec2 822becf0 818e58ac 00002400 nt+0x11195
818e58c4 8260ee6f 02ca33f8 86e88100 00000000 tcpip+0x84ec2
818e58c8 02ca33f8 86e88100 00000000 00000001 ndis+0x2e6f
818e58cc 86e88100 00000000 00000001 00000000 0x2ca33f8
818e58d0 00000000 00000001 00000000 849b21b4 0x86e88100


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO+3ffb
826e1ffb ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  NETIO+3ffb

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  NETIO.SYS

BUCKET_ID:  WRONG_SYMBOLS

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

 

[Kampiakseli]

If I remeber right. I uninstalled Avast right when I noticed it. Well, I'll give it a try

 

[Kampiakseli]

If I remeber right. I uninstalled Avast right when I noticed it. Well, I'll give it a try

Nope. It didn't work, because Avast was removed and so was the folder too. So yeah.