Hoping someone can help me out with this.

It is my personal laptop with a fairly fresh install of XP Pro on it. Here are the computer details.

Toshiba Satellite M105-S3041
Intel® Core™ Solo Processor T1350
o 1.86GHz, 2MB L2, 533MHz FSB
• Mobile Intel® 945GM Express Chipset
• Intel® PRO/Wireless 3945ABG (802.11a/b/g)
• Configured with 512MB DDR2 SDRAM, PC4200 533MHz or PC5300 677MHz DDR2 SDRAM,
dual-channel support requires two memory modules of same capacity and clockspeed
• 80GB (5400 RPM) Serial-ATA (SATA) hard disk drive; 9.5mm height
• DVD SuperMulti (+/-R double layer) drive supporting 11 formats
• Intel® Graphics Media Accelerator 950 with 8MB-128MB dynamically allocated shared graphics memory
• Realtek ALC861 16-bit stereo software sound
• Toshiba V.92 software modem9
• Intel® PRO/100 VE Network Connection - 10/100 Base-TX Ethernet
• Integrated Intel® PRO/Wireless Network Connection 3945ABG (802.11a/b/g) 10

Fresh install of XP Pro with the following software;
Norton Ghost 2003
Office 2003
Active Sync 4.2
Adobe Professional 7.0
Nero Ultra 7.0
Quicken 98 & 2003
Quickbooks 2003
Firefox 2.0
Intervideo WinDVD
Intervideo WinDVD Creator 2
System Mechanic 7.0
Perfect Disk 8.0
Avast! Antivirus
Counterspy
Comodo Firewall
CCleaner
X-Setup Pro 6.6

This is the only Debug info I could pull. I really cannot understand much, other than the obvious REGISTRY ERROR piece. I have also attached a picture of the blue screen and the memory dump files.

Well it looks like I cannot attach the memory dump since the laptop was setup to do a full dump and the file is 1.8mb zipped.

Thanks for any assistance you can provide. Tim
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
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 = 0x8055a420
Debug session time: Wed Jan 17 06:27:54.093 2007 (GMT-7)
System Uptime: 0 days 7:50:04.656
Loading Kernel Symbols
...................................................................................................................................................
Loading User Symbols
....................................................................
Loading unloaded module list
.....................................
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 51, {4, 1, e2fdd440, 238}

*** WARNING: Unable to verify checksum for IOLOSM~1.DLL
*** ERROR: Symbol file could not be found. Defaulted to export symbols for IOLOSM~1.DLL -
*** ERROR: Module load completed but symbols could not be loaded for SMSystemAnalyzer.exe
Probably caused by : ntoskrnl.exe ( nt!CmpAssignSecurityToKcb+3f )

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

kd> .reload
Loading Kernel Symbols
...................................................................................................................................................
Loading User Symbols
....................................................................
Loading unloaded module list
.....................................
kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

REGISTRY_ERROR (51)
Something has gone badly wrong with the registry. If a kernel debugger
is available, get a stack trace. It can also indicate that the registry got
an I/O error while trying to read one of its files, so it can be caused by
hardware problems or filesystem corruption.
It may occur due to a failure in a refresh operation, which is used only
in by the security system, and then only when resource limits are encountered.
Arguments:
Arg1: 00000004, (reserved)
Arg2: 00000001, (reserved)
Arg3: e2fdd440, depends on where Windows bugchecked, may be pointer to hive
Arg4: 00000238, depends on where Windows bugchecked, may be return code of
HvCheckHive if the hive is corrupt.

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

*** WARNING: Unable to verify checksum for IOLOSM~1.DLL
*** ERROR: Symbol file could not be found. Defaulted to export symbols for IOLOSM~1.DLL -
*** ERROR: Module load completed but symbols could not be loaded for SMSystemAnalyzer.exe

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x51

PROCESS_NAME: SMSystemAnalyze

LAST_CONTROL_TRANSFER: from 8060c0ce to 8053331e

STACK_TEXT:
a9ce590c 8060c0ce 00000051 00000004 00000001 nt!KeBugCheckEx+0x1b
a9ce5930 8058b6aa 00000006 00000238 c9988e4c nt!CmpAssignSecurityToKcb+0x3f
a9ce5958 8058a121 e16d9588 00a07e48 c9988e4c nt!CmpCreateKeyControlBlock+0x1b5
a9ce59a8 805677a0 e16d9588 00a07e48 c9988e4c nt!CmpDoOpen+0xf4
a9ce5ba0 805674b5 00a07e48 00a07e48 8138d2d8 nt!CmpParseKey+0x558
a9ce5c28 8056729a 0000002c a9ce5c68 00000040 nt!ObpLookupObjectName+0x119
a9ce5c7c 80567bfd 00000000 823c3560 80566b01 nt!ObOpenObjectByName+0xeb
a9ce5d50 804de7ec 016afa78 00020019 016af9d4 nt!NtOpenKey+0x1af
a9ce5d50 7c90eb94 016afa78 00020019 016af9d4 nt!KiFastCallEntry+0xf8
016af9b0 7c90dd48 77dd6a13 016afa78 00020019 ntdll!KiFastSystemCallRet
016af9b4 77dd6a13 016afa78 00020019 016af9d4 ntdll!ZwOpenKey+0xc
016afa14 77dd76eb 0000002c 016afa3c 00000000 advapi32!LocalBaseRegOpenKey+0xe4
016afa48 131970af 80000002 090847b4 00000000 advapi32!RegOpenKeyExA+0x119
WARNING: Stack unwind information not available. Following frames may be wrong.
016afa88 132fd6f1 016afa9c 132fd79b 016afafc IOLOSM_1!DllUnregisterServer+0x36377
016afafc 132fd773 0bf3bb01 016afb14 132fd79b IOLOSM_1!DllUnregisterServer+0x19c9b9
016afb74 132fd773 0a317401 016afb8c 132fd79b IOLOSM_1!DllUnregisterServer+0x19ca3b
016afbec 132fd773 07bda501 016afc04 132fd79b IOLOSM_1!DllUnregisterServer+0x19ca3b
016afc64 132fd773 0c8d7b01 016afc7c 132fd79b IOLOSM_1!DllUnregisterServer+0x19ca3b
016afcdc 132fda04 09397201 016afd0c 132fda35 IOLOSM_1!DllUnregisterServer+0x19ca3b
016afd04 132fcf93 016afd58 132fcfb9 016afd28 IOLOSM_1!DllUnregisterServer+0x19cccc
016afd28 13360ff4 133614c4 0c055e9c 00000001 IOLOSM_1!DllUnregisterServer+0x19c25b
016afd50 132fd018 016afda8 132fd02e 016afd68 IOLOSM_1!DllUnregisterServer+0x2002bc
016afd68 133611ff 1336109c 0c055e9c 13361b64 IOLOSM_1!DllUnregisterServer+0x19c2e0
016afdc4 1336a80c 0b2ede6c 00000000 134218b6 IOLOSM_1!DllUnregisterServer+0x2004c7
016afe1c 00564b64 016afe30 00564b6e 016afe5c IOLOSM_1!DllUnregisterServer+0x209ad4
016afe5c 00563093 016afe70 005630b4 016afe88 SMSystemAnalyzer+0x164b64
016afe88 00563345 016afe9c 0056336b 016afebc SMSystemAnalyzer+0x163093
016afebc 00563fac 016afed0 00563fd2 016afee0 SMSystemAnalyzer+0x163345
016afee0 00565d37 016afef4 00565d49 016aff14 SMSystemAnalyzer+0x163fac
016aff14 00565545 016aff38 005655c3 016aff2c SMSystemAnalyzer+0x165d37
016aff2c 0056571f 016aff70 016aff78 0056575e SMSystemAnalyzer+0x165545
016aff70 004253db 016aff84 004253e5 016affa0 SMSystemAnalyzer+0x16571f
016affa0 00404c22 016affdc 00404754 016affb4 SMSystemAnalyzer+0x253db
016affb4 7c80b683 00e9e804 00000020 00000001 SMSystemAnalyzer+0x4c22
016affec 00000000 00404bf8 00e9e804 00000000 kernel32!BaseThreadStart+0x37


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!CmpAssignSecurityToKcb+3f
8060c0ce ff33 push dword ptr [ebx]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!CmpAssignSecurityToKcb+3f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9

FAILURE_BUCKET_ID: 0x51_nt!CmpAssignSecurityToKcb+3f

BUCKET_ID: 0x51_nt!CmpAssignSecurityToKcb+3f

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

Refer this document

Thanks for the link. Scarey procedure by the look of it.

As I mentioned before I have System Mechanic 7.0 on this machine and I am new to that software. Dug into it and found the deep scan option and ran it. It found about 125 registry errors which I had it fix. The unit has been stable for over 24 hours now so I guess the test now is time.

Thanks, Tim