Bluescreen after second Standby

[Captain-DJ]

Hello! GB-PVR runs on an Notebook. The first standby is ok, it wakes up, no problem. The second standby crach with an bluescreen stop =x00000000A (0xBAD0B214, 0X000000FF, 0X0000000000, 0x844E35E9) NDIS.SYS I think its an problem with the "Virtual Network Adapter" from GB-PVR. Wenn its disabled standby will work.

Anyone can help me?

[Captain-DJ]

No one can help me ???

I used the WinDGB Tool from Microsoft.
This analyze says its an Problem with the "Virtual Net Adaptor"

This is an part of GBPVR ?!?!
Also starting takes a long time since gbpvr is installed...is that normal ??

The Log of the Windgb Tool:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 1, f839f5b2}

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

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: f839f5b2, address which referenced memory

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


WRITE_ADDRESS:  00000000

CURRENT_IRQL:  2

FAULTING_IP:
NDIS!NdisMDeregisterDevice+2f
f839f5b2 890f            mov     dword ptr [edi],ecx

CUSTOMER_CRASH_COUNT:  5

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  f861435c -- (.trap fffffffff861435c)
ErrCode = 00000002
eax=00000000 ebx=f83a1138 ecx=00000000 edx=00000000 esi=820acda0 edi=00000000
eip=f839f5b2 esp=f86143d0 ebp=f86143dc iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
NDIS!NdisMDeregisterDevice+0x2f:
f839f5b2 890f            mov     dword ptr [edi],ecx  ds:0023:00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from f839f5b2 to 804e187f

STACK_TEXT:  
f861435c f839f5b2 badb0d00 00000000 00000000 nt!KiTrap0E+0x233
f86143dc f88c6771 000000ac 81d04830 003bdb21 NDIS!NdisMDeregisterDevice+0x2f
WARNING: Stack unwind information not available. Following frames may be wrong.
f86143f0 f83ad06e 81cd1008 f83a1138 81d04830 VirtualNet+0x1771
f861442c f83ae67a 00000000 806ee720 81d04830 NDIS!ndisMCommonHaltMiniport+0x362
f8614444 f83af58a 8055ff68 8218109c 82181008 NDIS!ndisPmHaltMiniport+0x90
f8614470 f83af902 82181008 8218109c 81d04830 NDIS!ndisSetPower+0x277
f8614490 804e37f7 823b1730 82181008 8218109c NDIS!ndisPowerDispatch+0x8b
f86144a0 805081dc 8218109c 82181008 00000000 nt!IopfCallDriver+0x31
f86144b4 80507adf 8218109c 82181008 821810c0 nt!PopPresentIrp+0x57
f86144d4 80507cb0 81d04730 81d04d30 00000000 nt!PoCallDriver+0x195
f86144f0 f83af7a7 823b1730 00000002 00000004 nt!PoRequestPowerIrp+0x129
f8614534 f83af902 821a6008 821a609c 00000004 NDIS!ndisSetPower+0x494
f8614554 804e37f7 823b1730 821a6008 821a609c NDIS!ndisPowerDispatch+0x8b
f8614564 805081dc 821a609c 821a6008 00000000 nt!IopfCallDriver+0x31
f8614578 80507adf 821a609c 821a6008 8205e9e0 nt!PopPresentIrp+0x57
f8614598 8066675d 81d04730 81d04d30 8205ec04 nt!PoCallDriver+0x195
f86145b8 80666823 805583dc 81cd91b8 00000007 nt!PopNotifyDevice+0x1ac
f86145d4 80666afe 8205e9e0 8205ec04 00000000 nt!PopSleepDeviceList+0xb5
f86145fc 8066595a 00000000 f86146e4 f8614768 nt!PopSetDevicesSystemState+0x1a4
f86146d0 804de7ec 00000002 00000005 00000003 nt!NtSetSystemPowerState+0x426
f86146d0 804dd9a1 00000002 00000005 00000003 nt!KiFastCallEntry+0xf8
f8614754 8066558c 00000002 00000005 00000003 nt!ZwSetSystemPowerState+0x11
f8614830 804de7ec 00000002 00000005 00000003 nt!NtSetSystemPowerState+0x65
f8614830 7c91eb94 00000002 00000005 00000003 nt!KiFastCallEntry+0xf8
0006f2a0 00000000 00000000 00000000 00000000 0x7c91eb94


STACK_COMMAND:  kb

FOLLOWUP_IP:
VirtualNet+1771
f88c6771 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  VirtualNet+1771

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: VirtualNet

IMAGE_NAME:  VirtualNet.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  438563dd

FAILURE_BUCKET_ID:  0xD1_W_VirtualNet+1771

BUCKET_ID:  0xD1_W_VirtualNet+1771

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

[sub]

I used the WinDGB Tool from Microsoft.
This analyze says its an Problem with the "Virtual Net Adaptor"

This is an part of GBPVR ?!?!

No its not.

From the stack trace, it looks like you network adapter is having problems when being informed by Windows of the change in power state. So, sounds like buggy drivers for your network adapter.

[Captain-DJ]

Oh...sorry !

Its from my DVB Software...i try to disable this.

Thanks !