Windowblinds 5.5 and Vista BSOD

BSOD on bootup

from Stardock Forums
Hello,

I am a long-time WG user and recently install WB5.5 on a new Vista PC. Everything appears to be working correctly except that I will occasionally get a BSOD on startup. I've analyze the minidump and found:

*******************************************************************************
* *
* 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: 94cc5881, The address that the exception occurred at
Arg3: 99290c04, 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.

FAULTING_IP:
win32k!HMAllocObject+27
94cc5881 8b402c mov eax,dword ptr [eax+2Ch]

TRAP_FRAME: 99290c04 -- (.trap 0xffffffff99290c04)
ErrCode = 00000000
eax=00000000 ebx=000000c0 ecx=ffaa5170 edx=00000000 esi=00000000 edi=00000000
eip=94cc5881 esp=99290c78 ebp=99290c88 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
win32k!HMAllocObject+0x27:
94cc5881 8b402c mov eax,dword ptr [eax+2Ch] ds:0023:0000002c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: WBVista.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 94ccdf9c to 94cc5881

STACK_TEXT:
99290c88 94ccdf9c 00000000 00000000 00000010 win32k!HMAllocObject+0x27
99290cac 94cb4fd6 00000000 00000000 000088b8 win32k!InternalSetTimer+0x86
99290cc8 94ca68a2 00000000 000088b8 94c86d62 win32k!SetRITTimer+0x22
99290ce0 94cbc1fe ffacc008 ffacc008 ffacc008 win32k!SetAppStarting+0x3d
99290d00 94cbc00e 00000000 ffacc008 892e8a18 win32k!xxxInitProcessInfo+0xaa
99290d24 94cbbfa7 ffacc008 00000001 892e8a18 win32k!xxxUserProcessCallout+0x1f
99290d40 81e19311 892e5d90 00000001 81d31b10 win32k!W32pProcessCallout+0x43
99290d4c 81d31b10 892e8a18 81c8c5ee 000010e4 nt!PsConvertToGuiThread+0x47
99290d64 77610f34 badb0d00 0012f190 00000000 nt!KeServiceDescriptorTable+0x10
WARNING: Frame IP not in any known module. Following frames may be wrong.
99290d68 badb0d00 0012f190 00000000 00000000 0x77610f34
99290d6c 0012f190 00000000 00000000 00000000 0xbadb0d00
99290d70 00000000 00000000 00000000 00000000 0x12f190


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!HMAllocObject+27
94cc5881 8b402c mov eax,dword ptr [eax+2Ch]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!HMAllocObject+27

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45d3cc1d

FAILURE_BUCKET_ID: 0x8E_win32k!HMAllocObject+27

BUCKET_ID: 0x8E_win32k!HMAllocObject+27

I've seen several mentions of VistaSrv on the forums. What is this and should WB be using this rather than WBVista?

System Info:
Motherboard: ASUS Striker Extreme
CPU: Intel Q6600
Memory: 4GB RAM
Video: NVidia 8800GTX

Any ideas or suggestions?

Regards,
Dan
windowblinds
2,511 views 7 replies
Reply #1 from Stardock Forums Top
*bump*
Reply #2 from WinCustomize Forums Top
Are you by chance using a USB Remote Control Dongle? (Like for a TV tuner) This has been noted as a problem before and I had it. The only known workaround (AFAIK) is to disconnect the dongle.   
SoundPackager - Customize the Windows sound scheme
Reply #3 from Stardock Forums Top

Are you by chance using a USB Remote Control Dongle? (Like for a TV tuner) This has been noted as a problem before and I had it. The only known workaround (AFAIK) is to disconnect the dongle.   


Nope, no dongle. However, the keyboard and mouse are both USB as well as the occasional time when I have a flash stick plugged in.

I've uninstalled WB from my Vista machine until this gets fixed or the developers jump in with a fix. Still using WB on XP though...

Regards,
Dan
Reply #4 from WinCustomize Forums Top
Dan what anti-virus program are you using? That and how did you install windowblinds? What security do you have running as for UAC and /or firewall and is there a antispy program being used?

Also if you could post your system info for windowblinds it would help a lot.

Reply #5 from WinCustomize Forums Top
Dan, you might also want to email support@stardock.com
Your problem may be outside the realm of community support in these forums.
Reply #6 from WinCustomize Forums Top

Dan what anti-virus program are you using? That and how did you install windowblinds? What security do you have running as for UAC and /or firewall and is there a antispy program being used?

Also if you could post your system info for windowblinds it would help a lot.




Anti-virus is AVG 7. Machine specs are at the end of the original post. I am running as a standard user and installed WB5.5 from the registered version setup executable. Nothing special...

Regards,
Dan

Reply #7 from WinCustomize Forums Top

Dan, you might also want to email support@stardock.com
Your problem may be outside the realm of community support in these forums.




Done. Thanks for the suggestion.

Regards,
Dan