Last week I started getting BSOD when uploading images to eBay. It happened maybe six or seven separate times. I disabled Avast web protection and the problem stopped.
Windows 7 x64.
What exact version of avast are you using?
What is the exact error on the bsod ?
I don’t know if the version # is the one I was using last week because I started to upgrade Avast yesterday when I got a notice to do so, but then cancelled out before the download completed, and yet Avast is still telling me I need to reboot my computer as if an update went forward, despite my having clicked the Cancel button. Here is the #:
2014.9.0.2013
The error was in NETIO.SYS.
2014.9.0.2013 is the latest version, cancelling the update mid process may have screwed up your system so if it were me I would be doing a clean install.
If you get problems with ebay after a new install try disabling Browser Protection - AOS ( Avast Online Security ) by right clicking the toolbar of your browser and untick the feature.
I just downloaded the WhoCrashed program and it analyzed 5 dumps; they all say the same thing; here’s one of them:
computer name: ASUS1
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., P8H67-I DELUXE
CPU: GenuineIntel Intel(R) Core™ i5-2500 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8495742976 total
VM: 2147352576, free: 1924976640
Crash Dump Analysis
Crash dump directory: h:\Minidump
Crash dumps are enabled on your computer.
On Sat 1/25/2014 3:45:53 PM GMT your computer crashed
crash dump file: h:\Minidump\012514-15132-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF88001797A1D)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001797A1D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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’ll report this to one of the specialists as it appears to be either a ram problem or one of you system drivers are corrupted.
Have you recently updated any drivers ? Could you upload all the minidumps to a file sharing site for me to look at