Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD whilst computer is idle.


  • Please log in to reply
1 reply to this topic

#1 Alachas

Alachas

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:04:09 PM

Posted 19 August 2009 - 06:29 AM

Hi everyone,

I few months ago I bought myself a new PC running Vista Home Premium 64-bit and havn't had any issues with it, until now.

Starting from two days ago, my PC has been getting the BSOD and shutting itself down everytime I leave it idle for a few hours (when I go bed and again when I go to work). It has not yet happened when I've been using it (that is probably just coincidence), so I haven't been able to see what the BSOD says.

I'd also like to point out that I didn't make any changes to my system that could have caused the error, it just came out of the blue... so to speak.

In the "Problem Reports and Solutions" window from the Control Panel, it gives the following info:

[codebox]Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 3081

Files that help describe the problem (some files may no longer be available)
Mini081909-02.dmp
sysdata.xml
Version.txt

View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Extra information about the problem
BCCode: d1
BCP1: 00000000E72B3F6B
BCP2: 0000000000000002
BCP3: 0000000000000008
BCP4: 00000000E72B3F6B
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1
Server information: 4d7148b5-eb16-4f3a-942b-c99ee94d217f
[/codebox]

The mini-dump file contains the following:

[codebox]
Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Home\Desktop\Mini081909-02.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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18226.amd64fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0xfffff800`02002000 PsLoadedModuleList = 0xfffff800`021c7db0
Debug session time: Wed Aug 19 14:03:24.889 2009 (GMT+10)
System Uptime: 0 days 10:38:17.927
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {e72b3f6b, 2, 8, e72b3f6b}

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

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

2: 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: 00000000e72b3f6b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 00000000e72b3f6b, address which referenced memory

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


AUTOBUG_USER_LCID_STR: ENU

AUTOBUG_OS_SKU: 3

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000222b080
00000000e72b3f6b

CURRENT_IRQL: 2

FAULTING_IP:
+0
00000000`e72b3f6b ?? ???

PROCESS_NAME: System

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

TRAP_FRAME: fffffa6001b8c7f0 -- (.trap 0xfffffa6001b8c7f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000e72b3f6b rbx=0000000000000000 rcx=000000000000edf0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=00000000e72b3f6b rsp=fffffa6001b8c988 rbp=fffffa600135c220
r8=0000000000000000 r9=500105206e000000 r10=500105206f6f0001
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
00000000`e72b3f6b ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800020563ee to fffff80002056650

FAILED_INSTRUCTION_ADDRESS:
+0
00000000`e72b3f6b ?? ???

STACK_TEXT:
fffffa60`01b8c6a8 fffff800`020563ee : 00000000`0000000a 00000000`e72b3f6b 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffffa60`01b8c6b0 fffff800`020552cb : 00000000`00000008 00000000`00000018 fffffa60`01b8ca00 fffffa80`0aa79a20 : nt!KiBugCheckDispatch+0x6e
fffffa60`01b8c7f0 00000000`e72b3f6b : fffffa60`01261d86 fffffa80`06a05f00 00000000`00000000 fffffa60`01b8cc88 : nt!KiPageFault+0x20b
fffffa60`01b8c988 fffffa60`01261d86 : fffffa80`06a05f00 00000000`00000000 fffffa60`01b8cc88 00000000`00000001 : 0xe72b3f6b
fffffa60`01b8c990 fffffa60`0127eb8b : fffffa80`0aa79a20 fffffa80`06a0b000 fffffa80`0690cec0 fffffa60`01b8ca70 : tcpip!TcpCleanupTcbWorkQueueRoutine+0xd6
fffffa60`01b8c9d0 fffffa60`0127f91f : fffffa80`06a05f00 00000000`42526301 fffffa80`06a0b000 00000000`00000000 : tcpip!TcpTcbReceive+0x6db
fffffa60`01b8cb80 fffffa60`01278fd7 : fffffa60`02ad0662 00000000`00000000 fffffa80`06a0b000 fffffa80`06a000fa : tcpip!TcpMatchReceive+0x19f
fffffa60`01b8cc80 fffffa60`0125723d : fffffa80`06a0b000 00000000`00da7a64 fffffa80`06a05f00 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x377
fffffa60`01b8cd10 fffffa60`0126241d : fffffa80`06a0ae30 fffffa60`01349f20 fffffa60`01b8ced0 00000000`00000000 : tcpip!TcpNlClientReceiveDatagrams+0x6d
fffffa60`01b8cd40 fffffa60`0125b009 : 00000000`00000000 fffffa80`0a3bf1a0 fffffa80`097e1540 fffffa60`01349f20 : tcpip!IppDeliverListToProtocol+0x4d
fffffa60`01b8ce00 fffffa60`0125a69e : fffffa60`01349f20 fffffa60`02ad065a 00000000`00000000 fffffa60`01b8cec0 : tcpip!IppProcessDeliverList+0x59
fffffa60`01b8ce70 fffffa60`012662e6 : 00000000`00000000 fffffa80`06a0b000 fffffa80`08678080 00000000`0000000e : tcpip!IppReceiveHeaderBatch+0x23e
fffffa60`01b8cf60 fffffa60`01265875 : fffffa80`09831d60 00000000`00000000 00000000`00000001 00000000`00000001 : tcpip!IpFlcReceivePackets+0x8d6
fffffa60`01b8d140 fffffa60`0127e3b3 : fffffa80`097e1540 fffffa60`01b8d278 fffffa80`097e1540 fffffa60`01170000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x265
fffffa60`01b8d220 fffffa60`011a833c : fffffa80`0981c300 fffffa80`093c1e40 fffffa60`01b8d300 fffffa80`08aa31a0 : tcpip!FlReceiveNetBufferListChain+0xd3
fffffa60`01b8d270 fffffa60`01171266 : fffffa60`01b8d3d0 fffffa60`01b8d3e0 00000000`00000001 00000000`00000001 : ndis!ndisMIndicateNetBufferListsToOpen+0xac
fffffa60`01b8d2c0 fffffa60`010187c4 : fffffa80`08aa31a0 00000000`00000002 00000000`00000001 fffffa60`01b8d778 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
fffffa60`01b8d740 fffffa60`010187ed : d0558eaa`483f6878 e653fa00`5bc09266 00000000`00000000 00000000`0a010102 : ndis!ndisMTopReceiveNetBufferLists+0x24
fffffa60`01b8d780 fffffa60`01018786 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`093c1e40 : ndis!ndisFilterIndicateReceiveNetBufferLists+0x1d
fffffa60`01b8d7c0 fffffa60`04c655ff : 00000000`00000000 fffffa80`097b7210 00000000`00000001 fffffa60`04c6426f : ndis!NdisFIndicateReceiveNetBufferLists+0x16
fffffa60`01b8d800 00000000`00000000 : fffffa80`097b7210 00000000`00000001 fffffa60`04c6426f fffffa80`00000001 : avgfwd6a+0x35ff


STACK_COMMAND: kb

FOLLOWUP_IP:
avgfwd6a+35ff
fffffa60`04c655ff ?? ???

SYMBOL_STACK_INDEX: 14

SYMBOL_NAME: avgfwd6a+35ff

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: avgfwd6a

IMAGE_NAME: avgfwd6a.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49b7f384

FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_avgfwd6a+35ff

BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_avgfwd6a+35ff

Followup: MachineOwner
---------
[/codebox]

I'm using a legitimate copy of AVG and haven't had any issues with it until now (presuming that the "avgfwd6a.sys" mentioned in the mini-dump is related and not just a coincidence in naming).

Hopefully one of you can help me with this problem; it drives me crazy when I have PC issues that I can't solve myself.

Thanks in advance,

Alachas

BC AdBot (Login to Remove)

 


#2 Alachas

Alachas
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:04:09 PM

Posted 20 August 2009 - 04:24 PM

it drives me crazy when I have PC issues that I can't solve myself.

Well, turns out I could solve this one myself =P

I did a re-install of AVG and this morning the computer was still running; no BSOD.

Hopefully, this has solved the problem for good.

Cheers,

Alachas




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users