Blue screen

Hans Näslund

Recently, I am frequently getting the infamous blue screen for some reason I
cannot figure out, so I hope sombody here might be able to help.

I have created two virtual disks on a USB memory stick with Cryptainer
(. One of them works OK, but the other frequently crashes
the computer with the blue screen if I try to drag and drop a file to or
from the disk, or even if I try to close a program with Explorer.

CHKDSK does not find any errors on the virtual disk or on the USB memory.

Recent error reports to Microsoft generate the following response:
"Unfortunately, the error report you submitted is corrupted and cannot be
analyzed. Corrupted error reports are rare. They can be caused by hardware
or software problems, and they usually indicate a serious problem with your
computer."

The remedies suggested by Microsoft do not help.

Any other suggestions??

Hans Näslund

Is there really nobody out there who has an idea of how to remedy, or
diagnose, this error?

"Hans Näslund" <> skrev i meddelandet
news:T_jui.5795$...
> Recently, I am frequently getting the infamous blue screen for some reason
> I cannot figure out, so I hope sombody here might be able to help.
>
> I have created two virtual disks on a USB memory stick with Cryptainer
> (. One of them works OK, but the other frequently crashes
> the computer with the blue screen if I try to drag and drop a file to or
> from the disk, or even if I try to close a program with Explorer.
>
> CHKDSK does not find any errors on the virtual disk or on the USB memory.
>
> Recent error reports to Microsoft generate the following response:
> "Unfortunately, the error report you submitted is corrupted and cannot be
> analyzed. Corrupted error reports are rare. They can be caused by hardware
> or software problems, and they usually indicate a serious problem with
> your computer."
>
> The remedies suggested by Microsoft do not help.
>
> Any other suggestions??
>

John John

We don't know the contents of the Bugcheck error message (BSOD) so we
can't give you any suggestions.

John

Hans Näslund wrote:

> Is there really nobody out there who has an idea of how to remedy, or
> diagnose, this error?
>
> "Hans Näslund" <> skrev i meddelandet
> news:T_jui.5795$...
>
>>Recently, I am frequently getting the infamous blue screen for some reason
>>I cannot figure out, so I hope sombody here might be able to help.
>>
>>I have created two virtual disks on a USB memory stick with Cryptainer
>>(. One of them works OK, but the other frequently crashes
>>the computer with the blue screen if I try to drag and drop a file to or
>>from the disk, or even if I try to close a program with Explorer.
>>
>>CHKDSK does not find any errors on the virtual disk or on the USB memory.
>>
>>Recent error reports to Microsoft generate the following response:
>>"Unfortunately, the error report you submitted is corrupted and cannot be
>>analyzed. Corrupted error reports are rare. They can be caused by hardware
>>or software problems, and they usually indicate a serious problem with
>>your computer."
>>
>>The remedies suggested by Microsoft do not help.
>>
>>Any other suggestions??
>>
>
>
>

Hans Näslund

Is there really nobody out there who has an idea of how to remedy, or
diagnose, this error?

"Hans Näslund" <> skrev i meddelandet
news:T_jui.5795$...
> Recently, I am frequently getting the infamous blue screen for some reason
> I cannot figure out, so I hope sombody here might be able to help.
>
> I have created two virtual disks on a USB memory stick with Cryptainer
> (. One of them works OK, but the other frequently crashes
> the computer with the blue screen if I try to drag and drop a file to or
> from the disk, or even if I try to close a program with Explorer.
>
> CHKDSK does not find any errors on the virtual disk or on the USB memory.
>
> Recent error reports to Microsoft generate the following response:
> "Unfortunately, the error report you submitted is corrupted and cannot be
> analyzed. Corrupted error reports are rare. They can be caused by hardware
> or software problems, and they usually indicate a serious problem with
> your computer."
>
> The remedies suggested by Microsoft do not help.
>
> Any other suggestions??
>

John John

We don't know the contents of the Bugcheck error message (BSOD) so we
can't give you any suggestions.

John

Hans Näslund wrote:

> Is there really nobody out there who has an idea of how to remedy, or
> diagnose, this error?
>
> "Hans Näslund" <> skrev i meddelandet
> news:T_jui.5795$...
>
>>Recently, I am frequently getting the infamous blue screen for some reason
>>I cannot figure out, so I hope sombody here might be able to help.
>>
>>I have created two virtual disks on a USB memory stick with Cryptainer
>>(. One of them works OK, but the other frequently crashes
>>the computer with the blue screen if I try to drag and drop a file to or
>>from the disk, or even if I try to close a program with Explorer.
>>
>>CHKDSK does not find any errors on the virtual disk or on the USB memory.
>>
>>Recent error reports to Microsoft generate the following response:
>>"Unfortunately, the error report you submitted is corrupted and cannot be
>>analyzed. Corrupted error reports are rare. They can be caused by hardware
>>or software problems, and they usually indicate a serious problem with
>>your computer."
>>
>>The remedies suggested by Microsoft do not help.
>>
>>Any other suggestions??
>>
>
>
>

Uncle Grumpy

"Hans Näslund" <> wrote:

>Is there really nobody out there who has an idea of how to remedy, or
>diagnose, this error?

Apparently not... I guess you're on yer own, bucko.

Uncle Grumpy

"Hans Näslund" <> wrote:

>Is there really nobody out there who has an idea of how to remedy, or
>diagnose, this error?

Apparently not... I guess you're on yer own, bucko.

Hans Näslund

OK - I have now been able to read the dump files with the help of WinDbg,
and it seems that the error was caused by SRTSP.SYS i three cases, and by
Fastfat.SYS i four cases, seemingly random.

I attach the printouts of the dump files in text format - does that help?


"John John" <.ca> skrev i meddelandet
news:%.gbl...
> We don't know the contents of the Bugcheck error message (BSOD) so we
> can't give you any suggestions.
>
> John
>
> Hans Näslund wrote:
>
>> Is there really nobody out there who has an idea of how to remedy, or
>> diagnose, this error?
>>
>> "Hans Näslund" <> skrev i meddelandet
>> news:T_jui.5795$...
>>
>>>Recently, I am frequently getting the infamous blue screen for some
>>>reason
>>>I cannot figure out, so I hope sombody here might be able to help.
>>>
>>>I have created two virtual disks on a USB memory stick with Cryptainer
>>>(. One of them works OK, but the other frequently
>>>crashes
>>>the computer with the blue screen if I try to drag and drop a file to or
>>>from the disk, or even if I try to close a program with Explorer.
>>>
>>>CHKDSK does not find any errors on the virtual disk or on the USB memory.
>>>
>>>Recent error reports to Microsoft generate the following response:
>>>"Unfortunately, the error report you submitted is corrupted and cannot be
>>>analyzed. Corrupted error reports are rare. They can be caused by
>>>hardware
>>>or software problems, and they usually indicate a serious problem with
>>>your computer."
>>>
>>>The remedies suggested by Microsoft do not help.
>>>
>>>Any other suggestions??
>>>
>>
>>
>>
>

Hans Näslund

OK - I have now been able to read the dump files with the help of WinDbg,
and it seems that the error was caused by SRTSP.SYS i three cases, and by
Fastfat.SYS i four cases, seemingly random.

I attach the printouts of the dump files in text format - does that help?


"John John" <.ca> skrev i meddelandet
news:%.gbl...
> We don't know the contents of the Bugcheck error message (BSOD) so we
> can't give you any suggestions.
>
> John
>
> Hans Näslund wrote:
>
>> Is there really nobody out there who has an idea of how to remedy, or
>> diagnose, this error?
>>
>> "Hans Näslund" <> skrev i meddelandet
>> news:T_jui.5795$...
>>
>>>Recently, I am frequently getting the infamous blue screen for some
>>>reason
>>>I cannot figure out, so I hope sombody here might be able to help.
>>>
>>>I have created two virtual disks on a USB memory stick with Cryptainer
>>>(. One of them works OK, but the other frequently
>>>crashes
>>>the computer with the blue screen if I try to drag and drop a file to or
>>>from the disk, or even if I try to close a program with Explorer.
>>>
>>>CHKDSK does not find any errors on the virtual disk or on the USB memory.
>>>
>>>Recent error reports to Microsoft generate the following response:
>>>"Unfortunately, the error report you submitted is corrupted and cannot be
>>>analyzed. Corrupted error reports are rare. They can be caused by
>>>hardware
>>>or software problems, and they usually indicate a serious problem with
>>>your computer."
>>>
>>>The remedies suggested by Microsoft do not help.
>>>
>>>Any other suggestions??
>>>
>>
>>
>>
>

John John

Well, all I can do is provided general information and point you to
further reading material:




SRTSP.SYS: Owned by Symantec/Norton applications, applications that are
known to be problematic on some computers. You may want to disable
those applications and see if the errors cease. Those applications are
probably security/AV applications so take proper precautions if you
disable them.

vsdatant.sys: Owned by Zone Alarm, another application known to be
problematic on some computers. Disable ZA and see if the errors go
away. *WARNING!* If you are using the Zone Alarm firewall and disable
it for troubleshooting purposes *make absolutely sure* that you enable
the Windows firewall or another firewall solution! Unless you
disconnect the computer from outside network (internet) you will be
guaranteed to be infected with a pest of one sort or another within 5
minutes if you run an exposed NT type operating system without a firewall!

John

Hans Näslund wrote:

> OK - I have now been able to read the dump files with the help of WinDbg,
> and it seems that the error was caused by SRTSP.SYS i three cases, and by
> Fastfat.SYS i four cases, seemingly random.
>
> I attach the printouts of the dump files in text format - does that help?
>
>
> "John John" <.ca> skrev i meddelandet
> news:%.gbl...
>
>>We don't know the contents of the Bugcheck error message (BSOD) so we
>>can't give you any suggestions.
>>
>>John
>>
>>Hans Näslund wrote:
>>
>>
>>>Is there really nobody out there who has an idea of how to remedy, or
>>>diagnose, this error?
>>>
>>>"Hans Näslund" <> skrev i meddelandet
>>>news:T_jui.5795$...
>>>
>>>
>>>>Recently, I am frequently getting the infamous blue screen for some
>>>>reason
>>>>I cannot figure out, so I hope sombody here might be able to help.
>>>>
>>>>I have created two virtual disks on a USB memory stick with Cryptainer
>>>>(. One of them works OK, but the other frequently
>>>>crashes
>>>>the computer with the blue screen if I try to drag and drop a file to or
>>>
>>>>from the disk, or even if I try to close a program with Explorer.
>>>
>>>>CHKDSK does not find any errors on the virtual disk or on the USB memory.
>>>>
>>>>Recent error reports to Microsoft generate the following response:
>>>>"Unfortunately, the error report you submitted is corrupted and cannot be
>>>>analyzed. Corrupted error reports are rare. They can be caused by
>>>>hardware
>>>>or software problems, and they usually indicate a serious problem with
>>>>your computer."
>>>>
>>>>The remedies suggested by Microsoft do not help.
>>>>
>>>>Any other suggestions??
>>>>
>>>
>>>
>>>
>
>
> Microsoft (R) Windows Debugger Version 6.7.0005.1
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [C:\WINDOWS\Minidump\Mini080507-01.dmp]
> Mini Kernel Dump File: Only registers and stack trace are available
>
> Symbol search path is: SRV*c:\websymbols*
> 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_qfe.070227-2300
> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
> Debug session time: Sun Aug 5 12:27:14.121 2007 (GMT+2)
> System Uptime: 0 days 4:12:36.974
> Loading Kernel Symbols
> .................................................. .................................................. .................................................. ....................................
> Loading User Symbols
> Loading unloaded module list
> ..............................
> ERROR: FindPlugIns 8007007b
> ************************************************** *****************************
> * *
> * Bugcheck Analysis *
> * *
> ************************************************** *****************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 23, {e0100, b07f54a8, b07f51a4, 8050ef0d}
>
> Probably caused by : Fastfat.SYS ( Fastfat!FatUnpinRepinnedBcbs+94 )
>
> Followup: MachineOwner
> ---------
>
> Microsoft (R) Windows Debugger Version 6.7.0005.1
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [C:\WINDOWS\Minidump\Mini080607-01.dmp]
> Mini Kernel Dump File: Only registers and stack trace are available
>
> Symbol search path is: SRV*c:\websymbols*
> 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_qfe.070227-2300
> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
> Debug session time: Mon Aug 6 10:49:18.656 2007 (GMT+2)
> System Uptime: 0 days 2:27:00.355
> Loading Kernel Symbols
> .................................................. .................................................. .................................................. ...................................
> Loading User Symbols
> Loading unloaded module list
> ................................
> ERROR: FindPlugIns 8007007b
> ************************************************** *****************************
> * *
> * Bugcheck Analysis *
> * *
> ************************************************** *****************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 1000008E, {c0000005, b9dee44b, b2287424, 0}
>
> Unable to load image SRTSP.SYS, Win32 error 0n2
> *** WARNING: Unable to verify timestamp for SRTSP.SYS
> *** ERROR: Module load completed but symbols could not be loaded for SRTSP.SYS
> Unable to load image vsdatant.sys, Win32 error 0n2
> *** WARNING: Unable to verify timestamp for vsdatant.sys
> *** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
> Probably caused by : SRTSP.SYS ( SRTSP+1f56e )
>
> Followup: MachineOwner
> ---------
>
> Microsoft (R) Windows Debugger Version 6.7.0005.1
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [C:\WINDOWS\Minidump\Mini080607-01.dmp]
> Mini Kernel Dump File: Only registers and stack trace are available
>
> Symbol search path is: SRV*c:\websymbols*
> 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_qfe.070227-2300
> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
> Debug session time: Mon Aug 6 10:49:18.656 2007 (GMT+2)
> System Uptime: 0 days 2:27:00.355
> Loading Kernel Symbols
> .................................................. .................................................. .................................................. ...................................
> Loading User Symbols
> Loading unloaded module list
> ................................
> ERROR: FindPlugIns 8007007b
> ************************************************** *****************************
> * *
> * Bugcheck Analysis *
> * *
> ************************************************** *****************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 1000008E, {c0000005, b9dee44b, b2287424, 0}
>
> Unable to load image SRTSP.SYS, Win32 error 0n2
> *** WARNING: Unable to verify timestamp for SRTSP.SYS
> *** ERROR: Module load completed but symbols could not be loaded for SRTSP.SYS
> Unable to load image vsdatant.sys, Win32 error 0n2
> *** WARNING: Unable to verify timestamp for vsdatant.sys
> *** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
> Probably caused by : SRTSP.SYS ( SRTSP+1f56e )
>
> Followup: MachineOwner
> ---------
>
> Microsoft (R) Windows Debugger Version 6.7.0005.1
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [C:\WINDOWS\Minidump\Mini080707-01.dmp]
> Mini Kernel Dump File: Only registers and stack trace are available
>
> Symbol search path is: SRV*c:\websymbols*
> 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_qfe.070227-2300
> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
> Debug session time: Tue Aug 7 18:46:24.255 2007 (GMT+2)
> System Uptime: 0 days 10:19:22.940
> Loading Kernel Symbols
> .................................................. .................................................. .................................................. ....................................
> Loading User Symbols
> Loading unloaded module list
> ......................................
> ERROR: FindPlugIns 8007007b
> ************************************************** *****************************
> * *
> * Bugcheck Analysis *
> * *
> ************************************************** *****************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 23, {e0100, b3709f48, b3709c44, 0}
>
> Probably caused by : Fastfat.SYS ( Fastfat!ExFreeToNPagedLookasideList+15 )
>
> Followup: MachineOwner
> ---------
>
> Microsoft (R) Windows Debugger Version 6.7.0005.1
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [C:\WINDOWS\Minidump\Mini080807-01.dmp]
> Mini Kernel Dump File: Only registers and stack trace are available
>
> Symbol search path is: SRV*c:\websymbols*
> 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_qfe.070227-2300
> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
> Debug session time: Wed Aug 8 11:09:47.219 2007 (GMT+2)
> System Uptime: 0 days 2:47:22.624
> Loading Kernel Symbols
> .................................................. .................................................. .................................................. ...................................
> Loading User Symbols
> Loading unloaded module list
> ....................................
> ERROR: FindPlugIns 8007007b
> ************************************************** *****************************
> * *
> * Bugcheck Analysis *
> * *
> ************************************************** *****************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 23, {e0100, b43ba4a8, b43ba1a4, 8050ef0d}
>
> Probably caused by : Fastfat.SYS ( Fastfat!FatUnpinRepinnedBcbs+94 )
>
> Followup: MachineOwner
> ---------
>
> Microsoft (R) Windows Debugger Version 6.7.0005.1
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [C:\WINDOWS\Minidump\Mini080807-02.dmp]
> Mini Kernel Dump File: Only registers and stack trace are available
>
> Symbol search path is: SRV*c:\websymbols*
> 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_qfe.070227-2300
> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
> Debug session time: Wed Aug 8 15:27:52.306 2007 (GMT+2)
> System Uptime: 0 days 4:17:36.302
> Loading Kernel Symbols
> .................................................. .................................................. .................................................. ....................................
> Loading User Symbols
> Loading unloaded module list
> ................................
> ERROR: FindPlugIns 8007007b
> ************************************************** *****************************
> * *
> * Bugcheck Analysis *
> * *
> ************************************************** *****************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 23, {e0100, b3103a58, b3103754, 8050ef0d}
>
> Probably caused by : Fastfat.SYS ( Fastfat!FatUnpinRepinnedBcbs+94 )
>
> Followup: MachineOwner
> ---------
>
> Microsoft (R) Windows Debugger Version 6.7.0005.1
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [C:\WINDOWS\Minidump\Mini080907-01.dmp]
> Mini Kernel Dump File: Only registers and stack trace are available
>
> Symbol search path is: SRV*c:\websymbols*
> 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_qfe.070227-2300
> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
> Debug session time: Thu Aug 9 15:02:54.976 2007 (GMT+2)
> System Uptime: 0 days 5:20:20.963
> Loading Kernel Symbols
> .................................................. .................................................. .................................................. .....................................
> Loading User Symbols
> Loading unloaded module list
> ................................................
> ERROR: FindPlugIns 8007007b
> ************************************************** *****************************
> * *
> * Bugcheck Analysis *
> * *
> ************************************************** *****************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 1000008E, {c0000005, b9dee44b, b2bf9a24, 0}
>
> Unable to load image SRTSP.SYS, Win32 error 0n2
> *** WARNING: Unable to verify timestamp for SRTSP.SYS
> *** ERROR: Module load completed but symbols could not be loaded for SRTSP.SYS
> Unable to load image vsdatant.sys, Win32 error 0n2
> *** WARNING: Unable to verify timestamp for vsdatant.sys
> *** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
> Probably caused by : SRTSP.SYS ( SRTSP+1f56e )
>
> Followup: MachineOwner
> ---------