Hello,
This is my first post on this forum. I have recently upgraded my 32bit inspiron 1520 to windows 7 (Build 7600). Up until yesterday, everything was running amazingly but then yesterday i received 2 blue screens. I dont know what caused it. I googled one of them and i found another thread saying that blue screens is caused by a hardware malfunction but i have no idea. Can someone help me?
I have included both of the file dumps in a .zip.
Skull
One dump was truncated so not alot ofo info from there. this one was caused by a system file win32k.sys. firefox wrote out to the system and killed win32k.
Let see you are 32bit and running 7600. you have a couple of older drivers from 2007 ans we should look at updating them. can I assume you aren't overclocking or running a raid? can you give us info about your computer so we know what hardware you have.
If you get more BSOD's keep uploading the dumps so we can narrow it down.
Hope this helps
Ken
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\101209-34616-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\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 = 0x82a10000 PsLoadedModuleList = 0x82b58810
Debug session time: Mon Oct 12 01:21:59.256 2009 (GMT-4)
System Uptime: 0 days 0:57:25.425
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 93cad687, ad9dbbec, 0}
Probably caused by : win32k.sys ( win32k!HmgQueryAltLock+11 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: 93cad687, The address that the exception occurred at
Arg3: ad9dbbec, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: firefox.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 93d3d21d to 93cad687
STACK_TEXT:
ad9dbc5c 93d3d21d f4050ac2 ad9dbd10 93d1f939 win32k!HmgQueryAltLock+0x11
ad9dbcec 93d3e718 00000000 00000000 00000000 win32k!SURFACE::bDeleteSurface+0x14e
ad9dbd00 93d1e1d3 00000000 00000000 fe0f1000 win32k!SURFREF::bDeleteSurface+0x14
ad9dbd14 93d1f9b8 f4050ac2 002ff11c f4050ac2 win32k!bDeleteSurface+0x20
ad9dbd28 82a5342a f4050ac2 002ff130 772b64f4 win32k!NtGdiDeleteObjectApp+0x7f
ad9dbd28 772b64f4 f4050ac2 002ff130 772b64f4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
002ff130 00000000 00000000 00000000 00000000 0x772b64f4
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!HmgQueryAltLock+11
93cad687 8b4004 mov eax,dword ptr [eax+4]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!HmgQueryAltLock+11
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc2a2
FAILURE_BUCKET_ID: 0x8E_win32k!HmgQueryAltLock+11
BUCKET_ID: 0x8E_win32k!HmgQueryAltLock+11
Followup: MachineOwner
---------
