Win7 64bit BSOD Report

[ChristoLombaard]

Hi,

The hardware in question is about 1 year old, custom built and has been been running on a full retail genuine, licensed and activated version of Windows 7 Home Premium 64 bit since the initial build (the first of many with the most recent build about 2 weeks old). I chose the 64bit route as I would like to be able to use more than 3GB and upgrade this in future as my needs change (I am an amateur Photographer). For the first month or so the PC was stable and then the BSOD's started. We have done several fresh rebuilds, we have checked hardware, we have ran with Windows updates enabled and disabled etc. to no avail - we still experience the same intermittent BSOD problem.

BSOD's are more frequent with cold startups. We did a test where we kept the PC on (and standby mode at night) and the PC ran fine with no problems for 4 weeks. As soon as it is switched off and cold restarts are done we get the same problems again.

The machine is currently running dual OS with Ubuntu as an alternative (Ubuntu runs fine with absolutely no problem which tells us that there is probably no hardware error ?).

See the attached System Information and BSOD and Perfmon files.

This is causing a lot of frustration as the PC was a serious financial investment for me and is now so unreliable I cannot really use it for its purpose - a supporting tool for my digital photography. We would be ever grateful if you could assist us in resolving this problem once and for all.

Kind Regards
from the "Christo Lombaard BSOD Support Team":
Christo Lombaard Snr
Chris Lombaard
Rudolph Lombaard
Ernie Bernardo

 

[zigzag3143]

Hi,

The hardware in question is about 1 year old, custom built and has been been running on a full retail genuine, licensed and activated version of Windows 7 Home Premium 64 bit since the initial build (the first of many with the most recent build about 2 weeks old). I chose the 64bit route as I would like to be able to use more than 3GB and upgrade this in future as my needs change (I am an amateur Photographer). For the first month or so the PC was stable and then the BSOD's started. We have done several fresh rebuilds, we have checked hardware, we have ran with Windows updates enabled and disabled etc. to no avail - we still experience the same intermittent BSOD problem.

BSOD's are more frequent with cold startups. We did a test where we kept the PC on (and standby mode at night) and the PC ran fine with no problems for 4 weeks. As soon as it is switched off and cold restarts are done we get the same problems again.

The machine is currently running dual OS with Ubuntu as an alternative (Ubuntu runs fine with absolutely no problem which tells us that there is probably no hardware error ?).

See the attached System Information and BSOD and Perfmon files.

This is causing a lot of frustration as the PC was a serious financial investment for me and is now so unreliable I cannot really use it for its purpose - a supporting tool for my digital photography. We would be ever grateful if you could assist us in resolving this problem once and for all.

Kind Regards
from the "Christo Lombaard BSOD Support Team":
Christo Lombaard Snr
Chris Lombaard
Rudolph Lombaard
Ernie Bernardo

Easy, your AVG caused these. Remove and replace with Microsoft Security essentials

AVG - Download tools

http://www.microsoft.com/security_essentials/

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\051311-18595-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;srv*e:\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 Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c5f000 PsLoadedModuleList = 0xfffff800`02e9ce50
Debug session time: Fri May 13 13:23:02.630 2011 (GMT-4)
System Uptime: 0 days 0:00:07.550
Loading Kernel Symbols
...............................................................
............
Loading User Symbols
Unable to load image \SystemRoot\System32\Drivers\avgldx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgldx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgldx64.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88003d028b0, fffff880009a8bf8, fffff880009a8450}

Probably caused by : avgldx64.sys ( avgldx64+78b0 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88003d028b0, The address that the exception occurred at
Arg3: fffff880009a8bf8, Exception Record Address
Arg4: fffff880009a8450, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
avgldx64+78b0
fffff880`03d028b0 458b442404      mov     r8d,dword ptr [r12+4]

EXCEPTION_RECORD:  fffff880009a8bf8 -- (.exr 0xfffff880009a8bf8)
ExceptionAddress: fffff88003d028b0 (avgldx64+0x00000000000078b0)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000089b000c
Attempt to read from address 00000000089b000c

CONTEXT:  fffff880009a8450 -- (.cxr 0xfffff880009a8450)
rax=00000000069b0008 rbx=fffff88003d5bb40 rcx=0000000002000000
rdx=000000000091d934 rsi=000000000000002c rdi=0000000000009349
rip=fffff88003d028b0 rsp=fffff880009a8e30 rbp=000000000091d960
 r8=0000000000000000  r9=0000000000000000 r10=00002cd59daa8c49
r11=0000000000000000 r12=00000000089b0008 r13=0000000000b20614
r14=0000000000b4df92 r15=000000000000002c
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
avgldx64+0x78b0:
fffff880`03d028b0 458b442404      mov     r8d,dword ptr [r12+4] ds:002b:00000000`089b000c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000089b000c

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f070e0
 00000000089b000c 

FOLLOWUP_IP: 
avgldx64+78b0
fffff880`03d028b0 458b442404      mov     r8d,dword ptr [r12+4]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88003d5bb40 to fffff88003d028b0

STACK_TEXT:  
fffff880`009a8e30 fffff880`03d5bb40 : fffff880`03d5bb40 00000000`069b0008 fffff8a0`002ab018 00000000`069b0008 : avgldx64+0x78b0
fffff880`009a8e38 fffff880`03d5bb40 : 00000000`069b0008 fffff8a0`002ab018 00000000`069b0008 00000000`005cb8ab : avgldx64+0x60b40
fffff880`009a8e40 00000000`069b0008 : fffff8a0`002ab018 00000000`069b0008 00000000`005cb8ab 003ed904`00000000 : avgldx64+0x60b40
fffff880`009a8e48 fffff8a0`002ab018 : 00000000`069b0008 00000000`005cb8ab 003ed904`00000000 00000000`069b0008 : 0x69b0008
fffff880`009a8e50 00000000`069b0008 : 00000000`005cb8ab 003ed904`00000000 00000000`069b0008 00000000`0091d934 : 0xfffff8a0`002ab018
fffff880`009a8e58 00000000`005cb8ab : 003ed904`00000000 00000000`069b0008 00000000`0091d934 00000000`06f80008 : 0x69b0008
fffff880`009a8e60 003ed904`00000000 : 00000000`069b0008 00000000`0091d934 00000000`06f80008 00000000`06a7a90c : 0x5cb8ab
fffff880`009a8e68 00000000`069b0008 : 00000000`0091d934 00000000`06f80008 00000000`06a7a90c 00000000`00000000 : 0x3ed904`00000000
fffff880`009a8e70 00000000`0091d934 : 00000000`06f80008 00000000`06a7a90c 00000000`00000000 fffff880`009a90b0 : 0x69b0008
fffff880`009a8e78 00000000`06f80008 : 00000000`06a7a90c 00000000`00000000 fffff880`009a90b0 fffff880`03d00cf9 : 0x91d934
fffff880`009a8e80 00000000`06a7a90c : 00000000`00000000 fffff880`009a90b0 fffff880`03d00cf9 00000000`00000000 : 0x6f80008
fffff880`009a8e88 00000000`00000000 : fffff880`009a90b0 fffff880`03d00cf9 00000000`00000000 00000000`00000000 : 0x6a7a90c


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  avgldx64+78b0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: avgldx64

IMAGE_NAME:  avgldx64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ab6446f

STACK_COMMAND:  .cxr 0xfffff880009a8450 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_avgldx64+78b0

BUCKET_ID:  X64_0x7E_avgldx64+78b0

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

 

[ChristoLombaard]

Hi Zigzag,

Thanks for the quick response. We will implement the proposed fix and test to see if this resolves the issue. I am hoping we can keep this thread active untill the fix is confirmed

Regards
Christo Lombaard

 

[ChristoLombaard]

Hi Zigzag / Anyone Else ,

We removed AVG as suggested and installed Microsoft Security Essentials and the PC was stable for around 3 weeks after which it started with the BSOD's again. We are resubmitting the BSOD and Perfmon diagnostics.

Thanks in advance for helping us !

Kind Regards
from the "Christo Lombaard BSOD Support Team":

 

[ChristoLombaard]

Hi,

I logged a follow-up message regarding a recurring BSOD problem on the 24th of July 2011 and have not had any response yet. Please Help ?

Regards
from the "Christo Lombaard BSOD Support Team"