BSOD crash dump XP

PhilB

PhilB

PhilB

Associate
Joined
21 Jul 2005
Posts
17
I've got both a laptop and desktop which have both recently starting giving my BSOD's reporting win32k.sys as the probable cause.

Chrome seems to be blame, what should I do about it? Chrome is up to date.

Here's the crash dump analysis.


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: chrome.exe

LAST_CONTROL_TRANSFER: from 00000000 to bf955547

STACK_TEXT:
b15b1c78 00000000 e114b800 0000001e ffffffff win32k!MultiUserNtGreCleanup+0x125


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!MultiUserNtGreCleanup+125
bf955547 8b4004 mov eax,dword ptr [eax+4]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!MultiUserNtGreCleanup+125

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4f0f0ff9

FAILURE_BUCKET_ID: 0x8E_win32k!MultiUserNtGreCleanup+125

BUCKET_ID: 0x8E_win32k!MultiUserNtGreCleanup+125

Followup: MachineOwner
 
Well, it seems very peculiar that a user-mode application like Chrome would BSOD (kernel mode) Windows, but that doesn't help you either really. If you upgraded to Vista at the very least the problem would probably disappear.

edit: Since I feel bad about the original reply, install this hotfix and I'm confident your problems will disappear.
 
Last edited:
markyb said:
Fantastic response :rolleyes: even though Windows XP is still supported until 2014 now...
Click to expand...
That's nice.

Vauxhall cars have a lifetime warranty but I wouldn't expect to run one for 30 years, nor would I desire to.

There are numerous reasons, not least of which performance on the same hardware, to upgrade. You'd save money in productivity, etc. I've been going around upgrading XP machines (that ran like a dog, had numerous quirky issues with modern hardware) to Windows 7 Pro here at work and they've had a new lease of life.

That's by the by really since the hotfix I linked will fix this guys problem.
 
Durzel said:
That's nice.

Vauxhall cars have a lifetime warranty but I wouldn't expect to run one for 30 years, nor would I desire to.

There are numerous reasons, not least of which performance on the same hardware, to upgrade. You'd save money in productivity, etc. I've been going around upgrading XP machines (that ran like a dog, had numerous quirky issues with modern hardware) to Windows 7 Pro here at work and they've had a new lease of life.

That's by the by really since the hotfix I linked will fix this guys problem.
Click to expand...

Whilst I'll agree by upgrading there will be a number of improvements, performance, security e.t.c. I really don't think the best suggestion is to spend over £100 to replace the OS on a aging desktop/laptop for the sake of a Web Browser causing a BSOD on Windows XP.

I support a very large number of companies who use Windows XP, in fact in most companies networks Windows 7 is still in the "testing phase" XP is still a very usable OS. I'm willing to bet if you would performed a new install of Windows XP on the machines you've recently upgraded - it would have also of given them a new lease of life.
 
Last edited:
markyb said:
PhilB - I would first try using Google Chrome in some kind of safe mode which disables any add-ons e.t.c. I don't use it myself but try following this link here...
Click to expand...

I've disabled all three extensions for now, until I have a bit more free time uninstall and reinstall chrome.

I've also reported the error to the chrome help boards too.

I quite like XP, it's very stable.
 
You must log in or register to reply here.
Back
Top Bottom