BSOD and system freezes at random times even after format

[plasid93]

Good day SevenForums community.

My laptop has been freezing a lot since yesterday, at seemingly the most random times. The only way to solve this is to hard reset it, holding in the power button for a couple of seconds.
It has also gotten BSOD four times.

I formatted my laptop on Sunday the 7th of October, hardly a week ago. I used the official Win7 Reinstall CD (provided with my lapptop when I purchased it). I also installed the necessary drivers and utilities (also from a cd that came with the laptop).

On Monday or Tuesday I got a random BSOD. I though it was really weird that am getting it after a format and fresh install.
On Thursday the 11th of October (yesterday) my laptop started freezing much more and got the BSOD on every couple of hard restarts.

I installed Avast 5 Free Antivirus since I can't afford premium antivirus at the moment (I used to have Kaspersky, but the licence expired).
Yesterday I installed AVG Free Antivirus Trial because I though it was better.

I am not sure what more information I have to provide. The my dump files are attached.

 

[tom982]

Hello plasid93 and welcome to the forums

Have you got a USB WiFi device plugged in by any chance? If so, could you update the drivers please?

Tom

 

[plasid93]

Thank you happy to be here...well not really because it's problems that sent me.

I am using a USB 3G Stick to connect to the internet. I updated all relevant drivers, but it still froze just now.
I used tethering from my phone yesterday to connect the laptop to the internet, and everything went smoothly. I didn't use it a lot by the way, so I'm still trying to figure out if a certain web page causes this.

 

[tom982]

Hi plasid93,

lol, well I'll try my best to deal with you quickly then.

Here is the output from when I ran your dump:

Microsoft (R) Windows Debugger Version 6.2.8400.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Tom\AppData\Local\Temp\Temp2_plasid93.zip\plasid93\101212-37689-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c55000 PsLoadedModuleList = 0xfffff800`02e92e50
Debug session time: Fri Oct 12 12:35:35.096 2012 (UTC + 1:00)
System Uptime: 0 days 0:02:42.782
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
......
*** WARNING: Unable to verify timestamp for ewusbnet.sys
*** ERROR: Module load completed but symbols could not be loaded for ewusbnet.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88005b5c9e4, fffff880041fd8b8, fffff880041fd110}

Probably caused by : ewusbnet.sys ( ewusbnet+29e4 )

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: fffff88005b5c9e4, The address that the exception occurred at
Arg3: fffff880041fd8b8, Exception Record Address
Arg4: fffff880041fd110, Context Record Address

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


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

FAULTING_IP: 
ewusbnet+29e4
fffff880`05b5c9e4 f6410a05        test    byte ptr [rcx+0Ah],5

EXCEPTION_RECORD:  fffff880041fd8b8 -- (.exr 0xfffff880041fd8b8)
ExceptionAddress: fffff88005b5c9e4 (ewusbnet+0x00000000000029e4)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 000000000000020a
Attempt to read from address 000000000000020a

CONTEXT:  fffff880041fd110 -- (.cxr 0xfffff880041fd110)
rax=00000000000005ea rbx=fffffa8002692f01 rcx=0000000000000200
rdx=fffffa8003ff5100 rsi=fffffa8002588a30 rdi=fffffa8003ff5000
rip=fffff88005b5c9e4 rsp=fffff880041fdaf0 rbp=0000000000000000
 r8=fffffa8003ff5000  r9=0000000000000000 r10=0000000000006400
r11=0000000000000000 r12=fffffa8003ff5170 r13=00000000000005dc
r14=fffffa8002692bd0 r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
ewusbnet+0x29e4:
fffff880`05b5c9e4 f6410a05        test    byte ptr [rcx+0Ah],5 ds:002b:00000000`0000020a=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

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:  000000000000020a

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efd0e0
GetUlongFromAddress: unable to read from fffff80002efd198
 000000000000020a Nonpaged pool

FOLLOWUP_IP: 
ewusbnet+29e4
fffff880`05b5c9e4 f6410a05        test    byte ptr [rcx+0Ah],5

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88005b5c9e4

STACK_TEXT:  
fffff880`041fdaf0 00000000`00000000 : 00000000`00000000 fffffa80`03ff5000 fffffa80`02692f00 fffffa80`00000000 : ewusbnet+0x29e4


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  ewusbnet+29e4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ewusbnet

IMAGE_NAME:  ewusbnet.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bdabd9c

STACK_COMMAND:  .cxr 0xfffff880041fd110 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_ewusbnet+29e4

BUCKET_ID:  X64_0x7E_ewusbnet+29e4

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

In particular:

Probably caused by : ewusbnet.sys ( ewusbnet+29e4 )

and:

fffff880`041fdaf0 00000000`00000000 : 00000000`00000000 fffffa80`03ff5000 fffffa80`02692f00 fffffa80`00000000 : ewusbnet+0x29e4

The former is what Windbg thinks is the problem (and is usually right with third party drivers, if you ever have a Windows file in there then the chances are that Windbg is wrong. I won't go into the reasons why unless you want me to). The latter is the stack, of which there is only ewusbnet in there so I'd put a lot of money on that being the problem!

It won't be a specific web page that causes you to crash, it will just be a dodgy copy of the driver, or an incompatibility with your system. Rather than just updating it, let's uninstall it before we install the latest version, just to make sure we get all of the remnants:

Uninstall Driver

1. Click on the Start
   
   button and in the search box, type Device Manager and click on it
2. Expand the Network Adapters category by clicking on the little + sign (it might be in a USB category, I don't know)
3. Right click on your 3G USB Stick and select Uninstall
4. Reboot your computer after that finishes

Then install the latest version from wherever you got it from last time

Tom

 

[plasid93]

I can't make head or tails of that dump file, but as long as you know what's going on there I'm happy.

I did as you instructed, uninstalled and then re installed the drivers. The pc has not frozen yet, but if it does I will be sure to let you know.

 

[plasid93]

Doesn't look like that step worked. It just froze again.

 

[tom982]

Is it freezing or crashing? If it BSODs again, could you upload the dumps please?

Tom

 

[plasid93]

This time it was just a simple freeze, no BSOD yet. It has been a while since it last froze though. Next time it freezes or gives me a BSOD I will upload the fresh dump files.

 

[tom982]

Hi plasid93,

Okay, that's good to hear. Hopefully we put an end to the BSODs when we sorted out the problematic driver, but you never know. A simple freeze is much easier to troubleshoot. Try this:

How to perform a clean boot to troubleshoot a problem in Windows Vista or Windows 7

Tom

 

[plasid93]

I did that and it looks like the problem might be a thing of the past. I'll see if it gives me any more problems or freezes, but no freezes since yesterday.

Of course, I'll continue commenting on this forum if it freezes again, but for now it looks like the problem is a thing of the past.

Thanks for your help! You're doing a good job, helping people sort out the problems with their pesky pc's!

 

[tom982]

Hi plasid93,

That's great news, thanks for posting back the results. Hopefully that's the last we'll hear of this problem, but you know where to get help if it isn't.

You're most welcome for the help

Tom