BSoD in Windows 7

So I just got a new Sony laptop with Windows 7 a few days ago but I keep getting blue screens everyday despite having updated all of my drivers including the one included in the report. I havent had a single BSOD using WinXP for 4 years... This is pissing me off...anyone know why this is happening? I used whocrashed to get the reports.

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 1/7/2010 11:23:36 PM your computer crashed
This was likely caused by the following module: netw5s64.sys
Bugcheck code: 0xC2 (0x7, 0x1097, 0xA08002B0, 0xFFFFF88007B18090)
Error: BAD_POOL_CALLER
Dump file: C:\Windows\Minidump\010710-23212-01.dmp
file path: C:\Windows\system32\drivers\netw5s64.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver



On Thu 1/7/2010 5:15:17 PM your computer crashed
This was likely caused by the following module: netw5s64.sys
Bugcheck code: 0xC2 (0x7, 0x1097, 0x406001F, 0xFFFFFA8009287720)
Error: BAD_POOL_CALLER
Dump file: C:\Windows\Minidump\010710-22495-01.dmp
file path: C:\Windows\system32\drivers\netw5s64.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver



On Wed 1/6/2010 9:47:15 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC2 (0x7, 0x1097, 0x40D0001, 0xFFFFFA80093FB880)
Error: BAD_POOL_CALLER
Dump file: C:\Windows\Minidump\010610-20217-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Wed 1/6/2010 4:12:50 AM your computer crashed
This was likely caused by the following module: netw5v64.sys
Bugcheck code: 0xC2 (0x7, 0x1097, 0x210008, 0xFFFFFA8007082E00)
Error: BAD_POOL_CALLER
Dump file: C:\Windows\Minidump\010510-23509-01.dmp
file path: C:\Windows\system32\drivers\netw5v64.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver



On Tue 1/5/2010 3:57:03 AM your computer crashed
This was likely caused by the following module: nwifi.sys
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800033E2477)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\010410-35693-01.dmp
file path: C:\Windows\system32\drivers\nwifi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NativeWiFi Miniport Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.


I also ran tests using malwarebytes and SuperAntispyware and they came up with nothing.

 

Looks like a bad wifi driver.
Maybe need to use Sony's wifi driver for Win7, if they have one for your laptop.

That or roll back the wifi driver. If you updated the driver via Windows Update then that may be the problem. Windows Update does not always give you the best driver to use.

If things are working ok on a system then driver updates are not always needed.

 

netw5v64.sys looks like it's the main antagonist, this is part of the Intel Wireless drivers, specifically, I think, the Novell Netware drivers. Were the wireless drivers updated from the Sony site? If so, I'd hop over to Intel and see if they have a later version, if there's one available, opt for the drivers only download.

You may also be able to trim back on the number of networking protocols used by the wireless card, how do you use the laptop?

 

I downloaded an update from the Sony site, saw that I still had problems and then downloaded an update off the Intel site which against still gave me blue screens.

All I do with the laptop is go on websites...

And I somehow managed to fry my motherboard while downloading a BIOS utility update and getting a blue screen. Absolutely fabulous...It hasnt been a week yet and I already managed to **** up a $1000 laptop

 

Now it sounds like the laptop was faulty to begin with if you "fried" your laptop just by downloading.

Not sure if exchange is an option, or at least use the warranty.

 

Well I got a replacement motherboard under warranty but surprise surprise, I'm still having problems. Am I the only one with this much trouble? And I mainly use the computer to watch shows and browse the internet so it shouldnt be that much activity...Logs from after the replacement


On Sat 1/16/2010 5:47:04 PM your computer crashed
This was likely caused by the following module: netw5s64.sys
Bugcheck code: 0xD1 (0x30, 0x2, 0x0, 0xFFFFF880057F6394)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\011610-22994-01.dmp
file path: C:\Windows\system32\drivers\netw5s64.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver



On Fri 1/15/2010 10:15:58 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800033E2477)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\011510-20560-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Thu 1/14/2010 7:14:50 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800033EE477)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\011410-42806-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Mon 1/11/2010 2:43:18 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800033E6477)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\011010-21933-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



On Mon 1/11/2010 12:01:48 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002E06477)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\011010-22292-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.

 

So can anyone help me out or even know what is causing the blue screen? I'm just reading the news, watching videos and stuff...

 

Well I followed the instructions but this is what I got.


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


Loading Dump File [C:\Windows\Minidump\012710-22198-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e57000 PsLoadedModuleList = 0xfffff800`03094e50
Debug session time: Wed Jan 27 19:09:20.729 2010 (GMT-5)
System Uptime: 0 days 2:59:09.649
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002e10477}

Unable to load image \SystemRoot\system32\DRIVERS\NETw5s64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+b76b )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002e10477, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ff0e0
0000000000000000

CURRENT_IRQL: 2

FAULTING_IP:
hal!HalpDmaNextContiguousPiece+103
fffff800`02e10477 448b08 mov r9d,dword ptr [rax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: uTorrent.exe

TRAP_FRAME: fffff88008b10c50 -- (.trap 0xfffff88008b10c50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000600
rdx=0000000000000600 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e10477 rsp=fffff88008b10de8 rbp=0000000000000000
r8=0000000000000490 r9=0000000000000000 r10=00000000000fffff
r11=fffffa8007d182b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
hal!HalpDmaNextContiguousPiece+0x103:
fffff800`02e10477 448b08 mov r9d,dword ptr [rax] ds:0001:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002ec8469 to fffff80002ec8f00

STACK_TEXT:
fffff880`08b10b08 fffff800`02ec8469 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`08b10b10 fffff800`02ec70e0 : fffffa80`05534ee0 fffffa80`09b3bd90 fffffa80`084cd870 fffff880`0490e893 : nt!KiBugCheckDispatch+0x69
fffff880`08b10c50 fffff800`02e10477 : fffffa80`057106b0 fffffa80`0661fa00 fffff800`02e10524 fffffa80`09b3bd90 : nt!KiPageFault+0x260
fffff880`08b10de8 fffff800`02e10524 : fffffa80`09b3bd90 fffffa80`07d182b0 fffffa80`0a601200 00000000`00000000 : hal!HalpDmaNextContiguousPiece+0x103
fffff880`08b10e00 fffff800`02e134fb : fffffa80`09b3bd90 fffffa80`07d182b0 fffffa80`057106b0 fffffa80`0670efd8 : hal!HalpDmaMapScatterTransfer+0x34
fffff880`08b10e50 fffff800`02e13472 : fffffa80`09b3bd90 fffffa80`09b3bd88 00000000`00000490 00000000`00000000 : hal!HalpMapTransfer+0x7b
fffff880`08b10ee0 fffff800`02e1294f : fffffa80`07da9e20 fffff800`02e1001e 00000000`00000003 00000000`00000005 : hal!IoMapTransfer+0x8e
fffff880`08b10f20 fffff800`02e12afd : fffffa80`07720050 fffffa80`07d182b0 00000000`00000001 fffffa80`00000000 : hal!HalpAllocateAdapterCallback+0xc7
fffff880`08b10fc0 fffff800`02e13156 : fffffa80`07d182b0 00000000`00000000 fffffa80`07d18200 00000000`00000003 : hal!IoFreeAdapterChannel+0x109
fffff880`08b10ff0 fffff800`02e1271f : fffffa80`08aa6010 00000000`0000005c fffffa80`07d182b0 fffffa80`05db5220 : hal!HalAllocateAdapterChannel+0x11a
fffff880`08b11030 fffff880`016a57c0 : fffffa80`0a549d50 fffffa80`07d18130 fffffa80`000000a0 fffff880`04b08c40 : hal!HalBuildScatterGatherList+0x2f3
fffff880`08b110a0 fffff880`048c476b : fffffa80`077201a0 00000000`00000000 fffffa80`08bb2dc0 fffff880`04a69aa0 : ndis!NdisMAllocateNetBufferSGList+0x110
fffff880`08b11140 fffffa80`077201a0 : 00000000`00000000 fffffa80`08bb2dc0 fffff880`04a69aa0 00000000`00000000 : NETw5s64+0xb76b
fffff880`08b11148 00000000`00000000 : fffffa80`08bb2dc0 fffff880`04a69aa0 00000000`00000000 0000005c`00000100 : 0xfffffa80`077201a0


STACK_COMMAND: kb

FOLLOWUP_IP:
NETw5s64+b76b
fffff880`048c476b ?? ???

SYMBOL_STACK_INDEX: c

SYMBOL_NAME: NETw5s64+b76b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETw5s64

IMAGE_NAME: NETw5s64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4aafedb7

FAILURE_BUCKET_ID: X64_0xA_NETw5s64+b76b

BUCKET_ID: X64_0xA_NETw5s64+b76b

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



I guess it has something to do with uTorrent making NETw5s64 (the WiFi) mess up even though I already updated the drivers to the latest one? I'm not really sure how to interpret this mess...