Guest Hans Näslund Posted August 8, 2007 Posted August 8, 2007 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 (http://www.cypherix.com). 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??
Guest Hans Näslund Posted August 9, 2007 Posted August 9, 2007 Re: Blue screen Is there really nobody out there who has an idea of how to remedy, or diagnose, this error? "Hans Näslund" <hans.naslund@spray.se> skrev i meddelandet news:T_jui.5795$ZA.2673@newsb.telia.net... > 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 > (http://www.cypherix.com). 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?? >
Guest John John Posted August 9, 2007 Posted August 9, 2007 Re: Blue screen 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" <hans.naslund@spray.se> skrev i meddelandet > news:T_jui.5795$ZA.2673@newsb.telia.net... > >>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 >>(http://www.cypherix.com). 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?? >> > > >
Guest Uncle Grumpy Posted August 10, 2007 Posted August 10, 2007 Re: Blue screen "Hans Näslund" <hans.naslund@spray.se> 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.
Guest Hans Näslund Posted August 10, 2007 Posted August 10, 2007 Re: Blue screen 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" <audetweld@nbnot.nb.ca> skrev i meddelandet news:%232tYiVp2HHA.5424@TK2MSFTNGP02.phx.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" <hans.naslund@spray.se> skrev i meddelandet >> news:T_jui.5795$ZA.2673@newsb.telia.net... >> >>>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 >>>(http://www.cypherix.com). 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?? >>> >> >> >> >
Guest John John Posted August 10, 2007 Posted August 10, 2007 Re: Blue screen Well, all I can do is provided general information and point you to further reading material: http://search.yahoo.com/search?ei=UTF-8&fr=yfp-t-501&cop=mss&p=0x8E+c0000005&x=0&y=0 http://search.yahoo.com/search?ei=UTF-8&fr=yfp-t-501&cop=mss&p=0x23+Fastfat.SYS&x=41&y=8 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" <audetweld@nbnot.nb.ca> skrev i meddelandet > news:%232tYiVp2HHA.5424@TK2MSFTNGP02.phx.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" <hans.naslund@spray.se> skrev i meddelandet >>>news:T_jui.5795$ZA.2673@newsb.telia.net... >>> >>> >>>>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 >>>>(http://www.cypherix.com). 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 ® Windows Debugger Version 6.7.0005.1 > Copyright © 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*http://msdl.microsoft.com/download/symbols > 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 ® Windows Debugger Version 6.7.0005.1 > Copyright © 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*http://msdl.microsoft.com/download/symbols > 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 ® Windows Debugger Version 6.7.0005.1 > Copyright © 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*http://msdl.microsoft.com/download/symbols > 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 ® Windows Debugger Version 6.7.0005.1 > Copyright © 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*http://msdl.microsoft.com/download/symbols > 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 ® Windows Debugger Version 6.7.0005.1 > Copyright © 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*http://msdl.microsoft.com/download/symbols > 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 ® Windows Debugger Version 6.7.0005.1 > Copyright © 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*http://msdl.microsoft.com/download/symbols > 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 ® Windows Debugger Version 6.7.0005.1 > Copyright © 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*http://msdl.microsoft.com/download/symbols > 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 > ---------
Guest Hans Näslund Posted August 11, 2007 Posted August 11, 2007 Re: Blue screen Well - today it happened again. And here are the details: Blue screen message: STOP: 0x0000008E (0x0000005, 0xB9DEE44B, 0xB17B4424, 0x00000000) fltmgr.sys - Address B9DE44B base at B9DDE000, DateStyamp 44e97991 Error signature: BCCode: 1000008e BCP1: C0000005 BCP2: B9DEE44B BCP3: B17B4424 BCP 4: 0000000 OSVer: 5_1_2600 SP: 2_0 Product: 256_1 The report from Microsoft says: 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. I attach a text version of the crash dump file. Any suggestions? "Hans Näslund" <hans.naslund@spray.se> skrev i meddelandet news:T_jui.5795$ZA.2673@newsb.telia.net... > 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 > (http://www.cypherix.com). 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?? > >
Guest Alias Posted August 11, 2007 Posted August 11, 2007 Re: Blue screen Hans Näslund wrote: > Well - today it happened again. And here are the details: > > Blue screen message: > STOP: 0x0000008E (0x0000005, 0xB9DEE44B, 0xB17B4424, 0x00000000) > fltmgr.sys - Address B9DE44B base at B9DDE000, DateStyamp 44e97991 > > Error signature: > BCCode: 1000008e BCP1: C0000005 BCP2: B9DEE44B BCP3: B17B4424 BCP > 4: 0000000 > OSVer: 5_1_2600 SP: 2_0 Product: 256_1 > > The report from Microsoft says: > 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. > > I attach a text version of the crash dump file. > > Any suggestions? > > > "Hans Näslund" <hans.naslund@spray.se> skrev i meddelandet > news:T_jui.5795$ZA.2673@newsb.telia.net... >> 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 >> (http://www.cypherix.com). 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 ® Windows Debugger Version 6.7.0005.1 > Copyright © Microsoft Corporation. All rights reserved. > > > Loading Dump File [C:\Documents and Settings\Hans Näslund\Skrivbord\WERdf02.dir00\Mini081107-01.dmp] > Mini Kernel Dump File: Only registers and stack trace are available > > Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols > 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: Sat Aug 11 12:05:17.988 2007 (GMT+2) > System Uptime: 0 days 3:04:56.544 > 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, b17b4424, 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 > --------- > > 1: kd> !analyze -v > ERROR: FindPlugIns 8007007b > ******************************************************************************* > * * > * Bugcheck Analysis * > * * > ******************************************************************************* > > KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) > This is a very common bugcheck. Usually the exception address pinpoints > the driver/function that caused the problem. Always note this address > as well as the link date of the driver/image that contains this address. > Some common problems are exception code 0x80000003. This means a hard > coded breakpoint or assertion was hit, but this system was booted > /NODEBUG. This is not supposed to happen as developers should never have > hardcoded breakpoints in retail code, but ... > If this happens, make sure a debugger gets connected, and the > system is booted /DEBUG. This will let us see why this breakpoint is > happening. > Arguments: > Arg1: c0000005, The exception code that was not handled > Arg2: b9dee44b, The address that the exception occurred at > Arg3: b17b4424, Trap Frame > Arg4: 00000000 > > Debugging Details: > ------------------ > > > EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruktionen p "0x%08lx" refererade till minnet p "0x%08lx". Det gick inte att utf ra en minnes tg rd. F ljande fel returnerades: The memory could not be "%s". > > FAULTING_IP: > fltMgr!FltpCreate+26d > b9dee44b c9 leave > > TRAP_FRAME: b17b4424 -- (.trap 0xffffffffb17b4424) > ErrCode = 00000000 > eax=00000000 ebx=88fc4d40 ecx=b6c03d51 edx=0000000f esi=8b0cb270 edi=8990e330 > eip=b9dee44b esp=b17b4498 ebp=00000000 iopl=0 nv up ei pl zr na pe nc > cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 > fltMgr!FltpCreate+0x26d: > b9dee44b c9 leave > Resetting default scope > > CUSTOMER_CRASH_COUNT: 1 > > DEFAULT_BUCKET_ID: DRIVER_FAULT > > BUGCHECK_STR: 0x8E > > PROCESS_NAME: explorer.exe > > LAST_CONTROL_TRANSFER: from 804ef163 to b9dee44b > > STACK_TEXT: > b17b44b4 804ef163 889c2610 8990e320 8990e320 fltMgr!FltpCreate+0x26d > b17b44c4 80581fe2 87f979e8 8902b0ac b17b465c nt!IopfCallDriver+0x31 > b17b45a4 805bdf06 87f97a00 00000000 8902b008 nt!IopParseDevice+0xa12 > b17b461c 805ba58e 00000000 b17b465c 00000240 nt!ObpLookupObjectName+0x53c > b17b4670 80574f33 00000000 00000000 c079dc00 nt!ObOpenObjectByName+0xea > b17b46ec 80575920 b17b47a4 00100001 b17b4784 nt!IopCreateFile+0x407 > b17b4734 b9df3915 b17b47a4 00100001 b17b4784 nt!IoCreateFileSpecifyDeviceObjectHint+0x52 > b17b47a8 b9df3bff 87f30c28 b17b47e0 b9df411c fltMgr!FltpNormalizeNameComponent+0x75 > b17b47b4 b9df411c 87f30c28 00000000 87f30c28 fltMgr!FltpCallNormalizeNameComponentHandler+0x41 > b17b47e0 b9df4df6 00000014 00000000 87f30c28 fltMgr!FltpExpandShortNames+0x110 > b17b47fc b9df5407 00000c28 00000000 000000fe fltMgr!FltpGetNormalizedFileNameWorker+0x90 > b17b4814 b9df2f3e 87f30c28 00000000 87f30c28 fltMgr!FltpGetNormalizedFileName+0x19 > b17b482c b9de3cd3 80553000 881338fc 00000000 fltMgr!FltpCreateFileNameInformation+0x84 > b17b4858 b9de4008 00000000 881338fc e531ba58 fltMgr!FltpGetFileNameInformation+0x2d1 > b17b4880 b716356e 001338fc 00000401 8805f198 fltMgr!FltGetFileNameInformation+0x114 > WARNING: Stack unwind information not available. Following frames may be wrong. > b17b48d8 b9ddeef3 881338fc b17b48fc 00000000 SRTSP+0x1f56e > b17b4940 b9de1338 001338a0 00000000 881338a0 fltMgr!FltpPerformPostCallbacks+0x1c5 > b17b4954 b9de1867 881338a0 88c68840 b17b4994 fltMgr!FltpProcessIoCompletion+0x10 > b17b4964 b9de1ef9 88a5e848 88c68840 881338a0 fltMgr!FltpPassThroughCompletion+0x89 > b17b4994 b9dee448 b17b49b4 00000000 00000000 fltMgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x269 > b17b49d0 804ef163 88a5e848 88c68840 88c68840 fltMgr!FltpCreate+0x26a > b17b49e0 80581fe2 87f979e8 88e949cc b17b4b78 nt!IopfCallDriver+0x31 > b17b4ac0 805bdf06 87f97a00 00000000 88e94928 nt!IopParseDevice+0xa12 > b17b4b38 805ba58e 00000000 b17b4b78 00000040 nt!ObpLookupObjectName+0x53c > b17b4b8c 80574f33 00000000 00000000 00000001 nt!ObOpenObjectByName+0xea > b17b4c08 805758aa 057cdf1c 40110080 057cde3c nt!IopCreateFile+0x407 > b17b4c64 80577f76 057cdf1c 40110080 057cde3c nt!IoCreateFile+0x8e > b17b4ca4 b6e1a946 057cdf1c 40110080 057cde3c nt!NtCreateFile+0x30 > b17b4d30 805409ac 057cdf1c 40110080 057cde3c vsdatant+0x2f946 > b17b4d30 7c90eb94 057cdf1c 40110080 057cde3c nt!KiFastCallEntry+0xfc > 057cdf1c 00000000 00000000 00000000 00000000 0x7c90eb94 > > > STACK_COMMAND: kb > > FOLLOWUP_IP: > SRTSP+1f56e > b716356e ?? ??? > > SYMBOL_STACK_INDEX: f > > FOLLOWUP_NAME: MachineOwner > > MODULE_NAME: SRTSP > > IMAGE_NAME: SRTSP.SYS > > DEBUG_FLR_IMAGE_TIMESTAMP: 45a6ee39 > > SYMBOL_NAME: SRTSP+1f56e > > FAILURE_BUCKET_ID: 0x8E_SRTSP+1f56e > > BUCKET_ID: 0x8E_SRTSP+1f56e > > Followup: MachineOwner > --------- It's probably your RAM. See: http://www.google.com/search?hl=en&q=STOP%3A+0x0000008E+&btnG=Search -- Alias To email me, remove shoes
Guest Hans Näslund Posted August 11, 2007 Posted August 11, 2007 Re: Blue screen The attached dump file didn't make it to the group - but it is available here: http://web.telia.com/~u46123001/Examples/Mini081107-01.txt "Alias" <iamalias@shoesgmail.com.> skrev i meddelandet news:OpPANWA3HHA.5316@TK2MSFTNGP04.phx.gbl... > Hans Näslund wrote: >> Well - today it happened again. And here are the details: >> >> Blue screen message: >> STOP: 0x0000008E (0x0000005, 0xB9DEE44B, 0xB17B4424, 0x00000000) >> fltmgr.sys - Address B9DE44B base at B9DDE000, DateStyamp 44e97991 >> >> Error signature: >> BCCode: 1000008e BCP1: C0000005 BCP2: B9DEE44B BCP3: B17B4424 >> BCP 4: 0000000 >> OSVer: 5_1_2600 SP: 2_0 Product: 256_1 >> >> The report from Microsoft says: >> 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. >> >> I attach a text version of the crash dump file. >> >> Any suggestions? >> >> >> "Hans Näslund" <hans.naslund@spray.se> skrev i meddelandet >> news:T_jui.5795$ZA.2673@newsb.telia.net... >>> 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 >>> (http://www.cypherix.com). 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 ® Windows Debugger Version 6.7.0005.1 >> Copyright © Microsoft Corporation. All rights reserved. >> >> >> Loading Dump File [C:\Documents and Settings\Hans >> Näslund\Skrivbord\WERdf02.dir00\Mini081107-01.dmp] >> Mini Kernel Dump File: Only registers and stack trace are available >> >> Symbol search path is: >> SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols >> 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: Sat Aug 11 12:05:17.988 2007 (GMT+2) >> System Uptime: 0 days 3:04:56.544 >> 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, b17b4424, 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 >> --------- >> >> 1: kd> !analyze -v >> ERROR: FindPlugIns 8007007b >> ******************************************************************************* >> * >> * >> * Bugcheck Analysis >> * >> * >> * >> ******************************************************************************* >> >> KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) >> This is a very common bugcheck. Usually the exception address pinpoints >> the driver/function that caused the problem. Always note this address >> as well as the link date of the driver/image that contains this address. >> Some common problems are exception code 0x80000003. This means a hard >> coded breakpoint or assertion was hit, but this system was booted >> /NODEBUG. This is not supposed to happen as developers should never have >> hardcoded breakpoints in retail code, but ... >> If this happens, make sure a debugger gets connected, and the >> system is booted /DEBUG. This will let us see why this breakpoint is >> happening. >> Arguments: >> Arg1: c0000005, The exception code that was not handled >> Arg2: b9dee44b, The address that the exception occurred at >> Arg3: b17b4424, Trap Frame >> Arg4: 00000000 >> >> Debugging Details: >> ------------------ >> >> >> EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruktionen p "0x%08lx" >> refererade till minnet p "0x%08lx". Det gick inte att utf ra en minnes >> tg rd. F ljande fel returnerades: The memory could not be "%s". >> >> FAULTING_IP: fltMgr!FltpCreate+26d >> b9dee44b c9 leave >> >> TRAP_FRAME: b17b4424 -- (.trap 0xffffffffb17b4424) >> ErrCode = 00000000 >> eax=00000000 ebx=88fc4d40 ecx=b6c03d51 edx=0000000f esi=8b0cb270 >> edi=8990e330 >> eip=b9dee44b esp=b17b4498 ebp=00000000 iopl=0 nv up ei pl zr na >> pe nc >> cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 >> efl=00010246 >> fltMgr!FltpCreate+0x26d: >> b9dee44b c9 leave >> Resetting default scope >> >> CUSTOMER_CRASH_COUNT: 1 >> >> DEFAULT_BUCKET_ID: DRIVER_FAULT >> >> BUGCHECK_STR: 0x8E >> >> PROCESS_NAME: explorer.exe >> >> LAST_CONTROL_TRANSFER: from 804ef163 to b9dee44b >> >> STACK_TEXT: b17b44b4 804ef163 889c2610 8990e320 8990e320 >> fltMgr!FltpCreate+0x26d >> b17b44c4 80581fe2 87f979e8 8902b0ac b17b465c nt!IopfCallDriver+0x31 >> b17b45a4 805bdf06 87f97a00 00000000 8902b008 nt!IopParseDevice+0xa12 >> b17b461c 805ba58e 00000000 b17b465c 00000240 nt!ObpLookupObjectName+0x53c >> b17b4670 80574f33 00000000 00000000 c079dc00 nt!ObOpenObjectByName+0xea >> b17b46ec 80575920 b17b47a4 00100001 b17b4784 nt!IopCreateFile+0x407 >> b17b4734 b9df3915 b17b47a4 00100001 b17b4784 >> nt!IoCreateFileSpecifyDeviceObjectHint+0x52 >> b17b47a8 b9df3bff 87f30c28 b17b47e0 b9df411c >> fltMgr!FltpNormalizeNameComponent+0x75 >> b17b47b4 b9df411c 87f30c28 00000000 87f30c28 >> fltMgr!FltpCallNormalizeNameComponentHandler+0x41 >> b17b47e0 b9df4df6 00000014 00000000 87f30c28 >> fltMgr!FltpExpandShortNames+0x110 >> b17b47fc b9df5407 00000c28 00000000 000000fe >> fltMgr!FltpGetNormalizedFileNameWorker+0x90 >> b17b4814 b9df2f3e 87f30c28 00000000 87f30c28 >> fltMgr!FltpGetNormalizedFileName+0x19 >> b17b482c b9de3cd3 80553000 881338fc 00000000 >> fltMgr!FltpCreateFileNameInformation+0x84 >> b17b4858 b9de4008 00000000 881338fc e531ba58 >> fltMgr!FltpGetFileNameInformation+0x2d1 >> b17b4880 b716356e 001338fc 00000401 8805f198 >> fltMgr!FltGetFileNameInformation+0x114 >> WARNING: Stack unwind information not available. Following frames may be >> wrong. >> b17b48d8 b9ddeef3 881338fc b17b48fc 00000000 SRTSP+0x1f56e >> b17b4940 b9de1338 001338a0 00000000 881338a0 >> fltMgr!FltpPerformPostCallbacks+0x1c5 >> b17b4954 b9de1867 881338a0 88c68840 b17b4994 >> fltMgr!FltpProcessIoCompletion+0x10 >> b17b4964 b9de1ef9 88a5e848 88c68840 881338a0 >> fltMgr!FltpPassThroughCompletion+0x89 >> b17b4994 b9dee448 b17b49b4 00000000 00000000 >> fltMgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x269 >> b17b49d0 804ef163 88a5e848 88c68840 88c68840 fltMgr!FltpCreate+0x26a >> b17b49e0 80581fe2 87f979e8 88e949cc b17b4b78 nt!IopfCallDriver+0x31 >> b17b4ac0 805bdf06 87f97a00 00000000 88e94928 nt!IopParseDevice+0xa12 >> b17b4b38 805ba58e 00000000 b17b4b78 00000040 nt!ObpLookupObjectName+0x53c >> b17b4b8c 80574f33 00000000 00000000 00000001 nt!ObOpenObjectByName+0xea >> b17b4c08 805758aa 057cdf1c 40110080 057cde3c nt!IopCreateFile+0x407 >> b17b4c64 80577f76 057cdf1c 40110080 057cde3c nt!IoCreateFile+0x8e >> b17b4ca4 b6e1a946 057cdf1c 40110080 057cde3c nt!NtCreateFile+0x30 >> b17b4d30 805409ac 057cdf1c 40110080 057cde3c vsdatant+0x2f946 >> b17b4d30 7c90eb94 057cdf1c 40110080 057cde3c nt!KiFastCallEntry+0xfc >> 057cdf1c 00000000 00000000 00000000 00000000 0x7c90eb94 >> >> >> STACK_COMMAND: kb >> >> FOLLOWUP_IP: SRTSP+1f56e >> b716356e ?? ??? >> >> SYMBOL_STACK_INDEX: f >> >> FOLLOWUP_NAME: MachineOwner >> >> MODULE_NAME: SRTSP >> >> IMAGE_NAME: SRTSP.SYS >> >> DEBUG_FLR_IMAGE_TIMESTAMP: 45a6ee39 >> >> SYMBOL_NAME: SRTSP+1f56e >> >> FAILURE_BUCKET_ID: 0x8E_SRTSP+1f56e >> >> BUCKET_ID: 0x8E_SRTSP+1f56e >> >> Followup: MachineOwner >> --------- > > It's probably your RAM. > > See: > > http://www.google.com/search?hl=en&q=STOP%3A+0x0000008E+&btnG=Search > -- > Alias > To email me, remove shoes
Recommended Posts