We’d like to remind Forumites to please avoid political debate on the Forum.
This is to keep it a safe and useful space for MoneySaving discussions. Threads that are – or become – political in nature may be removed in line with the Forum’s rules. Thank you for your understanding.
📨 Have you signed up to the Forum's new Email Digest yet? Get a selection of trending threads sent straight to your inbox daily, weekly or monthly!
Bad Pool Caller error blue screen...
Comments
-
OK - just went to look at the memory dump file but couldn't find it as I use CCleaner and this was set to delete 'Memory Dumps'. So I will have to wait and see if it Blue Screens again after all!
No problem. Glad to see you're giving it a shot. Any questions, either post them back here or PM me.0 -
Had another blue screen today. Have followed your advice and run WinDbg. Not sure what to do next.
It suggests Driver Fault for CM102.sys
Help appreciated!!!
Microsoft (R) Windows De!!!!!! Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available
************************************************************
WARNING: Dump file has been truncated. Data may be missing.
************************************************************
Symbol search path is: SRV*c:\*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Tue May 12 12:54:26.875 2009 (GMT+1)
System Uptime: 0 days 0:00:36.458
Loading Kernel Symbols
...............................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {80000003, 804e3586, bafdfcac, bafdf9a8}
Probably caused by : CM102.sys ( CM102+182f78 )
Followup: MachineOwner
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: 80000003, The exception code that was not handled
Arg2: 804e3586, The address that the exception occurred at
Arg3: bafdfcac, Exception Record Address
Arg4: bafdf9a8, Context Record Address
Debugging Details:
EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid
FAULTING_IP:
nt!DbgBreakPoint+0
804e3586 cc int 3
EXCEPTION_RECORD: bafdfcac -- (.exr 0xffffffffbafdfcac)
ExceptionAddress: 804e3586 (nt!DbgBreakPoint)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000000
Parameter[1]: 00000000
Parameter[2]: 80010031
CONTEXT: bafdf9a8 -- (.cxr 0xffffffffbafdf9a8)
eax=00000102 ebx=899bae50 ecx=00000000 edx=80010031 esi=899baec8 edi=899bad38
eip=804e3586 esp=bafdfd74 ebp=bafdfd94 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000246
nt!DbgBreakPoint:
804e3586 cc int 3
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x7E
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 00000000
EXCEPTION_PARAMETER3: 80010031
LAST_CONTROL_TRANSFER: from b7df5f78 to 804e3586
STACK_TEXT:
bafdfd70 b7df5f78 00000000 00000002 899bad38 nt!DbgBreakPoint
WARNING: Stack unwind information not available. Following frames may be wrong.
bafdfd94 b7d3dbff 00000000 89b55930 00000000 CM102+0x182f78
bafdfdac 8057aeff 899bad38 00000000 00000000 CM102+0xcabff
bafdfddc 804f88ea b7df6100 899bad38 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
CM102+182f78
b7df5f78 8bf3 mov esi,ebx
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: CM102+182f78
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: CM102
IMAGE_NAME: CM102.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45596013
STACK_COMMAND: .cxr 0xffffffffbafdf9a8 ; kb
FAILURE_BUCKET_ID: 0x7E_CM102+182f78
BUCKET_ID: 0x7E_CM102+182f78
Followup: MachineOwner
0
This discussion has been closed.
Confirm your email address to Create Threads and Reply

Categories
- All Categories
- 351.7K Banking & Borrowing
- 253.4K Reduce Debt & Boost Income
- 454K Spending & Discounts
- 244.7K Work, Benefits & Business
- 600.2K Mortgages, Homes & Bills
- 177.3K Life & Family
- 258.4K Travel & Transport
- 1.5M Hobbies & Leisure
- 16.2K Discuss & Feedback
- 37.6K Read-Only Boards