Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Server > Bad_Pool_Caller

Reply
Thread Tools Display Modes

Bad_Pool_Caller

 
 
Guest
Posts: n/a

 
      09-27-2004
I sure hope you can help. After re-booting my windows
2003 server due to security updates, I get the following
blue screen.

bad_pool_caller

stop: 0x000000c2 (0x00000044, 0x00000000, 0x80000000,
0x00000000)

I can access the machine in safe mode, I have tried to
uninstall the recent update and I am still getting the
same message. I have tried to install
http://www.microsoft.com/whdc/devtoo...ging/default.m
spx but since I am in safe mode, the installer is not
working. If you have any suggestions, please help.

Nancy
 
Reply With Quote
 
 
 
 
Todd J Heron
Guest
Posts: n/a

 
      09-28-2004
Look for a file in C:\Windows\Minidump called Mini<MostRecentDate>.dmp.
Paste it's conents in your reply to this message to the group. You have a
bad device driver causing your system to crash, and you proved that by going
into Safe Mode successfully. If I had to guess I'd say it was your sound
driver.

--
Todd J Heron, MCSE
Windows 2003/2000/NT

<> wrote in message
news:256d01c4a4db$69caada0$...
> I sure hope you can help. After re-booting my windows
> 2003 server due to security updates, I get the following
> blue screen.
>
> bad_pool_caller
>
> stop: 0x000000c2 (0x00000044, 0x00000000, 0x80000000,
> 0x00000000)
>
> I can access the machine in safe mode, I have tried to
> uninstall the recent update and I am still getting the
> same message. I have tried to install
> http://www.microsoft.com/whdc/devtoo...ging/default.m
> spx but since I am in safe mode, the installer is not
> working. If you have any suggestions, please help.
>
> Nancy



 
Reply With Quote
 
Nancy
Guest
Posts: n/a

 
      09-28-2004
I couldn't past the file for some reason but I used
dumpchk.exe on another machine and this is what it gave
me.

Nancy

Probably caused by : ntoskrnl.exe ( nt+655b9 )

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

Finished dump check

C:\Program Files\Debugging Tools for Windows>dumpchk -v
e:Mini092704-03.dmp
Loading dump file e:Mini092704-03.dmp

Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\Mini092704-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are
available

Symbol search path is: *** Invalid ***
************************************************** ********
******************
* Symbol loading may be unreliable without a symbol
search path. *
* Use .symfix to have the debugger choose a symbol
path. *
* After setting your symbol path, use .reload to refresh
symbol locations. *
************************************************** ********
******************
Executable search path is:
************************************************** ********
***********
* 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+ *
************************************************** ********
***********
Unable to load image \WINDOWS\system32\ntoskrnl.exe,
Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be
loaded for ntoskrnl.ex
e
Windows Server 2003 Kernel Version 3790 MP (2 procs) Free
x86 compatible
Product: Server, suite: TerminalServer SingleUserTS
Kernel base = 0x804de000 PsLoadedModuleList = 0x8057b6a8
Debug session time: Mon Sep 27 16:43:35 2004
System Uptime: 0 days 0:00:30.421
************************************************** ********
***********
* 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+ *
************************************************** ********
***********
Unable to load image \WINDOWS\system32\ntoskrnl.exe,
Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be
loaded for ntoskrnl.ex
e
Loading Kernel Symbols
.................................................. .........
.......................
....................
Loading unloaded module list
....
Loading User Symbols
************************************************** ********
*********************
*
*
* Bugcheck
Analysis *
*
*
************************************************** ********
*********************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {44, 0, 80000000, 0}

***** 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 ***
***
***
************************************************** ********
***************
Probably caused by : ntoskrnl.exe ( nt+655b9 )

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

----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000ece
KdSecondaryVersion 00000000
DirectoryTableBase 3684c000
PfnDataBase 80580078
PsLoadedModuleList 8057b6a8
PsActiveProcessHead 80581888
MachineImageType 0000014c
NumberProcessors 00000002
BugCheckCode 000000c2
BugCheckParameter1 00000044
BugCheckParameter2 00000000
BugCheckParameter3 80000000
BugCheckParameter4 00000000
PaeEnabled 00000000
KdDebuggerDataBlock 805693d0
ProductType 00000003
SuiteMask 00000110
WriterStatus 00000000
MiniDumpFields 00000cff

TRIAGE_DUMP32:
ServicePackBuild 00000000
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 00002648
ThreadOffset 000028c0
CallStackOffset 00002b20
SizeOfCallStack 000003d0
DriverListOffset 00003208
DriverCount 00000064
StringPoolOffset 00004fb8
StringPoolSize 00001b28
BrokenDriverOffset 00000000
TriageOptions ffffffff
TopOfStack ba906c30
DebuggerDataOffset 00002ef0
DebuggerDataSize 00000318
DataBlocksOffset 00006ae0
DataBlocksCount 00000004
00000000 - 00000fff at offset 00006b20
f7737000 - f7737fff at offset 00007b20
8618c000 - 8618cfff at offset 00008b20
80543000 - 80543fff at offset 00009b20
Max offset ab20, 54e0 from end of file


Windows Server 2003 Kernel Version 3790 MP (2 procs) Free
x86 compatible
Product: Server, suite: TerminalServer SingleUserTS
Kernel base = 0x804de000 PsLoadedModuleList = 0x8057b6a8
Debug session time: Mon Sep 27 16:43:35 2004
System Uptime: 0 days 0:00:30.421
start end module name
804de000 80744000 nt Tue Mar 25 02:39:34 2003
(3E8015C6)
80744000 8076c000 hal Tue Mar 25 01:07:28 2003
(3E800030)
b790b000 b7923000 Cdfs Tue Mar 25 02:17:19 2003
(3E80108F)
b7923000 b7936000 Fips Tue Mar 25 02:54:59 2003
(3E801963)
b7936000 b79a3000 mrxsmb Tue Mar 25 01:09:09 2003
(3E800095)
b8de3000 b8e0f000 rdbss Tue Mar 25 01:09:06 2003
(3E800092)
ba34e000 ba383000 netbt Fri Jul 18 12:16:03 2003
(3F182B53)
ba383000 ba3e5000 tcpip Tue Mar 25 02:04:01 2003
(3E800D71)
ba6fb000 ba717000 ipsec Tue Mar 25 01:55:45 2003
(3E800B81)
bf800000 bf9c6000 win32k Tue Mar 25 02:40:49 2003
(3E801611)
bf9c6000 bfa1c680 ati2drad Tue Mar 25 03:43:37 2003
(3E8024C9)
bff80000 bff96000 dxg Tue Mar 25 03:46:23 2003
(3E80256F)
f3842000 f3855000 usbhub Tue Mar 25 01:10:46 2003
(3E8000F6)
f3855000 f3888000 update Tue Mar 25 02:59:59 2003
(3E801A8F)
f3d7c000 f3db0000 rdpdr Tue Mar 25 01:09:30 2003
(3E8000AA)
f40e2000 f40f0000 NDProxy Tue Mar 25 01:11:30 2003
(3E800122)
f42d8000 f42df000 dxgthk Tue Mar 25 01:05:52 2003
(3E7FFFD0)
f47ce000 f47dd000 termdd Tue Mar 25 01:02:52 2003
(3E7FFF1C)
f4905000 f4906580 USBD Tue Mar 25 01:10:39 2003
(3E8000EF)
f4988000 f4989000 swenum Wed Dec 04 11:10:07 2002
(3DEE36EF)
f4ce9000 f4cf1000 rasacd Tue Mar 25 01:11:50 2003
(3E800136)
f4dcb000 f4dd3000 mnmdd Tue Mar 25 01:07:53 2003
(3E800049)
f57ae000 f57b6000 RDPCDD Tue Mar 25 01:03:05 2003
(3E7FFF29)
f57b6000 f57bd000 Null Tue Mar 25 01:03:05 2003
(3E7FFF29)
f57ce000 f57d6000 Fs_Rec Tue Mar 25 01:08:36 2003
(3E800074)
f5b63000 f5b70000 netbios Tue Mar 25 01:09:53 2003
(3E8000C1)
f5b73000 f5b7d000 Dxapi Tue Mar 25 01:06:01 2003
(3E7FFFD9)
f619c000 f61a6000 flpydisk Tue Mar 25 01:04:32 2003
(3E7FFF80)
f63d6000 f63d9bc0 dump_cpqcissm Mon Feb 10 16:34:54
2003 (3E48290E)
f64a7000 f64b6000 msgpc Tue Mar 25 01:10:12 2003
(3E8000D4)
f64c7000 f64dc000 raspptp Tue Mar 25 02:19:09 2003
(3E8010FD)
f6540000 f655b000 ndiswan Tue Mar 25 02:48:19 2003
(3E8017D3)
f655b000 f6572000 rasl2tp Tue Mar 25 01:54:46 2003
(3E800B46)
f673a000 f6747000 wanarp Tue Mar 25 01:11:22 2003
(3E80011A)
f678a000 f6796000 Npfs Tue Mar 25 01:08:59 2003
(3E80008B)
f679a000 f67a4000 Msfs Tue Mar 25 01:08:56 2003
(3E800088)
f682b000 f683b5a0 CPQCISSE Tue Feb 18 11:22:11 2003
(3E526BC3)
f683c000 f685de80 USBPORT Tue Mar 25 01:10:43 2003
(3E8000F3)
f685e000 f687dd00 ks Wed Dec 04 11:09:38 2002
(3DEE36D2)
f687e000 f6892000 redbook Tue Mar 25 01:04:38 2003
(3E7FFF86)
f6892000 f68a6000 cdrom Tue Mar 25 01:05:18 2003
(3E7FFFAE)
f68a6000 f68be000 serial Tue Mar 25 01:40:08 2003
(3E8007D8)
f68be000 f68d5000 parport Tue Mar 25 01:03:56 2003
(3E7FFF5C)
f68d5000 f68eb000 i8042prt Tue Mar 25 03:01:43 2003
(3E801AF7)
f68eb000 f692f780 cpqasm Thu Mar 20 15:50:13 2003
(3E7A3795)
f6b9b000 f6bc8700 q57xp32 Thu May 20 11:44:36 2004
(40ACE074)
f6bc9000 f6be2000 VIDEOPRT Tue Mar 25 01:08:02 2003
(3E800052)
f6be2000 f6c35d80 ati2mpad Thu Jul 18 20:13:20 2002
(3D3767B0)
f6e19000 f6e22000 raspti Tue Mar 25 01:11:36 2003
(3E800128)
f6e29000 f6e34000 ptilink Tue Mar 25 01:03:51 2003
(3E7FFF57)
f6e39000 f6e44000 TDI Tue Mar 25 01:14:28 2003
(3E8001D4)
f6e49000 f6e57000 raspppoe Tue Mar 25 01:11:37 2003
(3E800129)
f7222000 f7244000 Mup Tue Mar 25 02:55:58 2003
(3E80199E)
f7244000 f7285000 NDIS Tue Mar 25 02:45:35 2003
(3E80172F)
f7285000 f7322000 Ntfs Tue Mar 25 01:40:05 2003
(3E8007D5)
f7322000 f7343000 KSecDD Tue Mar 25 01:05:39 2003
(3E7FFFC3)
f7343000 f7359000 CLASSPNP Tue Mar 25 01:38:14 2003
(3E800766)
f7359000 f736de80 adpu160m Thu Jun 20 21:02:53 2002
(3D12894D)
f736e000 f738a000 atapi Tue Mar 25 01:04:48 2003
(3E7FFF90)
f738a000 f73b0000 SCSIPORT Tue Mar 25 02:01:25 2003
(3E800CD5)
f73b0000 f73d1000 volsnap Tue Mar 25 01:05:47 2003
(3E7FFFCB)
f73d1000 f73fb000 dmio Tue Mar 25 01:08:14 2003
(3E80005E)
f73fb000 f7420000 ftdisk Tue Mar 25 01:05:26 2003
(3E7FFFB6)
f7420000 f7435000 pci Tue Mar 25 01:16:40 2003
(3E800258)
f7435000 f7466000 ACPI Tue Mar 25 01:16:21 2003
(3E800245)
f7487000 f7490000 WMILIB Tue Mar 25 01:13:00 2003
(3E80017C)
f7497000 f74a6000 isapnp Tue Mar 25 01:16:35 2003
(3E800253)
f74a7000 f74b4000 PCIIDEX Tue Mar 25 01:04:44 2003
(3E7FFF8C)
f74b7000 f74c6000 MountMgr Tue Mar 25 01:03:05 2003
(3E7FFF29)
f74c7000 f74d5000 PartMgr Tue Mar 25 02:04:02 2003
(3E800D72)
f74d7000 f74e6ae0 cpq32fs2 Mon Nov 18 17:47:47 2002
(3DD97C23)
f74e7000 f74ef080 symc8xx Tue Sep 25 13:25:49 2001
(3BB0CC2D)
f74f7000 f7500100 symmpi Tue Dec 10 11:32:15 2002
(3DF6251F)
f7507000 f7516000 disk Tue Mar 25 01:05:20 2003
(3E7FFFB0)
f7517000 f7523000 Dfs Tue Mar 25 01:09:52 2003
(3E8000C0)
f7527000 f7530000 crcdisk Tue Mar 25 01:07:23 2003
(3E80002B)
f7547000 f7550000 ndistapi Tue Mar 25 01:11:28 2003
(3E800120)
f7557000 f7563000 processr Tue Mar 25 01:07:36 2003
(3E800038)
f7567000 f7570000 watchdog Tue Mar 25 01:09:01 2003
(3E80008D)
f7647000 f7651000 kbdclass Tue Mar 25 01:03:10 2003
(3E7FFF2E)
f7657000 f7661000 mouclass Tue Mar 25 01:03:09 2003
(3E7FFF2D)
f7667000 f7671000 serenum Tue Mar 25 01:04:01 2003
(3E7FFF61)
f7677000 f7682000 fdc Tue Mar 25 01:04:31 2003
(3E7FFF7F)
f76a7000 f76b3000 vga Tue Mar 25 01:08:03 2003
(3E800053)
f76f7000 f7700000 dump_diskdump Tue Mar 25 01:05:15
2003 (3E7FFFAB)
f7707000 f770f000 kdcom Tue Mar 25 01:08:00 2003
(3E800050)
f770f000 f7717000 BOOTVID Tue Mar 25 01:07:58 2003
(3E80004E)
f7717000 f771e000 pciide Tue Mar 25 01:04:46 2003
(3E7FFF8E)
f771f000 f7726000 dmload Tue Mar 25 01:08:08 2003
(3E800058)
f7727000 f772e080 sym_hi Wed Oct 03 18:48:12 2001
(3BBBA3BC)
f772f000 f7733c20 ino_flpy Fri May 18 12:36:22 2001
(3B055D96)
f7747000 f774f000 OPRGHDLR Tue Mar 25 01:16:25 2003
(3E800249)
f7787000 f778b200 usbohci Tue Mar 25 01:10:41 2003
(3E8000F1)
f778f000 f7797000 audstub Tue Mar 25 01:09:12 2003
(3E800098)
f784f000 f7856000 Beep Tue Mar 25 01:03:04 2003
(3E7FFF28)
f7857000 f785bae0 sonysdx Tue Sep 02 09:39:43 2003
(3F54ABAF)
f7897000 f789ab60 cpqarray Mon Oct 21 16:18:51 2002
(3DB46F3B)
f789b000 f789ef80 symc810 Fri Dec 08 11:40:59 2000
(3A311D2B)
f789f000 f78a2bc0 cpqcissm Mon Feb 10 16:34:54 2003
(3E48290E)
f78a3000 f78a6460 cpqarry2 Mon Nov 05 15:47:33 2001
(3BE708F5)

Unloaded modules:
f6df9000 f6e07000 imapi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f453f000 f4542000 scsichng.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f4db3000 f4dbb000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
************************************************** ********
*********************
*
*
* Bugcheck
Analysis *
*
*
************************************************** ********
*********************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {44, 0, 80000000, 0}

***** 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 ***
***
***
************************************************** ********
***************
Probably caused by : ntoskrnl.exe ( nt+655b9 )

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

Finished dump check

C:\Program Files\Debugging Tools for Windows>
>-----Original Message-----
>Look for a file in C:\Windows\Minidump called

Mini<MostRecentDate>.dmp.
>Paste it's conents in your reply to this message to the

group. You have a
>bad device driver causing your system to crash, and you

proved that by going
>into Safe Mode successfully. If I had to guess I'd say

it was your sound
>driver.
>
>--
>Todd J Heron, MCSE
>Windows 2003/2000/NT
>
><> wrote in message
>news:256d01c4a4db$69caada0$...
>> I sure hope you can help. After re-booting my windows
>> 2003 server due to security updates, I get the

following
>> blue screen.
>>
>> bad_pool_caller
>>
>> stop: 0x000000c2 (0x00000044, 0x00000000, 0x80000000,
>> 0x00000000)
>>
>> I can access the machine in safe mode, I have tried to
>> uninstall the recent update and I am still getting the
>> same message. I have tried to install
>>

http://www.microsoft.com/whdc/devtoo...ging/default.m
>> spx but since I am in safe mode, the installer is not
>> working. If you have any suggestions, please help.
>>
>> Nancy

>
>
>.
>

 
Reply With Quote
 
Todd J Heron
Guest
Posts: n/a

 
      09-28-2004
Go back to Safe Mode. Open a CMD prompt and run a CHKDSK against the
opertaing system drive. Use this syntax:

chkdsk /F /R

--
Todd J Heron, MCSE
Windows 2003/2000/NT

"Nancy" <> wrote in message
news:050101c4a508$476aa7b0$...
> I couldn't past the file for some reason but I used
> dumpchk.exe on another machine and this is what it gave
> me.
>
> Nancy
>
> Probably caused by : ntoskrnl.exe ( nt+655b9 )
>
> Followup: MachineOwner
> ---------
>
> Finished dump check
>
> C:\Program Files\Debugging Tools for Windows>dumpchk -v
> e:Mini092704-03.dmp
> Loading dump file e:Mini092704-03.dmp
>
> Microsoft (R) Windows Debugger Version 6.3.0017.0
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [E:\Mini092704-03.dmp]
> Mini Kernel Dump File: Only registers and stack trace are
> available
>
> Symbol search path is: *** Invalid ***
> ************************************************** ********
> ******************
> * Symbol loading may be unreliable without a symbol
> search path. *
> * Use .symfix to have the debugger choose a symbol
> path. *
> * After setting your symbol path, use .reload to refresh
> symbol locations. *
> ************************************************** ********
> ******************
> Executable search path is:
> ************************************************** ********
> ***********
> * 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+ *
> ************************************************** ********
> ***********
> Unable to load image \WINDOWS\system32\ntoskrnl.exe,
> Win32 error 2
> *** WARNING: Unable to verify timestamp for ntoskrnl.exe
> *** ERROR: Module load completed but symbols could not be
> loaded for ntoskrnl.ex
> e
> Windows Server 2003 Kernel Version 3790 MP (2 procs) Free
> x86 compatible
> Product: Server, suite: TerminalServer SingleUserTS
> Kernel base = 0x804de000 PsLoadedModuleList = 0x8057b6a8
> Debug session time: Mon Sep 27 16:43:35 2004
> System Uptime: 0 days 0:00:30.421
> ************************************************** ********
> ***********
> * 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+ *
> ************************************************** ********
> ***********
> Unable to load image \WINDOWS\system32\ntoskrnl.exe,
> Win32 error 2
> *** WARNING: Unable to verify timestamp for ntoskrnl.exe
> *** ERROR: Module load completed but symbols could not be
> loaded for ntoskrnl.ex
> e
> Loading Kernel Symbols
> .................................................. ........
> ......................
> ...................
> Loading unloaded module list
> ...
> Loading User Symbols
> ************************************************** ********
> *********************
> *
> *
> * Bugcheck
> Analysis *
> *
> *
> ************************************************** ********
> *********************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck C2, {44, 0, 80000000, 0}
>
> ***** 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 ***
> ***
> ***
> ************************************************** ********
> ***************
> Probably caused by : ntoskrnl.exe ( nt+655b9 )
>
> Followup: MachineOwner
> ---------
>
> ----- 32 bit Kernel Mini Dump Analysis
>
> DUMP_HEADER32:
> MajorVersion 0000000f
> MinorVersion 00000ece
> KdSecondaryVersion 00000000
> DirectoryTableBase 3684c000
> PfnDataBase 80580078
> PsLoadedModuleList 8057b6a8
> PsActiveProcessHead 80581888
> MachineImageType 0000014c
> NumberProcessors 00000002
> BugCheckCode 000000c2
> BugCheckParameter1 00000044
> BugCheckParameter2 00000000
> BugCheckParameter3 80000000
> BugCheckParameter4 00000000
> PaeEnabled 00000000
> KdDebuggerDataBlock 805693d0
> ProductType 00000003
> SuiteMask 00000110
> WriterStatus 00000000
> MiniDumpFields 00000cff
>
> TRIAGE_DUMP32:
> ServicePackBuild 00000000
> SizeOfDump 00010000
> ValidOffset 0000fffc
> ContextOffset 00000320
> ExceptionOffset 000007d0
> MmOffset 00001068
> UnloadedDriversOffset 000010a0
> PrcbOffset 00001878
> ProcessOffset 00002648
> ThreadOffset 000028c0
> CallStackOffset 00002b20
> SizeOfCallStack 000003d0
> DriverListOffset 00003208
> DriverCount 00000064
> StringPoolOffset 00004fb8
> StringPoolSize 00001b28
> BrokenDriverOffset 00000000
> TriageOptions ffffffff
> TopOfStack ba906c30
> DebuggerDataOffset 00002ef0
> DebuggerDataSize 00000318
> DataBlocksOffset 00006ae0
> DataBlocksCount 00000004
> 00000000 - 00000fff at offset 00006b20
> f7737000 - f7737fff at offset 00007b20
> 8618c000 - 8618cfff at offset 00008b20
> 80543000 - 80543fff at offset 00009b20
> Max offset ab20, 54e0 from end of file
>
>
> Windows Server 2003 Kernel Version 3790 MP (2 procs) Free
> x86 compatible
> Product: Server, suite: TerminalServer SingleUserTS
> Kernel base = 0x804de000 PsLoadedModuleList = 0x8057b6a8
> Debug session time: Mon Sep 27 16:43:35 2004
> System Uptime: 0 days 0:00:30.421
> start end module name
> 804de000 80744000 nt Tue Mar 25 02:39:34 2003
> (3E8015C6)
> 80744000 8076c000 hal Tue Mar 25 01:07:28 2003
> (3E800030)
> b790b000 b7923000 Cdfs Tue Mar 25 02:17:19 2003
> (3E80108F)
> b7923000 b7936000 Fips Tue Mar 25 02:54:59 2003
> (3E801963)
> b7936000 b79a3000 mrxsmb Tue Mar 25 01:09:09 2003
> (3E800095)
> b8de3000 b8e0f000 rdbss Tue Mar 25 01:09:06 2003
> (3E800092)
> ba34e000 ba383000 netbt Fri Jul 18 12:16:03 2003
> (3F182B53)
> ba383000 ba3e5000 tcpip Tue Mar 25 02:04:01 2003
> (3E800D71)
> ba6fb000 ba717000 ipsec Tue Mar 25 01:55:45 2003
> (3E800B81)
> bf800000 bf9c6000 win32k Tue Mar 25 02:40:49 2003
> (3E801611)
> bf9c6000 bfa1c680 ati2drad Tue Mar 25 03:43:37 2003
> (3E8024C9)
> bff80000 bff96000 dxg Tue Mar 25 03:46:23 2003
> (3E80256F)
> f3842000 f3855000 usbhub Tue Mar 25 01:10:46 2003
> (3E8000F6)
> f3855000 f3888000 update Tue Mar 25 02:59:59 2003
> (3E801A8F)
> f3d7c000 f3db0000 rdpdr Tue Mar 25 01:09:30 2003
> (3E8000AA)
> f40e2000 f40f0000 NDProxy Tue Mar 25 01:11:30 2003
> (3E800122)
> f42d8000 f42df000 dxgthk Tue Mar 25 01:05:52 2003
> (3E7FFFD0)
> f47ce000 f47dd000 termdd Tue Mar 25 01:02:52 2003
> (3E7FFF1C)
> f4905000 f4906580 USBD Tue Mar 25 01:10:39 2003
> (3E8000EF)
> f4988000 f4989000 swenum Wed Dec 04 11:10:07 2002
> (3DEE36EF)
> f4ce9000 f4cf1000 rasacd Tue Mar 25 01:11:50 2003
> (3E800136)
> f4dcb000 f4dd3000 mnmdd Tue Mar 25 01:07:53 2003
> (3E800049)
> f57ae000 f57b6000 RDPCDD Tue Mar 25 01:03:05 2003
> (3E7FFF29)
> f57b6000 f57bd000 Null Tue Mar 25 01:03:05 2003
> (3E7FFF29)
> f57ce000 f57d6000 Fs_Rec Tue Mar 25 01:08:36 2003
> (3E800074)
> f5b63000 f5b70000 netbios Tue Mar 25 01:09:53 2003
> (3E8000C1)
> f5b73000 f5b7d000 Dxapi Tue Mar 25 01:06:01 2003
> (3E7FFFD9)
> f619c000 f61a6000 flpydisk Tue Mar 25 01:04:32 2003
> (3E7FFF80)
> f63d6000 f63d9bc0 dump_cpqcissm Mon Feb 10 16:34:54
> 2003 (3E48290E)
> f64a7000 f64b6000 msgpc Tue Mar 25 01:10:12 2003
> (3E8000D4)
> f64c7000 f64dc000 raspptp Tue Mar 25 02:19:09 2003
> (3E8010FD)
> f6540000 f655b000 ndiswan Tue Mar 25 02:48:19 2003
> (3E8017D3)
> f655b000 f6572000 rasl2tp Tue Mar 25 01:54:46 2003
> (3E800B46)
> f673a000 f6747000 wanarp Tue Mar 25 01:11:22 2003
> (3E80011A)
> f678a000 f6796000 Npfs Tue Mar 25 01:08:59 2003
> (3E80008B)
> f679a000 f67a4000 Msfs Tue Mar 25 01:08:56 2003
> (3E800088)
> f682b000 f683b5a0 CPQCISSE Tue Feb 18 11:22:11 2003
> (3E526BC3)
> f683c000 f685de80 USBPORT Tue Mar 25 01:10:43 2003
> (3E8000F3)
> f685e000 f687dd00 ks Wed Dec 04 11:09:38 2002
> (3DEE36D2)
> f687e000 f6892000 redbook Tue Mar 25 01:04:38 2003
> (3E7FFF86)
> f6892000 f68a6000 cdrom Tue Mar 25 01:05:18 2003
> (3E7FFFAE)
> f68a6000 f68be000 serial Tue Mar 25 01:40:08 2003
> (3E8007D8)
> f68be000 f68d5000 parport Tue Mar 25 01:03:56 2003
> (3E7FFF5C)
> f68d5000 f68eb000 i8042prt Tue Mar 25 03:01:43 2003
> (3E801AF7)
> f68eb000 f692f780 cpqasm Thu Mar 20 15:50:13 2003
> (3E7A3795)
> f6b9b000 f6bc8700 q57xp32 Thu May 20 11:44:36 2004
> (40ACE074)
> f6bc9000 f6be2000 VIDEOPRT Tue Mar 25 01:08:02 2003
> (3E800052)
> f6be2000 f6c35d80 ati2mpad Thu Jul 18 20:13:20 2002
> (3D3767B0)
> f6e19000 f6e22000 raspti Tue Mar 25 01:11:36 2003
> (3E800128)
> f6e29000 f6e34000 ptilink Tue Mar 25 01:03:51 2003
> (3E7FFF57)
> f6e39000 f6e44000 TDI Tue Mar 25 01:14:28 2003
> (3E8001D4)
> f6e49000 f6e57000 raspppoe Tue Mar 25 01:11:37 2003
> (3E800129)
> f7222000 f7244000 Mup Tue Mar 25 02:55:58 2003
> (3E80199E)
> f7244000 f7285000 NDIS Tue Mar 25 02:45:35 2003
> (3E80172F)
> f7285000 f7322000 Ntfs Tue Mar 25 01:40:05 2003
> (3E8007D5)
> f7322000 f7343000 KSecDD Tue Mar 25 01:05:39 2003
> (3E7FFFC3)
> f7343000 f7359000 CLASSPNP Tue Mar 25 01:38:14 2003
> (3E800766)
> f7359000 f736de80 adpu160m Thu Jun 20 21:02:53 2002
> (3D12894D)
> f736e000 f738a000 atapi Tue Mar 25 01:04:48 2003
> (3E7FFF90)
> f738a000 f73b0000 SCSIPORT Tue Mar 25 02:01:25 2003
> (3E800CD5)
> f73b0000 f73d1000 volsnap Tue Mar 25 01:05:47 2003
> (3E7FFFCB)
> f73d1000 f73fb000 dmio Tue Mar 25 01:08:14 2003
> (3E80005E)
> f73fb000 f7420000 ftdisk Tue Mar 25 01:05:26 2003
> (3E7FFFB6)
> f7420000 f7435000 pci Tue Mar 25 01:16:40 2003
> (3E800258)
> f7435000 f7466000 ACPI Tue Mar 25 01:16:21 2003
> (3E800245)
> f7487000 f7490000 WMILIB Tue Mar 25 01:13:00 2003
> (3E80017C)
> f7497000 f74a6000 isapnp Tue Mar 25 01:16:35 2003
> (3E800253)
> f74a7000 f74b4000 PCIIDEX Tue Mar 25 01:04:44 2003
> (3E7FFF8C)
> f74b7000 f74c6000 MountMgr Tue Mar 25 01:03:05 2003
> (3E7FFF29)
> f74c7000 f74d5000 PartMgr Tue Mar 25 02:04:02 2003
> (3E800D72)
> f74d7000 f74e6ae0 cpq32fs2 Mon Nov 18 17:47:47 2002
> (3DD97C23)
> f74e7000 f74ef080 symc8xx Tue Sep 25 13:25:49 2001
> (3BB0CC2D)
> f74f7000 f7500100 symmpi Tue Dec 10 11:32:15 2002
> (3DF6251F)
> f7507000 f7516000 disk Tue Mar 25 01:05:20 2003
> (3E7FFFB0)
> f7517000 f7523000 Dfs Tue Mar 25 01:09:52 2003
> (3E8000C0)
> f7527000 f7530000 crcdisk Tue Mar 25 01:07:23 2003
> (3E80002B)
> f7547000 f7550000 ndistapi Tue Mar 25 01:11:28 2003
> (3E800120)
> f7557000 f7563000 processr Tue Mar 25 01:07:36 2003
> (3E800038)
> f7567000 f7570000 watchdog Tue Mar 25 01:09:01 2003
> (3E80008D)
> f7647000 f7651000 kbdclass Tue Mar 25 01:03:10 2003
> (3E7FFF2E)
> f7657000 f7661000 mouclass Tue Mar 25 01:03:09 2003
> (3E7FFF2D)
> f7667000 f7671000 serenum Tue Mar 25 01:04:01 2003
> (3E7FFF61)
> f7677000 f7682000 fdc Tue Mar 25 01:04:31 2003
> (3E7FFF7F)
> f76a7000 f76b3000 vga Tue Mar 25 01:08:03 2003
> (3E800053)
> f76f7000 f7700000 dump_diskdump Tue Mar 25 01:05:15
> 2003 (3E7FFFAB)
> f7707000 f770f000 kdcom Tue Mar 25 01:08:00 2003
> (3E800050)
> f770f000 f7717000 BOOTVID Tue Mar 25 01:07:58 2003
> (3E80004E)
> f7717000 f771e000 pciide Tue Mar 25 01:04:46 2003
> (3E7FFF8E)
> f771f000 f7726000 dmload Tue Mar 25 01:08:08 2003
> (3E800058)
> f7727000 f772e080 sym_hi Wed Oct 03 18:48:12 2001
> (3BBBA3BC)
> f772f000 f7733c20 ino_flpy Fri May 18 12:36:22 2001
> (3B055D96)
> f7747000 f774f000 OPRGHDLR Tue Mar 25 01:16:25 2003
> (3E800249)
> f7787000 f778b200 usbohci Tue Mar 25 01:10:41 2003
> (3E8000F1)
> f778f000 f7797000 audstub Tue Mar 25 01:09:12 2003
> (3E800098)
> f784f000 f7856000 Beep Tue Mar 25 01:03:04 2003
> (3E7FFF28)
> f7857000 f785bae0 sonysdx Tue Sep 02 09:39:43 2003
> (3F54ABAF)
> f7897000 f789ab60 cpqarray Mon Oct 21 16:18:51 2002
> (3DB46F3B)
> f789b000 f789ef80 symc810 Fri Dec 08 11:40:59 2000
> (3A311D2B)
> f789f000 f78a2bc0 cpqcissm Mon Feb 10 16:34:54 2003
> (3E48290E)
> f78a3000 f78a6460 cpqarry2 Mon Nov 05 15:47:33 2001
> (3BE708F5)
>
> Unloaded modules:
> f6df9000 f6e07000 imapi.sys
> Timestamp: unavailable (00000000)
> Checksum: 00000000
> f453f000 f4542000 scsichng.sys
> Timestamp: unavailable (00000000)
> Checksum: 00000000
> f4db3000 f4dbb000 Sfloppy.SYS
> Timestamp: unavailable (00000000)
> Checksum: 00000000
> ************************************************** ********
> *********************
> *
> *
> * Bugcheck
> Analysis *
> *
> *
> ************************************************** ********
> *********************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck C2, {44, 0, 80000000, 0}
>
> ***** 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 ***
> ***
> ***
> ************************************************** ********
> ***************
> Probably caused by : ntoskrnl.exe ( nt+655b9 )
>
> Followup: MachineOwner
> ---------
>
> Finished dump check
>
> C:\Program Files\Debugging Tools for Windows>
> >-----Original Message-----
> >Look for a file in C:\Windows\Minidump called

> Mini<MostRecentDate>.dmp.
> >Paste it's conents in your reply to this message to the

> group. You have a
> >bad device driver causing your system to crash, and you

> proved that by going
> >into Safe Mode successfully. If I had to guess I'd say

> it was your sound
> >driver.
> >
> >--
> >Todd J Heron, MCSE
> >Windows 2003/2000/NT
> >
> ><> wrote in message
> >news:256d01c4a4db$69caada0$...
> >> I sure hope you can help. After re-booting my windows
> >> 2003 server due to security updates, I get the

> following
> >> blue screen.
> >>
> >> bad_pool_caller
> >>
> >> stop: 0x000000c2 (0x00000044, 0x00000000, 0x80000000,
> >> 0x00000000)
> >>
> >> I can access the machine in safe mode, I have tried to
> >> uninstall the recent update and I am still getting the
> >> same message. I have tried to install
> >>

> http://www.microsoft.com/whdc/devtoo...ging/default.m
> >> spx but since I am in safe mode, the installer is not
> >> working. If you have any suggestions, please help.
> >>
> >> Nancy

> >
> >
> >.
> >



 
Reply With Quote
 
raymond_chad
Guest
Posts: n/a

 
      06-04-2005

Same problem only i am installing XP so cant do anything

p4 3.2
512 pc3200
40gb ata
120gb ata
asus p4p800-e mboard
Need some help Please


--
raymond_chad
------------------------------------------------------------------------
raymond_chad's Profile: http://extremetechsupport.com/forum/...ml?userid=1193
View this thread: http://extremetechsupport.com/forum/....phtml?t=90996

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

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

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




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 47 48 49 50 51 52 53 54 55 56 57 58 59