BATTC.sys blue screen please help!
Hi everyone im new here, I have a problem with BoSD im getting something about BATTC.sys and i hope someone can help me with it, heres the crash log from minidump folder:
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini101307-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\local cache
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Oct 13 00:32:55.484 2007 (GMT+2)
System Uptime: 0 days 4:36:50.171
Loading Kernel Symbols
.................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {0, 2, 0, f789fa20}
Probably caused by : BATTC.SYS ( BATTC!BattCQueueWorker+c )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f789fa20, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 00000000
CURRENT_IRQL: 2
FAULTING_IP:
BATTC!BattCQueueWorker+c
f789fa20 8b3e mov edi,dword ptr [esi]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from f789fb6c to f789fa20
STACK_TEXT:
f78eacb8 f789fb6c 00000000 00000001 849057e8 BATTC!BattCQueueWorker+0xc
f78eacc8 804f14fb 00000000 849057e8 84ac5398 BATTC!BattCCancelStatus+0x12
f78eace0 f789c31f 849057e8 e15be8a0 e15be870 nt!IoCancelIrp+0x65
f78ead14 f78a0558 00000578 00000001 0000058e compbatt!CompBattSetStatusNotify+0x223
f78ead60 f78a09da 84ac51b8 005be870 84ac5250 BATTC!BattCCheckStatusQueue+0x292
f78ead7c 805379bd 84ac51b8 00000000 84b083c8 BATTC!BattCWorkerThread+0x11a
f78eadac 805ce84c 84ac51b8 00000000 00000000 nt!ExpWorkerThread+0xef
f78eaddc 8054532e 805378ce 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
BATTC!BattCQueueWorker+c
f789fa20 8b3e mov edi,dword ptr [esi]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: BATTC
IMAGE_NAME: BATTC.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 3b7d8550
SYMBOL_NAME: BATTC!BattCQueueWorker+c
FAILURE_BUCKET_ID: 0xD1_BATTC!BattCQueueWorker+c
BUCKET_ID: 0xD1_BATTC!BattCQueueWorker+c
Followup: MachineOwner
---------
i have 2 more crash logs if anyone needs more to be certain of the problem.
oh and yes i have tested my memory with the windows memtest problem (let it run for a whole night) , result: no problems found.
also got a system recovered from a serious error message (not blue screen no reboot) here it is from the event viewer.
Error code 100000d1, parameter1 00000000, parameter2 00000002, parameter3 00000000, parameter4 f789fa20.
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 64 100000d
0020: 31 20 20 50 61 72 61 6d 1 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 30 2c 20 000000,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 66 37 38 39 00, f789
0050: 66 61 32 30 fa20
if anyone needs more info please tell me.
Hi everyone im new here, I have a problem with BoSD im getting something about BATTC.sys and i hope someone can help me with it, heres the crash log from minidump folder:
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini101307-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\local cache
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Oct 13 00:32:55.484 2007 (GMT+2)
System Uptime: 0 days 4:36:50.171
Loading Kernel Symbols
.................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {0, 2, 0, f789fa20}
Probably caused by : BATTC.SYS ( BATTC!BattCQueueWorker+c )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f789fa20, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 00000000
CURRENT_IRQL: 2
FAULTING_IP:
BATTC!BattCQueueWorker+c
f789fa20 8b3e mov edi,dword ptr [esi]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from f789fb6c to f789fa20
STACK_TEXT:
f78eacb8 f789fb6c 00000000 00000001 849057e8 BATTC!BattCQueueWorker+0xc
f78eacc8 804f14fb 00000000 849057e8 84ac5398 BATTC!BattCCancelStatus+0x12
f78eace0 f789c31f 849057e8 e15be8a0 e15be870 nt!IoCancelIrp+0x65
f78ead14 f78a0558 00000578 00000001 0000058e compbatt!CompBattSetStatusNotify+0x223
f78ead60 f78a09da 84ac51b8 005be870 84ac5250 BATTC!BattCCheckStatusQueue+0x292
f78ead7c 805379bd 84ac51b8 00000000 84b083c8 BATTC!BattCWorkerThread+0x11a
f78eadac 805ce84c 84ac51b8 00000000 00000000 nt!ExpWorkerThread+0xef
f78eaddc 8054532e 805378ce 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
BATTC!BattCQueueWorker+c
f789fa20 8b3e mov edi,dword ptr [esi]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: BATTC
IMAGE_NAME: BATTC.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 3b7d8550
SYMBOL_NAME: BATTC!BattCQueueWorker+c
FAILURE_BUCKET_ID: 0xD1_BATTC!BattCQueueWorker+c
BUCKET_ID: 0xD1_BATTC!BattCQueueWorker+c
Followup: MachineOwner
---------
i have 2 more crash logs if anyone needs more to be certain of the problem.
oh and yes i have tested my memory with the windows memtest problem (let it run for a whole night) , result: no problems found.
also got a system recovered from a serious error message (not blue screen no reboot) here it is from the event viewer.
Error code 100000d1, parameter1 00000000, parameter2 00000002, parameter3 00000000, parameter4 f789fa20.
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 64 100000d
0020: 31 20 20 50 61 72 61 6d 1 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 30 2c 20 000000,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 66 37 38 39 00, f789
0050: 66 61 32 30 fa20
if anyone needs more info please tell me.
