BSOD out of Standby mode

Blue Screen of Death (BSOD) Posting Instructions

PTwake04 said:

ok here we go. I did the perform scan and it is in the zipped folder. It is reporting an error "tv_ConfigMgrErr21".

I am running a full retailed version of Windows 7 home premium x64. I am also using this home built computer as an HTPC. I currently have it hooked up to my LG 55" TV.

Hello,
Several .dmp files point to NETIO.SYS as the cause so I suggest you perform System File Checker:
Right click CMD → run as administrator → sfc /scannow

For troubleshooting purpose, uninstall Norton Symantec AV and replace it with MSE.
http://www.microsoft.com/security_essentials/

Then install this hotfix.

Update these drivers:

Code:

atikmdag.sys Wed Jul 29 23:07:18 2009 → ATI video driver
Rt64win7.sys Thu Jul 30 04:58:43 2009 → Realtek NIC driver
RtHDMIVX.sys Thu Jul 16 20:52:36 2009 → ATI HDMI Audio Device

Code:

Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e65000 PsLoadedModuleList = 0xfffff800`030a2e50
Debug session time: Wed Jan  5 17:44:53.727 2011 (GMT-8)
System Uptime: 0 days 9:27:27.991
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 44, {fffffa800b1ef650, eae, 0, 0}

Probably caused by : NETIO.SYS ( NETIO!NetiopIoWorkItemRoutine+3b )

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

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

MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed.  This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened.  Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it.  The
first actually works, and the second fails.  Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second.  However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: fffffa800b1ef650, Address of the IRP
Arg2: 0000000000000eae
Arg3: 0000000000000000
Arg4: 0000000000000000

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


IRP_ADDRESS:  fffffa800b1ef650

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x44

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ebf365 to fffff80002ed5740

STACK_TEXT:  
fffff880`0335ba78 fffff800`02ebf365 : 00000000`00000044 fffffa80`0b1ef650 00000000`00000eae 00000000`00000000 : nt!KeBugCheckEx
fffff880`0335ba80 fffff880`048ef37b : fffff800`0307a5f8 fffffa80`08129c70 00000000`00000000 fffffa80`0762c680 : nt! ?? ::FNODOBFM::`string'+0x3ec7e
fffff880`0335bb60 fffff880`0492709b : 00000000`08400000 fffffa80`08129be0 00000000`00000000 00000000`00000000 : afd!WskProTLCloseEndpointComplete+0x2b
fffff880`0335bba0 fffff880`0170099b : fffff880`04909880 fffff800`0307a5f8 fffff880`04909880 00000000`00000000 : afd!WskTdiWQRoutineEndpointClose+0x13b
fffff880`0335bc30 fffff800`031d1c5d : fffffa80`09d29e40 fffffa80`0762c680 00000000`00000000 fffffa80`0762c680 : NETIO!NetiopIoWorkItemRoutine+0x3b
fffff880`0335bc80 fffff800`02ee2961 : fffff800`031c8800 fffff800`031c88dc fffffa80`0762c680 00000000`00000000 : nt!IopProcessWorkItem+0x3d
fffff880`0335bcb0 fffff800`03179c06 : 00540041`00540053 fffffa80`0762c680 00000000`00000080 fffffa80`075b5840 : nt!ExpWorkerThread+0x111
fffff880`0335bd40 fffff800`02eb3c26 : fffff880`03171180 fffffa80`0762c680 fffff880`0317c0c0 00000000`00000020 : nt!PspSystemThreadStartup+0x5a
fffff880`0335bd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!NetiopIoWorkItemRoutine+3b
fffff880`0170099b 488d542420      lea     rdx,[rsp+20h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  NETIO!NetiopIoWorkItemRoutine+3b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc18a

FAILURE_BUCKET_ID:  X64_0x44_NETIO!NetiopIoWorkItemRoutine+3b

BUCKET_ID:  X64_0x44_NETIO!NetiopIoWorkItemRoutine+3b

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

PTwake04 said:

I have not ran the system file check yet. But i did update the three listed drivers yesterday, and when my computer woke up this morning from sleep mode the BSOD was there.

I will do the system file check today.

do you have any other suggestions?

Have you installed the hotfix above?

Good troubleshooting and keep us posting