mce 2005 rollup2 known issues?

[lar282]

Hi
is there any known issues with running daemon tools on a mce2005 system? I keep getting bsod:s with 3.47 but not really sure why?



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


Loading Dump File [D:\debug\dreambox\Mini020606-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*d:\debug\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: d:\debug\i386
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Mon Feb 6 21:47:05.609 2006 (GMT+1)
System Uptime: 0 days 0:42:22.179
Loading Kernel Symbols
.................................................. .................................................. .................................
Loading unloaded module list
...............
Loading User Symbols
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000BE, {b85f0ab4, 1a67d121, b8570808, b}

Unable to load image d347bus.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for d347bus.sys
*** ERROR: Module load completed but symbols could not be loaded for d347bus.sys
Probably caused by : d347bus.sys ( d347bus+d887 )

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

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

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: b85f0ab4, Virtual address for the attempted write.
Arg2: 1a67d121, PTE contents.
Arg3: b8570808, (reserved)
Arg4: 0000000b, (reserved)

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


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xBE

LAST_CONTROL_TRANSFER: from 805720d4 to 805729ed

STACK_TEXT:
b8570898 805720d4 e1035758 e219a8fc e1444264 nt!CmpQueryKeyValueData+0x12b
b85708fc 8057227b e27c1050 000a0008 b8570c24 nt!CmQueryValueKey+0xb9
b85709a4 f7827887 80001928 b8570a80 00000002 nt!NtQueryValueKey+0x2cc
WARNING: Stack unwind information not available. Following frames may be wrong.
b85709d0 804dd99f 80001928 b8570a80 00000002 d347bus+0xd887
b85709d0 804e4067 80001928 b8570a80 00000002 nt!KiFastCallEntry+0xfc
b8570a60 8064be9b 80001928 b8570a80 00000002 nt!ZwQueryValueKey+0x11
b8570bb8 80610fd6 b8570c1c 00000000 7c97c038 nt!ExpIsValidUILanguage+0xcd
b8570d14 80587b9d 80587bb8 7c97c038 00000001 nt!ExpGetCurrentUserUILanguage+0x108
b8570d58 804dd99f 7c97c038 00cef348 7c90eb94 nt!NtQueryDefaultUILanguage+0x49
b8570d58 7c90eb94 7c97c038 00cef348 7c90eb94 nt!KiFastCallEntry+0xfc
00cef348 00000000 00000000 00000000 00000000 0x7c90eb94


FOLLOWUP_IP:
d347bus+d887
f7827887 ?? ???

SYMBOL_STACK_INDEX: 3

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: d347bus+d887

MODULE_NAME: d347bus

IMAGE_NAME: d347bus.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4128a01d

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0xBE_d347bus+d887

BUCKET_ID: 0xBE_d347bus+d887

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



regards
lasse