Posted by Grant Foraker on July 04, 2006 at 08:15:16:
Over the last month or two I've had three BSOD on my Win2003 server. Via a blog, I got the steps to install and run the MS debugger that works with the memory.dmp file created by the BSOD. According to the blog, 80% of driver problems are determined just by viewing the opening screen.
=====================================================================Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [\\SSASD00\Users\Grant\My Documents\MemoryDump\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 UP Free x86 compatible
Product: LanManNt, suite: SmallBusiness TerminalServer SmallBusinessRestricted SingleUserTS
Built by: 3790.srv03_gdr.050225-1827
Kernel base = 0x804de000 PsLoadedModuleList = 0x80568c08
Debug session time: Tue Jun 27 19:45:35.913 2006 (GMT-7)
System Uptime: 8 days 11:38:32.553
Loading Kernel Symbols
........................................................................................................
Loading User Symbols
..........................................................
Loading unloaded module list
..
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck B8, {8562bda0, 85449570, 0, 0}
*** ERROR: Module load completed but symbols could not be loaded for CBUSB.sys
Probably caused by : CBUSB.sys ( CBUSB+be6 )
Followup: MachineOwner
---------
=====================================================================
CBUSB.SYS is implicated as the "bad" driver. The version delivered by CSP is 2.04.929. At this point I remembered that my XP workstation had received a new CBUSB.SYS via Windows Update. That version is 2.06.511. Apparently, Marx or MS doesn't think that CBUSB.SYS is used on Win2003 server so there's no update on Windows update.
I've manually replaced the CBUSB.SYS on my server with the newer version and am waiting to see if I get another BSOD.
Lastly, when I installed the CSP 6.08 the new CBUSB.SYS was overwritten by the install. Shouldn't there be a warning?