vista bsod

A

amey_dude

Disciple
Hello everyone, I am occationally get a win32k.sys bsod.

Here i the memory dump and debugging details.

Code: 
Probably caused by : win32k.sys ( win32k!EngAlphaBlend+2b69 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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: 92f28852, The address that the exception occurred at
Arg3: 8e113528, Trap Frame
Arg4: 00000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************

MODULE_NAME: win32k

FAULTING_MODULE: 81c4b000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  47c78851

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

FAULTING_IP: 
win32k!EngAlphaBlend+2b69
92f28852 a5              movs    dword ptr es:[edi],dword ptr [esi]

TRAP_FRAME:  8e113528 -- (.trap 0xffffffff8e113528)
ErrCode = 00000000
eax=00000188 ebx=8e113b40 ecx=00000000 edx=f0758ec0 esi=00000188 edi=00000000
eip=92f28852 esp=8e11359c ebp=8e1135b4 iopl=0         nv up ei ng nz ac pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010297
win32k!EngAlphaBlend+0x2b69:
92f28852 a5              movs    dword ptr es:[edi],dword ptr [esi] es:0023:00000000=???????? ds:0023:00000188=????????
Resetting default scope

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

BUGCHECK_STR:  0x8E

LAST_CONTROL_TRANSFER:  from 81c815a0 to 81d18163

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
8e1130e8 81c815a0 0000008e c0000005 92f28852 nt+0xcd163
8e1134b8 81ca363a 8e1134d4 00000000 8e113528 nt+0x365a0
8e113544 92f241de fa756430 00000000 00000000 nt+0x5863a
8e1135b4 92ee6fa9 00000005 00000005 00000000 win32k!EngStrokePath+0x32a0
8e113950 92e836a1 8e113ad8 00000002 00000001 win32k!EngSetLastError+0x3b26
8e113b2c 92e83c3e 00000000 44040d30 0c100ccb win32k!EngQueryW32kCddInterface+0x7348
8e113b70 92e83aba fe805fb8 ff01071e 00000000 win32k!EngQueryW32kCddInterface+0x78e5
8e113be8 92e8407d 00000000 ff01071e fe826a08 win32k!EngQueryW32kCddInterface+0x7761
8e113c20 92e81d6e fe805fb8 fe826a08 fd2c4a70 win32k!EngQueryW32kCddInterface+0x7d24
8e113c54 92ed10d3 fe805fb8 fe800608 93032b20 win32k!EngQueryW32kCddInterface+0x5a15
8e113c7c 92ed26c4 93032b20 00000000 fe805fb8 win32k!EngUnlockSurface+0x3867
8e113cd4 92ed2950 00000000 fe805fb8 8e113d24 win32k!EngUnlockSurface+0x4e58
8e113cf4 92ed717b fe805fb8 00000000 00000000 win32k!EngUnlockSurface+0x50e4
8e113d40 81ca2a7a fe805fb8 00000000 00000000 win32k!EngUnlockSurface+0x990f
8e113d64 77c99a94 badb0d00 018cf5a8 00000000 nt+0x57a7a
8e113d68 badb0d00 018cf5a8 00000000 00000000 0x77c99a94
8e113d6c 018cf5a8 00000000 00000000 00000000 0xbadb0d00
8e113d70 00000000 00000000 00000000 00000000 0x18cf5a8
STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!EngAlphaBlend+2b69
92f28852 a5              movs    dword ptr es:[edi],dword ptr [esi]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!EngAlphaBlend+2b69

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  win32k.sys

BUCKET_ID:  WRONG_SYMBOLS

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

Please help...as i didnt understand the problem...
 
Most probably this is a hardware issue, install the latst drivers preferably microsoft signed...

check your cables and connections, cant tell you how many times I have had errors or BSOD's caused by loose connections and cables....

Try to do a controlled startup and get the error number then google it, it will make you learn more thoroughly.
 
seems this was fixed in sp1 You receive a Stop error message on a Windows Vista-based computer: "Stop 0x00000001 (0x00000000, 0x7FFDC000, 0X0000FFFF, 0X00000000)"

SYMPTOMS
Consider the following scenario: • You are using a Windows Vista-based computer.
• The color scheme is set to Windows Aero.
• You enter your credentials to unlock the computer. When you unlock the computer, you switch from a secure desktop to the default desktop.
• An event hook is running in the secure desktop. The event hook is registered by using the SetWinEventHook application programming interface (API).
Note A secure desktop appears when the computer is locked. When a secure desktop appears, you can enter your credentials to unlock the computer.

In this scenario, you receive a Stop error message that resembles the following:
Stop 0x00000001 (0x00000000, 0x7FFDC000, 0X0000FFFF, 0X00000000)
Note The Stop error message always has a Stop error code of 0x00000001. Also, the third parameter of the Stop error message is always 0x0000FFFF.
Click to expand...
 
^Boo, what makes you think the link you posted is related to this? The exception in both cases is different.

BTW, if updating to SP1 does not work, you may want to consider cleanly uninstalling and then reinstalling your graphics drivers.
 
^ well, both are access voilations in the same driver. both seem to related to Aero. so... I thought...
 
this reminded me of the press reports that MS blamed nVidia drivers for Vista's reported instability during the early days...
 
I already have sp1 installed. I have upgraded all drivers to latest...but still doesnt work.

Also I dont get it frequently, just once a week...so actually there isnt any problem but still i am curious abt why the bsod is comming.

Also i checked the cables...Now lets see wht happens...
 
Back
Top