Go Back   Velocity Reviews > Newsgroups > Windows 64bit
User Name
Password
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply

Windows 64bit - WinXP Pro x64: Blue Screen after installing and removing ipv6 (reboot?: no)

 
Thread Tools Search this Thread
Old 11-04-2009, 10:18 AM   #1
Default WinXP Pro x64: Blue Screen after installing and removing ipv6 (reboot?: no)


Hello,

I was trying to get my new internet/cable modem working.. internet
activation wasn't working so I thought maybe it needs ipv6 protocol.

So I installed ipv6 on WinXP x64 Pro... I gave it a try... it didn't
working... so I removed ipv6.

Windows asked if I wanted to reboot.. because it was required... first I
closed the dialog... then it asked again if I wanted to reboot... I said
"no" I wanna do reboot manually.

And then it crashed with a blue screen of death it said: "Bad Pool Header".

My internet is not working at the moment so I cannot analyze it and publish
the crash dump... but later I will...

See next post... just documentating what happend now...

Bye,
Skybuck.




Skybuck Flying
  Reply With Quote
Old 11-06-2009, 10:26 AM   #2
Carlos
 
Posts: n/a
Default RE: WinXP Pro x64: Blue Screen after installing and removing ipv6 (reb
Hi,
Try system restore, that should fix it.
Carlos

"Skybuck Flying" wrote:

> Hello,
>
> I was trying to get my new internet/cable modem working.. internet
> activation wasn't working so I thought maybe it needs ipv6 protocol.
>
> So I installed ipv6 on WinXP x64 Pro... I gave it a try... it didn't
> working... so I removed ipv6.
>
> Windows asked if I wanted to reboot.. because it was required... first I
> closed the dialog... then it asked again if I wanted to reboot... I said
> "no" I wanna do reboot manually.
>
> And then it crashed with a blue screen of death it said: "Bad Pool Header".
>
> My internet is not working at the moment so I cannot analyze it and publish
> the crash dump... but later I will...
>
> See next post... just documentating what happend now...
>
> Bye,
> Skybuck.
>
>
> .
>



Carlos
  Reply With Quote
Old 11-08-2009, 12:33 AM   #3
Skybuck Flying
 
Posts: n/a
Default Re: WinXP Pro x64: Blue Screen after installing and removing ipv6 (reboot?: no)
minidump file is here:

http://members.home.nl/hbthoupperman...i110409-01.dmp

folder is here:
http://members.home.nl/hbthouppermans/MiniDump/

analyze -v shows:

"
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini110409-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
SRV*c:\Tools\WinDbg\WebSymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free
x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.090805-1438
Machine Name:
Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140
Debug session time: Wed Nov 4 11:10:25.796 2009 (GMT+1)
System Uptime: 0 days 0:28:00.597
Loading Kernel Symbols
.................................................. ..............
.................................................. ...............
...........................
Loading User Symbols
Loading unloaded module list
.................................................. .
************************************************** *****************************
*
*
* Bugcheck Analysis
*
*
*
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa8004c018e0, fffffa8004c01980, e0a038e}

Probably caused by : win32k.sys ( win32k!HMFreeObject+14a )

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

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa8004c018e0, The pool entry we were looking for within the page.
Arg3: fffffa8004c01980, The next pool entry.
Arg4: 000000000e0a038e, (reserved)

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


BUGCHECK_STR: 0x19_20

POOL_ADDRESS: fffffa8004c018e0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800011ab36c to fffff8000102e890

STACK_TEXT:
fffffadf`c49deae8 fffff800`011ab36c : 00000000`00000019 00000000`00000020
fffffa80`04c018e0 fffffa80`04c01980 : nt!KeBugCheckEx
fffffadf`c49deaf0 fffff97f`ff09dad2 : 00000000`00000000 fffff97f`ff0a1912
fffffa80`04c018f0 fffff97f`f5993b58 : nt!ExFreePoolWithTag+0x45e
fffffadf`c49debb0 fffff97f`ff0716e3 : fffffa80`04c018f0 fffffa80`0404e480
fffffa80`04c018f0 00000000`00000001 : win32k!HMFreeObject+0x14a
fffffadf`c49debf0 fffff97f`ff071754 : 00000000`01dd0279 fffffadf`c49decf0
00000000`00000182 00000000`00000001 : win32k!DestroyCursor+0x208
fffffadf`c49dec40 fffff800`0102e33d : fffffadf`cbf48bf0 fffffadf`c49decf0
fffffadf`cbf48bf0 00000000`00000020 : win32k!NtUserDestroyCursor+0x44
fffffadf`c49dec70 00000000`77c3c6ea : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x3
00000000`02bffd38 00000000`00000000 : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 : 0x77c3c6ea


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!HMFreeObject+14a
fffff97f`ff09dad2 0fb74512 movzx eax,word ptr [rbp+12h]

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: win32k!HMFreeObject+14a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49e872b6

FAILURE_BUCKET_ID: X64_0x19_20_win32k!HMFreeObject+14a

BUCKET_ID: X64_0x19_20_win32k!HMFreeObject+14a

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

Bye,
Skybuck.





Skybuck Flying
  Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Win2K SP4 - what's the verdict? Max Quordlepleen Computer Support 6 09-16-2003 11:23 AM
Re: windows 2000 sp4 is a must PhilGreg Computer Support 0 07-17-2003 04:38 AM




SEO by vBSEO 3.3.2 ©2009, Crawlability, Inc.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46