BSOD and my minidumps.

I have a new Asus G73H laptop, and lately I have been getting BSOD's..

I'm including my .dmp's so hopefully someone smarter than me can at least tell me maybe what's going on.

Any help would be greatly appreciated...

Welcome!

I guess your attachments didn't come out. If you have the files zipped up, you can upload the zip folder to this site by clicking the paperclip icon over your next post.

All of them look like your network driver netw5s64.sys is causing the issue.

I recommend updating your network drivers from Device Manager.

Code:

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


Loading Dump File [C:\Users\Jonathan\Desktop\dumps\031110-12261-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e0a000 PsLoadedModuleList = 0xfffff800`03047e50
Debug session time: Thu Mar 11 00:39:46.253 2010 (GMT-4)
System Uptime: 3 days 6:35:23.281
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8007ba8060, fffff80000b9c518, fffffa8008dbac10}

*** 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

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8007ba8060, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8008dbac10, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa8008dbac10

DEVICE_OBJECT: fffffa8008dc9050

DRIVER_OBJECT: fffffa8008fca440

IMAGE_NAME:  NETw5s64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b4df6b9

MODULE_NAME: NETw5s64

FAULTING_MODULE: fffff88005608000 NETw5s64

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002eeae23 to fffff80002e7bf00

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02eeae23 : 00000000`0000009f 00000000`00000003 fffffa80`07ba8060 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02e87fa6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330
fffff800`00b9c570 fffff800`02e87326 : fffffa80`06d36148 fffffa80`06d36148 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02e87e7e : 00000292`bb6ab1b5 fffff800`00b9cc58 00000000`0114bbb7 fffff800`02ff8968 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02e87697 : 0000006d`e03ef0c3 0000006d`0114bbb7 0000006d`e03ef04d 00000000`000000b7 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02e846fa : fffff800`02ff4e80 fffff800`03002c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_NETw5s64.sys

BUCKET_ID:  X64_0x9F_IMAGE_NETw5s64.sys

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