Random BSOD :(

[vongenkuu]

Quit L4D2 to goto bed and up pops a BSOD. From the ensuing restart, the desktop failed to load (the mouse was visible and movable, but the taskbar and icons failed to show. ctrl+alt+dlt did work though). Any information shed on it would be greatly appreciated!

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fb49b860, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 9c5482ae, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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

*** WARNING: Unable to verify timestamp for avipbb.sys
*** ERROR: Module load completed but symbols could not be loaded for avipbb.sys

Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from 825466d8
Unable to read MiSystemVaType memory at 825272e0
fb49b860

FAULTING_IP:
win32k!ttfdCloseFontContext+16
9c5482ae 8b3e mov edi,dword ptr [esi]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

TRAP_FRAME: a9648a70 -- (.trap 0xffffffffa9648a70)
ErrCode = 00000000
eax=fb8dfb60 ebx=fb8dfb60 ecx=87031900 edx=00000000 esi=fb49b860 edi=9c5481e3
eip=9c5482ae esp=a9648ae4 ebp=a9648af0 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
win32k!ttfdCloseFontContext+0x16:
9c5482ae 8b3e mov edi,dword ptr [esi] ds:0023:fb49b860=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 82474b04 to 8248ab9e

STACK_TEXT:
a9648a58 82474b04 00000000 fb49b860 00000000 nt!MmAccessFault+0x158
a9648a58 9c5482ae 00000000 fb49b860 00000000 nt!KiTrap0E+0xdc
a9648af0 9c5481d5 fb8dfb60 a9648b44 a9648b0c win32k!ttfdCloseFontContext+0x16
a9648b00 9c5481fb fb8dfcf0 a9648b28 9c548274 win32k!ttfdDestroyFont+0x16
a9648b0c 9c548274 fb8dfcf0 fc1c5c50 a9648b80 win32k!ttfdSemDestroyFont+0x18
a9648b28 9c547f98 fb8dfcf0 fc1c5c50 fe305cf0 win32k!PDEVOBJ:estroyFont+0x65
a9648b4c 9c5098af 00000000 00000000 00000001 win32k!RFONTOBJ::vDeleteRFONT+0x33
a9648b84 9c509a30 a9648ba8 00000000 fded2354 win32k!vRestartKillRFONTList+0x7b
a9648bb8 9c4becd0 0000001c fded2354 00000000 win32k!PFTOBJ::bUnloadWorkhorse+0x115
a9648be4 9c4be8ca fdc4b008 00000000 00000000 win32k!vCleanupPrivateFonts+0x4d
a9648bfc 9c4bb092 fdc4b008 00000000 00000000 win32k!NtGdiCloseProcess+0x13d
a9648c1c 9c4babd1 fdc4b008 00000000 871cfbc0 win32k!GdiProcessCallout+0x145
a9648c38 82625fe1 85147ad8 00000000 af329cdd win32k!W32pProcessCallout+0x5d
a9648ca4 826265b0 00000000 00000000 84a901e8 nt!PspExitThread+0x4a0
a9648cc0 826331ff 84a901e8 00000000 00000001 nt!PspTerminateThreadByPointer+0x5b
a9648cf0 93d24c67 ffffffff 00000000 ffffffff nt!NtTerminateProcess+0x1e0
WARNING: Stack unwind information not available. Following frames may be wrong.
a9648d54 824719aa ffffffff 00000000 0012fe94 avipbb+0x8c67
a9648d54 772e5e74 ffffffff 00000000 0012fe94 nt!KiFastCallEntry+0x12a
0012fe94 00000000 00000000 00000000 00000000 0x772e5e74


STACK_COMMAND: kb

FOLLOWUP_IP:
avipbb+8c67
93d24c67 ?? ???

SYMBOL_STACK_INDEX: 10

SYMBOL_NAME: avipbb+8c67

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: avipbb

IMAGE_NAME: avipbb.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49c9008b

FAILURE_BUCKET_ID: 0x50_avipbb+8c67

BUCKET_ID: 0x50_avipbb+8c67

Followup: MachineOwner





------------

This is all i seem to be able to come up with.

Thanks

 

[Philtor]

I suspect you may have a faulty stick of RAM. Download a Memtest boot disk and run it for a few hours at least.... http://www.memtest.org/download/4.10/memtest86+-4.10.iso.zip

 

[vongenkuu]

From other sources, seems to be from a bug in Avira. Its the first BSOD i've had and i "know" my mobo is on it's way out. I think it's just a wait and see but if anyone can shed more light perhaps?

 

[Philtor]

In my experience a BSOD is almost always a sign of failing hardware. If you suspect Avira as the cause then why not uninstall it and use Avast instead?

 

[vongenkuu]

I've had one BSOD prior to this one and it was related to a dodgy GPU driver update. I think there are reports of a dodgy Avira 10 file causing problems. Dont know too much though

I've always used Avira (on both big rig and laptop) and never had any problems. Just a case of why fix whats not broken tbh.

 

[Philtor]

Just a case of why fix whats not broken tbh.

But your getting the BSOD so it is broken. Avast is excellent. I know you probably won't change but it doesn't say much for Avira if they can't test their AV program properly to the extent that it does this.