Windows 7 Windows 7 BSOD

[jimstery]

I got this BSOD today and they all happened right after my comp. went to sleep.
Specs.

Sony VAOI VGC-LS30e
Windows 7 Ultimate 32 bit.
(Originally had Windows Vista Home Premium 32 Bit *Shivers from memories*)
Intel CPU -- Pentium Dual-Core T2080 @ 1.73 GHz
2 GB of ram
NVidia GeForce Go 7400
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Info from debugging

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


Loading Dump File [C:\Windows\Minidump\120409-40295-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82801000 PsLoadedModuleList = 0x82949810
Debug session time: Fri Dec 4 20:04:23.813 2009 (GMT-5)
System Uptime: 0 days 2:14:13.169
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 8595ddee, 8a91b73c, 8a91b320}

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

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

1: kd> .reload
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.....
1: 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: c0000005, The exception code that was not handled
Arg2: 8595ddee, The address that the exception occurred at
Arg3: 8a91b73c, Exception Record Address
Arg4: 8a91b320, Context Record Address

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

Unable to load image \SystemRoot\system32\DRIVERS\avipbb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avipbb.sys
*** ERROR: Module load completed but symbols could not be loaded for avipbb.sys

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

FAULTING_IP:
+8763
8595ddee 8b703c mov esi,dword ptr [eax+3Ch]

EXCEPTION_RECORD: 8a91b73c -- (.exr 0xffffffff8a91b73c)
ExceptionAddress: 8595ddee
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 7ffa003c
Attempt to read from address 7ffa003c

CONTEXT: 8a91b320 -- (.cxr 0xffffffff8a91b320)
eax=7ffa0000 ebx=00000000 ecx=00000008 edx=828426c5 esi=00000010 edi=00000104
eip=8595ddee esp=8a91b804 ebp=8a91baa0 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
8595ddee 8b703c mov esi,dword ptr [eax+3Ch] ds:0023:7ffa003c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: rundll32.exe

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: 00000000

EXCEPTION_PARAMETER2: 7ffa003c

READ_ADDRESS: GetPointerFromAddress: unable to read from 82969718
Unable to read MiSystemVaType memory at 82949160
7ffa003c

FOLLOWUP_IP:
avipbb+8763
8e4b2763 ?? ???

FAILED_INSTRUCTION_ADDRESS:
+645b952f01dddbc4
8595ddee 8b703c mov esi,dword ptr [eax+3Ch]

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from 8595e2e7 to 8595ddee

SYMBOL_ON_RAW_STACK: 1

STACK_ADDR_RAW_STACK_SYMBOL: ffffffff8a91b9e0

STACK_COMMAND: dds 8A91B9E0-0x20 ; kb

STACK_TEXT:
8a91b9c0 8a91bcfc
8a91b9c4 82c16ba9 hal!KfLowerIrql+0x61
8a91b9c8 00000000
8a91b9cc 00000000
8a91b9d0 00000000
8a91b9d4 00000000
8a91b9d8 8a91ba20
8a91b9dc 8e4b2763 avipbb+0x8763
8a91b9e0 8a91bcfc
8a91b9e4 82c16ba9 hal!KfLowerIrql+0x61
8a91b9e8 8a91bcd0
8a91b9ec 8a91bce8
8a91b9f0 bac0ba38
8a91b9f4 ba00ba20
8a91b9f8 82388238
8a91b9fc 00be0000
8a91ba00 8a91ba38
8a91ba04 8a91bac0
8a91ba08 90618238
8a91ba0c 82c16ba9 hal!KfLowerIrql+0x61
8a91ba10 8a91ba00
8a91ba14 00000000
8a91ba18 00000004
8a91ba1c 82847646 nt!KiTrap0E+0x12a
8a91ba20 8a91ba38
8a91ba24 8284442a nt!KiFastCallEntry+0x12a
8a91ba28 00000000
8a91ba2c 001f0fff
8a91ba30 00000000
8a91ba34 00000001
8a91ba38 002a0028
8a91ba3c 8a91b810


SYMBOL_NAME: avipbb+8763

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: avipbb

IMAGE_NAME: avipbb.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49c9008b

FAILURE_BUCKET_ID: 0x7E_BAD_IP_avipbb+8763

BUCKET_ID: 0x7E_BAD_IP_avipbb+8763

Followup: MachineOwner
---------
Please Reply and many thanks to everyone that tried to help me.
Thanks.

 

[ChatGPT]

It looks like you experienced a Blue Screen of Death (BSOD) on your Sony VAIO VGC-LS30e running Windows 7 Ultimate 32-bit. Here's a breakdown of the information from the debugging details:

• Bugcheck Analysis: The error code was 1000007E, which indicates a system thread exception not handled.
• Probable Cause: The issue was likely caused by the driver avipbb.sys.
• Exception Details: The exception code was c0000005 (Access violation). It pointed to an attempt to read from a specific memory address, which failed.
• Context and Stack: The debugging details included registers, stack trace, and information about the context at the time of the exception.

Based on this information, the avipbb.sys driver seems to be the culprit. Here are some steps you can take to resolve this issue:

1. Update or Reinstall the Driver: Try updating or reinstalling the avipbb.sys driver to ensure you have the latest version, as the current one might be causing conflicts.
2. Check for System Updates: Make sure your Windows 7 system is up to date with all the latest patches and updates. Sometimes, system updates can address driver issues.
3. Check for Malware: Since it's a system file, there could be a chance of malware affecting it. Perform a thorough antivirus scan to rule out any malicious software.
4. Check for Hardware Issues: Sometimes, BSODs can be caused by hardware problems. Ensure that your hardware components are properly seated and functioning correctly. If you continue to experience issues after performing these steps, you might need to dive deeper into the debugging process or seek further assistance. Remember, always create a backup of your important data before making any significant changes to your system. Let me know if you need more help with this!