Has anyone ever seen anything like this?

[Loren_Wilton]

My partner has a machine that seemingly just doesn’t like to be debugged.

The machine is a dual x64 machine, but it is running XP Pro 32 bit.

When I connect windbg from my machine to this thing using a standard serial
debugging cable and then reboot the dual processor machine (specifying
/debugport=com1 /baudrate=115200) it comes up and s.l.o.w.l.y gets around to
showing a connect message in the debugger. Then nothing.

If I turn on verbose debugging I can see it s.l.o.w.l.y loading – and
unloading – multiple times – assorted modules. After about 20 minutes it
will finally load KSecDD. Then nothing. Ever.

If my partner tries debugging this from another machine she sais it doesn’t
even get that far before it stops. However, if run without the debugger,
the machine runs fine!

I’ve tried to break into the debug session, and tried setting initial
breakpoint. Neither result in a breakpoint. I’ve tried different baudrates
in case the machine is having a serial port problem. Nada.

So. Anyone seen something like this? Even better: have you seen it and
figured out what is going wrong, or what to do about it?

Thanks,

Loren

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

Opened \.\com1
Waiting to reconnect…
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is:
SRV*g:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
System Uptime: not available
Verbose mode ON.
ModLoad: bada8000 bada9b80 kdcom.dll
Force unload of kdcom.dll
ModLoad: bada8000 bada9b80 kdcom.dll
ModLoad: bacb8000 bacbb000 BOOTVID.dll
ModLoad: ba779000 ba7a6d80 ACPI.sys
ModLoad: badaa000 badab100 WMILIB.SYS
ModLoad: ba768000 ba778a80 pci.sys
Force unload of pci.sys
ModLoad: ba768000 ba778a80 pci.sys
Force unload of pci.sys
ModLoad: ba768000 ba778a80 pci.sys
ModLoad: ba8a8000 ba8b0c00 isapnp.sys
ModLoad: ba8b8000 ba8c6e80 ohci1394.sys
ModLoad: ba8c8000 ba8d5000 1394BUS.SYS
ModLoad: bae70000 bae70d00 pciide.sys
ModLoad: bab28000 bab2e200 PCIIDEX.SYS
Force unload of PCIIDEX.SYS
ModLoad: bab28000 bab2e200 PCIIDEX.SYS
ModLoad: ba8d8000 ba8e2500 MountMgr.sys
ModLoad: ba749000 ba767880 ftdisk.sys
Force unload of ftdisk.sys
ModLoad: ba749000 ba767880 ftdisk.sys
Force unload of ftdisk.sys
ModLoad: ba749000 ba767880 ftdisk.sys
Force unload of ftdisk.sys
ModLoad: ba749000 ba767880 ftdisk.sys
Force unload of ftdisk.sys
ModLoad: ba749000 ba767880 ftdisk.sys
ModLoad: badac000 badad700 dmload.sys
ModLoad: ba723000 ba748700 dmio.sys
ModLoad: bab30000 bab34900 PartMgr.sys
ModLoad: ba8e8000 ba8f4000 amdbusdr.sys
ModLoad: ba8f8000 ba904c80 VolSnap.sys
Force unload of VolSnap.sys
ModLoad: ba8f8000 ba904c80 VolSnap.sys
Force unload of VolSnap.sys
ModLoad: ba8f8000 ba904c80 VolSnap.sys
ModLoad: ba70b000 ba722480 atapi.sys
ModLoad: bab38000 bab3c380 mraid35x.sys
Force unload of mraid35x.sys
ModLoad: bab38000 bab3c380 mraid35x.sys
ModLoad: ba6f3000 ba70a800 SCSIPORT.SYS
Force unload of SCSIPORT.SYS
ModLoad: ba6f3000 ba70a800 SCSIPORT.SYS
Force unload of SCSIPORT.SYS
ModLoad: ba6f3000 ba70a800 SCSIPORT.SYS
ModLoad: ba908000 ba917100 SI3114.sys
ModLoad: ba918000 ba922100 AmdEide.sys
Force unload of AmdEide.sys
ModLoad: ba918000 ba922100 AmdEide.sys
Force unload of AmdEide.sys
ModLoad: ba918000 ba922100 AmdEide.sys
ModLoad: ba928000 ba930e00 disk.sys
Force unload of disk.sys
ModLoad: ba928000 ba930e00 disk.sys
Force unload of disk.sys
ModLoad: ba928000 ba930e00 disk.sys
ModLoad: ba938000 ba944200 CLASSPNP.SYS
ModLoad: ba6d4000 ba6f2780 fltMgr.sys
Force unload of fltMgr.sys
ModLoad: ba6d4000 ba6f2780 fltMgr.sys
Force unload of fltMgr.sys
ModLoad: ba6d4000 ba6f2780 fltMgr.sys
Force unload of fltMgr.sys
ModLoad: ba6d4000 ba6f2780 fltMgr.sys
ModLoad: ba6c2000 ba6d3f00 sr.sys
ModLoad: bab40000 bab44080 PxHelp20.sys
ModLoad: bacbc000 bacbe880 SiWinAcc.sys
ModLoad: ba6ab000 ba6c1780 KSecDD.sys
Force unload of KSecDD.sys
ModLoad: ba6ab000 ba6c1780 KSecDD.sys
Force unload of KSecDD.sys
ModLoad: ba6ab000 ba6c1780 KSecDD.sys
Force unload of KSecDD.sys
ModLoad: ba6ab000 ba6c1780 KSecDD.sys

[David_J_Craig]

What is wrong with 6.6.3.5? Check the cable with HyperTerminal and see if
it is reliable. Also try slowing the baud rate to 56k or slower. Any
chance the serial port is normally used by the UPS or a modem? Did you try
Ctrl+Alt+R? Check the software on that machine to make sure these is no
protected software on it that won’t run with the debug mode active. This is
on the target only as it should be easy to validate the host system. Serial
ports are becoming as the $0.19 hamburger of my youth. Try a USB to Serial
adapter on the host. Only Vista can use one of those on a target system.

“Loren Wilton” wrote in message news:xxxxx@ntdev…
> My partner has a machine that seemingly just doesn’t like to be debugged.
>
> The machine is a dual x64 machine, but it is running XP Pro 32 bit.
>
> When I connect windbg from my machine to this thing using a standard
> serial debugging cable and then reboot the dual processor machine
> (specifying /debugport=com1 /baudrate=115200) it comes up and s.l.o.w.l.y
> gets around to showing a connect message in the debugger. Then nothing.
>
> If I turn on verbose debugging I can see it s.l.o.w.l.y loading – and
> unloading – multiple times – assorted modules. After about 20 minutes
> it will finally load KSecDD. Then nothing. Ever.
>
> If my partner tries debugging this from another machine she sais it
> doesn’t even get that far before it stops. However, if run without the
> debugger, the machine runs fine!
>
> I’ve tried to break into the debug session, and tried setting initial
> breakpoint. Neither result in a breakpoint. I’ve tried different
> baudrates in case the machine is having a serial port problem. Nada.
>
> So. Anyone seen something like this? Even better: have you seen it and
> figured out what is going wrong, or what to do about it?
>
> Thanks,
>
> Loren
>
>
> Microsoft (R) Windows Debugger Version 6.5.0003.7
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Opened \.\com1
> Waiting to reconnect…
> Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
> Kernel Debugger connection established.
> Symbol search path is:
> SRVg:\websymbolshttp://msdl.microsoft.com/download/symbols
> Executable search path is:
> Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
> Built by: 2600.xpsp_sp2_gdr.050301-1519
> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
> System Uptime: not available
> Verbose mode ON.
> ModLoad: bada8000 bada9b80 kdcom.dll
> Force unload of kdcom.dll
> ModLoad: bada8000 bada9b80 kdcom.dll
> ModLoad: bacb8000 bacbb000 BOOTVID.dll
> ModLoad: ba779000 ba7a6d80 ACPI.sys
> ModLoad: badaa000 badab100 WMILIB.SYS
> ModLoad: ba768000 ba778a80 pci.sys
> Force unload of pci.sys
> ModLoad: ba768000 ba778a80 pci.sys
> Force unload of pci.sys
> ModLoad: ba768000 ba778a80 pci.sys
> ModLoad: ba8a8000 ba8b0c00 isapnp.sys
> ModLoad: ba8b8000 ba8c6e80 ohci1394.sys
> ModLoad: ba8c8000 ba8d5000 1394BUS.SYS
> ModLoad: bae70000 bae70d00 pciide.sys
> ModLoad: bab28000 bab2e200 PCIIDEX.SYS
> Force unload of PCIIDEX.SYS
> ModLoad: bab28000 bab2e200 PCIIDEX.SYS
> ModLoad: ba8d8000 ba8e2500 MountMgr.sys
> ModLoad: ba749000 ba767880 ftdisk.sys
> Force unload of ftdisk.sys
> ModLoad: ba749000 ba767880 ftdisk.sys
> Force unload of ftdisk.sys
> ModLoad: ba749000 ba767880 ftdisk.sys
> Force unload of ftdisk.sys
> ModLoad: ba749000 ba767880 ftdisk.sys
> Force unload of ftdisk.sys
> ModLoad: ba749000 ba767880 ftdisk.sys
> ModLoad: badac000 badad700 dmload.sys
> ModLoad: ba723000 ba748700 dmio.sys
> ModLoad: bab30000 bab34900 PartMgr.sys
> ModLoad: ba8e8000 ba8f4000 amdbusdr.sys
> ModLoad: ba8f8000 ba904c80 VolSnap.sys
> Force unload of VolSnap.sys
> ModLoad: ba8f8000 ba904c80 VolSnap.sys
> Force unload of VolSnap.sys
> ModLoad: ba8f8000 ba904c80 VolSnap.sys
> ModLoad: ba70b000 ba722480 atapi.sys
> ModLoad: bab38000 bab3c380 mraid35x.sys
> Force unload of mraid35x.sys
> ModLoad: bab38000 bab3c380 mraid35x.sys
> ModLoad: ba6f3000 ba70a800 SCSIPORT.SYS
> Force unload of SCSIPORT.SYS
> ModLoad: ba6f3000 ba70a800 SCSIPORT.SYS
> Force unload of SCSIPORT.SYS
> ModLoad: ba6f3000 ba70a800 SCSIPORT.SYS
> ModLoad: ba908000 ba917100 SI3114.sys
> ModLoad: ba918000 ba922100 AmdEide.sys
> Force unload of AmdEide.sys
> ModLoad: ba918000 ba922100 AmdEide.sys
> Force unload of AmdEide.sys
> ModLoad: ba918000 ba922100 AmdEide.sys
> ModLoad: ba928000 ba930e00 disk.sys
> Force unload of disk.sys
> ModLoad: ba928000 ba930e00 disk.sys
> Force unload of disk.sys
> ModLoad: ba928000 ba930e00 disk.sys
> ModLoad: ba938000 ba944200 CLASSPNP.SYS
> ModLoad: ba6d4000 ba6f2780 fltMgr.sys
> Force unload of fltMgr.sys
> ModLoad: ba6d4000 ba6f2780 fltMgr.sys
> Force unload of fltMgr.sys
> ModLoad: ba6d4000 ba6f2780 fltMgr.sys
> Force unload of fltMgr.sys
> ModLoad: ba6d4000 ba6f2780 fltMgr.sys
> ModLoad: ba6c2000 ba6d3f00 sr.sys
> ModLoad: bab40000 bab44080 PxHelp20.sys
> ModLoad: bacbc000 bacbe880 SiWinAcc.sys
> ModLoad: ba6ab000 ba6c1780 KSecDD.sys
> Force unload of KSecDD.sys
> ModLoad: ba6ab000 ba6c1780 KSecDD.sys
> Force unload of KSecDD.sys
> ModLoad: ba6ab000 ba6c1780 KSecDD.sys
> Force unload of KSecDD.sys
> ModLoad: ba6ab000 ba6c1780 KSecDD.sys
>
>

[Scott_Noone_OSR]

Hi,

The usual trick to these sorts of problems is disabling legacy USB support
in the target BIOS. If that doesn’t work I suggest investing in a couple of
1394 cards.

-scott

–
Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Loren Wilton” wrote in message news:xxxxx@ntdev…
> My partner has a machine that seemingly just doesn’t like to be debugged.
>
> The machine is a dual x64 machine, but it is running XP Pro 32 bit.
>
> When I connect windbg from my machine to this thing using a standard
> serial debugging cable and then reboot the dual processor machine
> (specifying /debugport=com1 /baudrate=115200) it comes up and s.l.o.w.l.y
> gets around to showing a connect message in the debugger. Then nothing.
>
> If I turn on verbose debugging I can see it s.l.o.w.l.y loading – and
> unloading – multiple times – assorted modules. After about 20 minutes
> it will finally load KSecDD. Then nothing. Ever.
>
> If my partner tries debugging this from another machine she sais it
> doesn’t even get that far before it stops. However, if run without the
> debugger, the machine runs fine!
>
> I’ve tried to break into the debug session, and tried setting initial
> breakpoint. Neither result in a breakpoint. I’ve tried different
> baudrates in case the machine is having a serial port problem. Nada.
>
> So. Anyone seen something like this? Even better: have you seen it and
> figured out what is going wrong, or what to do about it?
>
> Thanks,
>
> Loren
>
>
> Microsoft (R) Windows Debugger Version 6.5.0003.7
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Opened \.\com1
> Waiting to reconnect…
> Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
> Kernel Debugger connection established.
> Symbol search path is:
> SRVg:\websymbolshttp://msdl.microsoft.com/download/symbols
> Executable search path is:
> Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
> Built by: 2600.xpsp_sp2_gdr.050301-1519
> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
> System Uptime: not available
> Verbose mode ON.
> ModLoad: bada8000 bada9b80 kdcom.dll
> Force unload of kdcom.dll
> ModLoad: bada8000 bada9b80 kdcom.dll
> ModLoad: bacb8000 bacbb000 BOOTVID.dll
> ModLoad: ba779000 ba7a6d80 ACPI.sys
> ModLoad: badaa000 badab100 WMILIB.SYS
> ModLoad: ba768000 ba778a80 pci.sys
> Force unload of pci.sys
> ModLoad: ba768000 ba778a80 pci.sys
> Force unload of pci.sys
> ModLoad: ba768000 ba778a80 pci.sys
> ModLoad: ba8a8000 ba8b0c00 isapnp.sys
> ModLoad: ba8b8000 ba8c6e80 ohci1394.sys
> ModLoad: ba8c8000 ba8d5000 1394BUS.SYS
> ModLoad: bae70000 bae70d00 pciide.sys
> ModLoad: bab28000 bab2e200 PCIIDEX.SYS
> Force unload of PCIIDEX.SYS
> ModLoad: bab28000 bab2e200 PCIIDEX.SYS
> ModLoad: ba8d8000 ba8e2500 MountMgr.sys
> ModLoad: ba749000 ba767880 ftdisk.sys
> Force unload of ftdisk.sys
> ModLoad: ba749000 ba767880 ftdisk.sys
> Force unload of ftdisk.sys
> ModLoad: ba749000 ba767880 ftdisk.sys
> Force unload of ftdisk.sys
> ModLoad: ba749000 ba767880 ftdisk.sys
> Force unload of ftdisk.sys
> ModLoad: ba749000 ba767880 ftdisk.sys
> ModLoad: badac000 badad700 dmload.sys
> ModLoad: ba723000 ba748700 dmio.sys
> ModLoad: bab30000 bab34900 PartMgr.sys
> ModLoad: ba8e8000 ba8f4000 amdbusdr.sys
> ModLoad: ba8f8000 ba904c80 VolSnap.sys
> Force unload of VolSnap.sys
> ModLoad: ba8f8000 ba904c80 VolSnap.sys
> Force unload of VolSnap.sys
> ModLoad: ba8f8000 ba904c80 VolSnap.sys
> ModLoad: ba70b000 ba722480 atapi.sys
> ModLoad: bab38000 bab3c380 mraid35x.sys
> Force unload of mraid35x.sys
> ModLoad: bab38000 bab3c380 mraid35x.sys
> ModLoad: ba6f3000 ba70a800 SCSIPORT.SYS
> Force unload of SCSIPORT.SYS
> ModLoad: ba6f3000 ba70a800 SCSIPORT.SYS
> Force unload of SCSIPORT.SYS
> ModLoad: ba6f3000 ba70a800 SCSIPORT.SYS
> ModLoad: ba908000 ba917100 SI3114.sys
> ModLoad: ba918000 ba922100 AmdEide.sys
> Force unload of AmdEide.sys
> ModLoad: ba918000 ba922100 AmdEide.sys
> Force unload of AmdEide.sys
> ModLoad: ba918000 ba922100 AmdEide.sys
> ModLoad: ba928000 ba930e00 disk.sys
> Force unload of disk.sys
> ModLoad: ba928000 ba930e00 disk.sys
> Force unload of disk.sys
> ModLoad: ba928000 ba930e00 disk.sys
> ModLoad: ba938000 ba944200 CLASSPNP.SYS
> ModLoad: ba6d4000 ba6f2780 fltMgr.sys
> Force unload of fltMgr.sys
> ModLoad: ba6d4000 ba6f2780 fltMgr.sys
> Force unload of fltMgr.sys
> ModLoad: ba6d4000 ba6f2780 fltMgr.sys
> Force unload of fltMgr.sys
> ModLoad: ba6d4000 ba6f2780 fltMgr.sys
> ModLoad: ba6c2000 ba6d3f00 sr.sys
> ModLoad: bab40000 bab44080 PxHelp20.sys
> ModLoad: bacbc000 bacbe880 SiWinAcc.sys
> ModLoad: ba6ab000 ba6c1780 KSecDD.sys
> Force unload of KSecDD.sys
> ModLoad: ba6ab000 ba6c1780 KSecDD.sys
> Force unload of KSecDD.sys
> ModLoad: ba6ab000 ba6c1780 KSecDD.sys
> Force unload of KSecDD.sys
> ModLoad: ba6ab000 ba6c1780 KSecDD.sys
>
>

[OSR_Community_User]

LOREN:

I have experienced this a different form of this sort of behavior
several times in the past with some combination of these circumstances:

1. Using WinDbg and Visual SoftICE together.
2. Any Symantec Norton Product that using the common licensing engine
   under WinDbg. This is due to what xxxxx@yoshumini described.
3. WinDbg is not configured to use either symbols or images correctly,
   causing it to reload everything. In the case of images over serial, you
   would be there forever. Usually, this is due to a no local copy of the
   images being available. Make sure you have the correct images available
   locally, point WinDbg to them, and then try deleting your local symbol
   store, tunring !sym noisy, and see what happens. You probably already
   know this, but I thought I’d just mention it.

If any of these might apply to you, I’ll be glad to describe them
further, but I won’t here as, after doing some misguided research that
turned out to be useful, I don’t think this is your situation. It looks
like NT is objecting to your SCSI/RAID/DISK/SATA controiller and then
hanging; my guess would be that KSecDD is the last boot driver to load
on your system. The problem looks to be occurring when the kernel
actually tries to start the drivers. In any case, when I saw
SiWinAcc.SYS in the trace, I mistakenly thought that this was one of the
drivers that Visual SoftICE loads early in the boot process, so I
checked that out, which led me to references to Symantec Norton
products. That I had this problem with both products turned out to be,
I think, a strange coincidence, because I stumbled upon a much more
likely cause that I had not considered. It sounds like this problem
occurs on X64 systems with certain SATA RAID controllers, particuarly on
MSI motherboards, and is caused by confusion/lack of drivers for non
RAID based SATA disks. I have never had this problem, but it really
sounds like what is going on in your case, and, looking at the trace,
you never get an appropriate driver loaded. However, the problem, as
described, only seems to occur during setup, and, of course, you are
only seeing it under WinDbg, so maybe it is not it. In any case, Google
SiWinAcc and look at the first few hits.

MM

>> xxxxx@earthlink.net 2006-07-11 04:07 >>>
My partner has a machine that seemingly just doesn’t like to be
debugged.

The machine is a dual x64 machine, but it is running XP Pro 32 bit.

When I connect windbg from my machine to this thing using a standard
serial
debugging cable and then reboot the dual processor machine (specifying

/debugport=com1 /baudrate=115200) it comes up and s.l.o.w.l.y gets
around to
showing a connect message in the debugger. Then nothing.

If I turn on verbose debugging I can see it s.l.o.w.l.y loading – and

unloading – multiple times – assorted modules. After about 20
minutes it
will finally load KSecDD. Then nothing. Ever.

If my partner tries debugging this from another machine she sais it
doesn’t
even get that far before it stops. However, if run without the
debugger,
the machine runs fine!

I’ve tried to break into the debug session, and tried setting initial
breakpoint. Neither result in a breakpoint. I’ve tried different
baudrates
in case the machine is having a serial port problem. Nada.

So. Anyone seen something like this? Even better: have you seen it
and
figured out what is going wrong, or what to do about it?

Thanks,

Loren

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

Opened \.\com1
Waiting to reconnect…
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is:
SRV*g:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
System Uptime: not available
Verbose mode ON.
ModLoad: bada8000 bada9b80 kdcom.dll
Force unload of kdcom.dll
ModLoad: bada8000 bada9b80 kdcom.dll
ModLoad: bacb8000 bacbb000 BOOTVID.dll
ModLoad: ba779000 ba7a6d80 ACPI.sys
ModLoad: badaa000 badab100 WMILIB.SYS
ModLoad: ba768000 ba778a80 pci.sys
Force unload of pci.sys
ModLoad: ba768000 ba778a80 pci.sys
Force unload of pci.sys
ModLoad: ba768000 ba778a80 pci.sys
ModLoad: ba8a8000 ba8b0c00 isapnp.sys
ModLoad: ba8b8000 ba8c6e80 ohci1394.sys
ModLoad: ba8c8000 ba8d5000 1394BUS.SYS
ModLoad: bae70000 bae70d00 pciide.sys
ModLoad: bab28000 bab2e200 PCIIDEX.SYS
Force unload of PCIIDEX.SYS
ModLoad: bab28000 bab2e200 PCIIDEX.SYS
ModLoad: ba8d8000 ba8e2500 MountMgr.sys
ModLoad: ba749000 ba767880 ftdisk.sys
Force unload of ftdisk.sys
ModLoad: ba749000 ba767880 ftdisk.sys
Force unload of ftdisk.sys
ModLoad: ba749000 ba767880 ftdisk.sys
Force unload of ftdisk.sys
ModLoad: ba749000 ba767880 ftdisk.sys
Force unload of ftdisk.sys
ModLoad: ba749000 ba767880 ftdisk.sys
ModLoad: badac000 badad700 dmload.sys
ModLoad: ba723000 ba748700 dmio.sys
ModLoad: bab30000 bab34900 PartMgr.sys
ModLoad: ba8e8000 ba8f4000 amdbusdr.sys
ModLoad: ba8f8000 ba904c80 VolSnap.sys
Force unload of VolSnap.sys
ModLoad: ba8f8000 ba904c80 VolSnap.sys
Force unload of VolSnap.sys
ModLoad: ba8f8000 ba904c80 VolSnap.sys
ModLoad: ba70b000 ba722480 atapi.sys
ModLoad: bab38000 bab3c380 mraid35x.sys
Force unload of mraid35x.sys
ModLoad: bab38000 bab3c380 mraid35x.sys
ModLoad: ba6f3000 ba70a800 SCSIPORT.SYS
Force unload of SCSIPORT.SYS
ModLoad: ba6f3000 ba70a800 SCSIPORT.SYS
Force unload of SCSIPORT.SYS
ModLoad: ba6f3000 ba70a800 SCSIPORT.SYS
ModLoad: ba908000 ba917100 SI3114.sys
ModLoad: ba918000 ba922100 AmdEide.sys
Force unload of AmdEide.sys
ModLoad: ba918000 ba922100 AmdEide.sys
Force unload of AmdEide.sys
ModLoad: ba918000 ba922100 AmdEide.sys
ModLoad: ba928000 ba930e00 disk.sys
Force unload of disk.sys
ModLoad: ba928000 ba930e00 disk.sys
Force unload of disk.sys
ModLoad: ba928000 ba930e00 disk.sys
ModLoad: ba938000 ba944200 CLASSPNP.SYS
ModLoad: ba6d4000 ba6f2780 fltMgr.sys
Force unload of fltMgr.sys
ModLoad: ba6d4000 ba6f2780 fltMgr.sys
Force unload of fltMgr.sys
ModLoad: ba6d4000 ba6f2780 fltMgr.sys
Force unload of fltMgr.sys
ModLoad: ba6d4000 ba6f2780 fltMgr.sys
ModLoad: ba6c2000 ba6d3f00 sr.sys
ModLoad: bab40000 bab44080 PxHelp20.sys
ModLoad: bacbc000 bacbe880 SiWinAcc.sys
ModLoad: ba6ab000 ba6c1780 KSecDD.sys
Force unload of KSecDD.sys
ModLoad: ba6ab000 ba6c1780 KSecDD.sys
Force unload of KSecDD.sys
ModLoad: ba6ab000 ba6c1780 KSecDD.sys
Force unload of KSecDD.sys
ModLoad: ba6ab000 ba6c1780 KSecDD.sys

---

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer