Sudden Shutdown-Black Screen [DUMP DATA]

Hi,
I previously had this problem when running Nortan Antivirus Scan.
Now I have it with Spybot S&D, and Check it Diagnostics from
NSW 2006,and Adobe Reader v7.0 install too.
The computer would just get so far on a full scan and then shutdown
suddenly with no BSOD, just black screen.
The Adobe Reader upgrade/install 7.0 went to blackscreen after nearly
completing the install. I did not uninstall 6.0 first.

Here is what I have done to try to diagnose or fix it.
-
-Delete all Temp files,empty Recycle Bin.
-Ran full scan in Safe Mode including compressed files.
Still got the sudden black screen shutdown.
-Ran full scan in Normal Mode excluding compressed files
the scan completed but only a fraction of the files since
no compressed scanning.
-Ran scan in Safe Mode excluding compressed files and
the computer shutdown with black screen.
-Ran Disk Defrag
-Ran Everest
-Ran Spybot S&D 1.4 after updates and got BSOD with an Error Report
which I sent to Microsoft. The screen said,â€Fixed in Future version
Windows Vista release" (What ??)
-Deleted all Norton Files including hidden files.
-Upgraded and installed NSW 2006(from 2005)
-Autoupdate works but I cannot complete a full scan.
Still get the sudden shutdown with black screen only.
-Ran Check It diagnostics from NSW2006 and got black screen
shutdown on Memory tests.
-Read through XP Shutdown Troubleshooting page but it doesn’t seem to apply.
-Ran SIW.exe but it doesn’t show errors or problems as far as I can tell.

Appreciate any advice.
Gary

 

Hello Gary,

Don't see from your lsit that you ran chkdsk.

From the Start menu > run > type cmd > ok

In the command box at the prompt type chkdisk /r

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/chkdsk.mspx?mfr=true MS doc on chkdsk with the switch settings and what they do.

Regards - Charles

 

Sudden Shutdown-Black Screen

Hi Charles,
Thanks for your suggestion.
I just ran chkdsk /r and it stepped through stages 1-4.
At 97% complete on stage 4(file data) I looked away for
a few minutes and the computer suddenly restarted. After which it
displayed the small blue box and message, "chkdsk is checking
drive C: The volume is clean ". Then on to normal restart.
I read the document you referred me to and this appears to
be normal.

Related-I forgot to mention in my first post that the hard drive
seems to be running almost constantly after the install of NSW 2006.
It is definately running more than it used to.
Processes which seem to keep using system resources are:
cisvc.exe, SYSTEM, and csrss.exe.

Any suggestions ?

Thanks so much,
Gary

 

cisvc.exe is your Indexing Service. This has been known to cause problems on some systems.

Arie's article about Improve Performance By Disabling Indexing Service.

csrss.exe is Client Server Runtime Process. It should be located in the C:\Windows\System32 folder. There is also a Trojan with that name. It would be in a different location.

Check these out and see if it helps.

 

Hi Gary,

Reading thru your 1st post again, I'm struck by the fact that you get this running memory intensive processes. You don't mention what happens when you're running an app or surfing.

MS's memory diagnostic: http://oca.microsoft.com/en/windiag.asp

If you have more than 1 memory slot, or more than one stick, switch them. In any case case, pull the memory out (carefully) to get any accumulated junk off.

Still remains to be seen whether this is a problem with a file, application, or hardware.

Do you remember what the blue screen error was? If not, can you replicate it?

Regards - Charles

 

Sudden Shutdown-Black Screen

Whiskeyman and Charles,
Thanks for your replies.

I will check out the indexing info you sent.

Sorry, forgot to mention also that the computer gives no problem when
surfing or running any app so far. This is Fujitsu NSeries Lifebook 512MB Ram
XP Home SP2

I have the dump file from the Spybot BSOD and will post in next reply as it
is long. I ran it through debugwiz.

Thanks,
Gary

 

Sudden Shutdown-Black Screen Dump Data

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\WINDOWS\Minidump\Mini060606-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Tue Jun 6 08:52:25.478 2006 (GMT-7)
System Uptime: 0 days 0:22:35.048
Loading Kernel Symbols
..................................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image SAVRT.SYS, Win32 error 2
*** WARNING: Unable to verify timestamp for SAVRT.SYS
*** ERROR: Module load completed but symbols could not be loaded for SAVRT.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, ef2e2874, 82ef9c28, 0}

Probably caused by : hardware ( SAVRT+3f874 )

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

kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* 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: ef2e2874, The address that the exception occurred at
Arg3: 82ef9c28, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The memory could not be "%s ".

FAULTING_IP:
SAVRT+3f874
ef2e2874 c00d0010000600 ror byte ptr [06001000],0x0

TRAP_FRAME: 82ef9c28 -- (.trap ffffffff82ef9c28)
.trap ffffffff82ef9c28
ErrCode = 00000002
eax=82ef9cb0 ebx=e2b31008 ecx=00000000 edx=e2b31008 esi=e2b31008 edi=e2b3133a
eip=ef2e2874 esp=82ef9c9c ebp=82ef9eb4 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
SAVRT+0x3f874:
ef2e2874 c00d0010000600 ror byte ptr [06001000],0x0 ds:0023:06001000=??
.trap
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

MISALIGNED_IP:
SAVRT+3f874
ef2e2874 c00d0010000600 ror byte ptr [06001000],0x0

LAST_CONTROL_TRANSFER: from ef2d4daf to ef2e2874

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
82ef9eb4 ef2d4daf 00000000 00000000 82ef9ed8 SAVRT+0x3f874
00000000 00000000 00000000 00000000 00000000 SAVRT+0x31daf


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
SAVRT+3f874
ef2e2874 c00d0010000600 ror byte ptr [06001000],0x0

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: SAVRT+3f874

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED_SAVRT.SYS

BUCKET_ID: IP_MISALIGNED_SAVRT.SYS

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

eax=82ef9cb0 ebx=e2b31008 ecx=00000000 edx=e2b31008 esi=e2b31008 edi=e2b3133a
eip=ef2e2874 esp=82ef9c9c ebp=82ef9eb4 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
SAVRT+0x3f874:
ef2e2874 c00d0010000600 ror byte ptr [06001000],0x0 ds:0023:06001000=??
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
82ef9eb4 ef2d4daf 00000000 00000000 82ef9ed8 SAVRT+0x3f874
00000000 00000000 00000000 00000000 00000000 SAVRT+0x31daf
start end module name
804d7000 806eb100 nt ntoskrnl.exe Tue Mar 01 16:59:37 2005 (42250FF9)
806ec000 806ffd80 hal halacpi.dll Tue Aug 03 22:59:04 2004 (41107B28)
bf800000 bf9c1180 win32k win32k.sys Wed Oct 05 17:05:44 2005 (43446A58)
bf9c2000 bf9d3580 dxg dxg.sys Tue Aug 03 23:00:51 2004 (41107B93)
bf9d4000 bfa15880 ati2dvag ati2dvag.dll Mon Jan 20 19:45:02 2003 (3E2CC23E)
bfa16000 bfb2d440 ati3d2ag ati3d2ag.dll Mon Jan 20 19:18:25 2003 (3E2CBC01)
bffa0000 bffe5c00 ATMFD ATMFD.DLL Wed Aug 04 00:56:56 2004 (411096C8)
eeea4000 eeee4100 HTTP HTTP.sys Fri Oct 08 16:48:20 2004 (41672744)
ef16a000 ef17e400 wdmaud wdmaud.sys Tue Aug 03 23:15:03 2004 (41107EE7)
ef1cf000 ef1e0980 NAVENG NAVENG.Sys Thu Feb 23 15:37:13 2006 (43FE4729)
ef1e1000 ef2a2b40 NavEx15 NavEx15.Sys Thu Feb 23 15:57:28 2006 (43FE4BE8)
ef2a3000 ef2fb000 SAVRT SAVRT.SYS Mon Mar 07 14:49:41 2005 (422CDA85)
ef6db000 ef6e9d80 sysaudio sysaudio.sys Tue Aug 03 23:15:54 2004 (41107F1A)
ef75b000 ef78a700 symidsco symidsco.sys Tue Jan 10 18:55:48 2006 (43C473B4)
ef7b3000 ef7dbdc0 SYMFW SYMFW.SYS Tue Apr 05 11:11:07 2005 (4252D4BB)
ef954000 ef95c8a0 NPDRIVER NPDRIVER.SYS Mon Jan 24 16:38:00 2005 (41F594E8)
ef974000 ef97e180 SYMNDIS SYMNDIS.SYS Tue Apr 05 11:11:01 2005 (4252D4B5)
ef994000 ef9e5300 srv srv.sys Mon May 09 17:17:49 2005 (427FFDAD)
ef9e6000 ef9e8f60 SYMREDRV SYMREDRV.SYS Tue Apr 05 11:11:10 2005 (4252D4BE)
efafe000 efb2a400 mrxdav mrxdav.sys Tue Aug 03 23:00:49 2004 (41107B91)
efc07000 efc0aee0 Aspi32 Aspi32.SYS Mon May 06 09:43:02 2002 (3CD6B296)
efcdb000 efcea900 Cdfs Cdfs.SYS Tue Aug 03 23:14:09 2004 (41107EB1)
efd23000 efd26280 ndisuio ndisuio.sys Tue Aug 03 23:03:10 2004 (41107C1E)
efdab000 efdc2480 dump_atapi dump_atapi.sys Tue Aug 03 22:59:41 2004 (41107B4D)
efdc3000 efde6000 Fastfat Fastfat.SYS Tue Aug 03 23:14:15 2004 (41107EB7)
efeae000 efecef00 ipnat ipnat.sys Wed Sep 29 15:28:36 2004 (415B3714)
efecf000 eff3d400 mrxsmb mrxsmb.sys Tue Jan 18 20:26:50 2005 (41EDE18A)
eff3e000 eff68a00 rdbss rdbss.sys Wed Oct 27 18:13:57 2004 (418047D5)
eff69000 eff7c000 SAVRTPEL SAVRTPEL.SYS Mon Mar 07 14:49:43 2005 (422CDA87)
eff7c000 effce000 SPBBCDrv SPBBCDrv.sys Wed Jul 21 16:08:26 2004 (40FEF76A)
effce000 effefd00 afd afd.sys Tue Aug 03 23:14:13 2004 (41107EB5)
efff0000 f0017c00 netbt netbt.sys Tue Aug 03 23:14:36 2004 (41107ECC)
f0034000 f0036900 Dxapi Dxapi.sys Fri Aug 17 13:53:19 2001 (3B7D843F)
f0040000 f005ccc0 SYMEVENT SYMEVENT.SYS Tue Jul 19 19:10:15 2005 (42DDB287)
f005d000 f009cce0 SYMTDI SYMTDI.SYS Tue Apr 05 11:10:52 2005 (4252D4AC)
f009d000 f00f4d80 tcpip tcpip.sys Thu Jan 12 18:28:12 2006 (43C7103C)
f00f5000 f0107400 ipsec ipsec.sys Tue Aug 03 23:14:27 2004 (41107EC3)
f8148000 f817b200 update update.sys Tue Aug 03 22:58:32 2004 (41107B08)
f8244000 f8254e00 psched psched.sys Tue Aug 03 23:04:16 2004 (41107C60)
f8255000 f826b680 ndiswan ndiswan.sys Tue Aug 03 23:14:30 2004 (41107EC6)
f826c000 f8294980 bcmwl5 bcmwl5.sys Wed Feb 12 14:25:07 2003 (3E4AC9C3)
f8295000 f82b7e80 USBPORT USBPORT.SYS Tue Aug 03 23:08:34 2004 (41107D62)
f82db000 f82fe980 portcls portcls.sys Tue Aug 03 23:15:47 2004 (41107F13)
f82ff000 f832c6a0 STAC97 STAC97.sys Tue Oct 22 07:36:43 2002 (3DB5627B)
f832d000 f8449c00 AGRSM AGRSM.sys Wed Jan 22 14:47:52 2003 (3E2F1F98)
f844a000 f846c680 ks ks.sys Tue Aug 03 23:15:20 2004 (41107EF8)
f846d000 f8480780 VIDEOPRT VIDEOPRT.SYS Tue Aug 03 23:07:04 2004 (41107D08)
f8481000 f850c280 ati2mtag ati2mtag.sys Mon Jan 20 19:44:36 2003 (3E2CC224)
f8525000 f8528c80 mssmbios mssmbios.sys Tue Aug 03 23:07:47 2004 (41107D33)
f8566000 f8580580 Mup Mup.sys Tue Aug 03 23:15:20 2004 (41107EF8)
f8581000 f85ada80 NDIS NDIS.sys Tue Aug 03 23:14:27 2004 (41107EC3)
f85ae000 f863a480 Ntfs Ntfs.sys Tue Aug 03 23:15:06 2004 (41107EEA)
f863b000 f8651780 KSecDD KSecDD.sys Tue Aug 03 22:59:45 2004 (41107B51)
f8652000 f8663f00 sr sr.sys Tue Aug 03 23:06:22 2004 (41107CDE)
f8664000 f8682780 fltmgr fltmgr.sys Tue Aug 03 23:01:17 2004 (41107BAD)
f8683000 f869a480 atapi atapi.sys Tue Aug 03 22:59:41 2004 (41107B4D)
f869b000 f86b9880 ftdisk ftdisk.sys Fri Aug 17 13:52:41 2001 (3B7D8419)
f86ba000 f86d7480 pcmcia pcmcia.sys Tue Aug 03 23:07:45 2004 (41107D31)
f86d8000 f86e8a80 pci pci.sys Tue Aug 03 23:07:45 2004 (41107D31)
f86e9000 f8716d80 ACPI ACPI.sys Tue Aug 03 23:07:35 2004 (41107D27)
f8738000 f8740c00 isapnp isapnp.sys Fri Aug 17 13:58:01 2001 (3B7D8559)
f8748000 f8756e80 ohci1394 ohci1394.sys Tue Aug 03 23:10:05 2004 (41107DBD)
f8758000 f8765000 1394BUS 1394BUS.SYS Tue Aug 03 23:10:03 2004 (41107DBB)
f8768000 f8772500 MountMgr MountMgr.sys Tue Aug 03 22:58:29 2004 (41107B05)
f8778000 f8784c80 VolSnap VolSnap.sys Tue Aug 03 23:00:14 2004 (41107B6E)
f8788000 f8790e00 disk disk.sys Tue Aug 03 22:59:53 2004 (41107B59)
f8798000 f87a4200 CLASSPNP CLASSPNP.SYS Tue Aug 03 23:14:26 2004 (41107EC2)
f87b8000 f87c4880 rasl2tp rasl2tp.sys Tue Aug 03 23:14:21 2004 (41107EBD)
f87c8000 f87d2200 raspppoe raspppoe.sys Tue Aug 03 23:05:06 2004 (41107C92)
f87d8000 f87e3d00 raspptp raspptp.sys Tue Aug 03 23:14:26 2004 (41107EC2)
f87e8000 f87f0900 msgpc msgpc.sys Tue Aug 03 23:04:11 2004 (41107C5B)
f8818000 f8821f00 termdd termdd.sys Tue Aug 03 22:58:52 2004 (41107B1C)
f8838000 f8841480 NDProxy NDProxy.SYS Fri Aug 17 13:55:30 2001 (3B7D84C2)
f8888000 f8896100 usbhub usbhub.sys Tue Aug 03 23:08:40 2004 (41107D68)
f8898000 f88a0700 netbios netbios.sys Tue Aug 03 23:03:19 2004 (41107C27)
f88b8000 f88c0880 Fips Fips.SYS Fri Aug 17 18:31:49 2001 (3B7DC585)
f88c8000 f88d0700 wanarp wanarp.sys Tue Aug 03 23:04:57 2004 (41107C89)
f88d8000 f88e6d80 arp1394 arp1394.sys Tue Aug 03 22:58:28 2004 (41107B04)
f8928000 f8930d00 intelppm intelppm.sys Tue Aug 03 22:59:19 2004 (41107B37)
f8938000 f8947180 nic1394 nic1394.sys Tue Aug 03 22:58:28 2004 (41107B04)
f8948000 f8952380 imapi imapi.sys Tue Aug 03 23:00:12 2004 (41107B6C)
f8958000 f8964180 cdrom cdrom.sys Tue Aug 03 22:59:52 2004 (41107B58)
f8968000 f8976080 redbook redbook.sys Tue Aug 03 22:59:34 2004 (41107B46)
f8988000 f8996b80 drmk drmk.sys Tue Aug 03 23:07:54 2004 (41107D3A)
f8998000 f89a4e00 i8042prt i8042prt.sys Tue Aug 03 23:14:36 2004 (41107ECC)
f89a8000 f89b5500 Apfiltr Apfiltr.sys Wed Jan 16 18:53:32 2002 (3C463CAC)
f89b8000 f89be200 PCIIDEX PCIIDEX.SYS Tue Aug 03 22:59:40 2004 (41107B4C)
f89c0000 f89c4900 PartMgr PartMgr.sys Fri Aug 17 18:32:23 2001 (3B7DC5A7)
f89c8000 f89cc080 PxHelp20 PxHelp20.sys Fri Jan 03 14:10:17 2003 (3E160A49)
f89d0000 f89d6b00 sisagp sisagp.sys Wed May 22 01:11:07 2002 (3CEB529B)
f89f8000 f89fc500 watchdog watchdog.sys Tue Aug 03 23:07:32 2004 (41107D24)
f8a80000 f8a81000 fdc fdc.sys unavailable (00000000)
f8a88000 f8a8f000 GEARAspiWDM GEARAspiWDM.sys Mon Apr 05 15:37:14 2004 (4071DF9A)
f8a90000 f8a97580 Modem Modem.SYS Tue Aug 03 23:08:04 2004 (41107D44)
f8a98000 f8a9c280 usbohci usbohci.sys Tue Aug 03 23:08:34 2004 (41107D62)
f8aa0000 f8aa6800 usbehci usbehci.sys Tue Aug 03 23:08:34 2004 (41107D62)
f8aa8000 f8aae000 kbdclass kbdclass.sys Tue Aug 03 22:58:32 2004 (41107B08)
f8ab0000 f8ab5a00 mouclass mouclass.sys Tue Aug 03 22:58:32 2004 (41107B08)
f8ab8000 f8abc880 TDI TDI.SYS Tue Aug 03 23:07:47 2004 (41107D33)
f8ac8000 f8accd00 BtnHnd BtnHnd.sys Wed Nov 06 18:00:09 2002 (3DC9C929)
f8ad8000 f8adc580 ptilink ptilink.sys Fri Aug 17 13:49:53 2001 (3B7D8371)
f8ae0000 f8ae4080 raspti raspti.sys Fri Aug 17 13:55:32 2001 (3B7D84C4)
f8af0000 f8af79a0 SYMIDS SYMIDS.SYS Tue Apr 05 11:11:16 2005 (4252D4C4)
f8af8000 f8afd000 flpydisk flpydisk.sys Tue Aug 03 22:59:24 2004 (41107B3C)
f8b08000 f8b0e000 symlcbrd symlcbrd.sys Thu Sep 02 18:56:06 2004 (4137CF36)
f8b18000 f8b1d200 vga vga.sys Tue Aug 03 23:07:06 2004 (41107D0A)
f8b20000 f8b24a80 Msfs Msfs.SYS Tue Aug 03 23:00:37 2004 (41107B85)
f8b28000 f8b2f880 Npfs Npfs.SYS Tue Aug 03 23:00:38 2004 (41107B86)
f8b48000 f8b4b000 BOOTVID BOOTVID.dll Fri Aug 17 13:49:09 2001 (3B7D8345)
f8b4c000 f8b4e480 compbatt compbatt.sys Fri Aug 17 13:57:58 2001 (3B7D8556)
f8b50000 f8b53700 BATTC BATTC.SYS Fri Aug 17 13:57:52 2001 (3B7D8550)
f8b54000 f8b56d80 ACPIEC ACPIEC.sys Fri Aug 17 13:57:55 2001 (3B7D8553)
f8be4000 f8be6280 rasacd rasacd.sys Fri Aug 17 13:55:39 2001 (3B7D84CB)
f8c08000 f8c0b700 CmBatt CmBatt.sys Tue Aug 03 23:07:39 2004 (41107D2B)
f8c24000 f8c26580 ndistapi ndistapi.sys Fri Aug 17 13:55:29 2001 (3B7D84C1)
f8c38000 f8c39b80 kdcom kdcom.dll Fri Aug 17 13:49:10 2001 (3B7D8346)
f8c3a000 f8c3b100 WMILIB WMILIB.SYS Fri Aug 17 14:07:23 2001 (3B7D878B)
f8c5a000 f8c5b480 FUJ02B1 FUJ02B1.sys Tue Jul 31 20:00:21 2001 (3B6770C5)
f8c64000 f8c65100 swenum swenum.sys Tue Aug 03 22:58:41 2004 (41107B11)
f8c84000 f8c85280 USBD USBD.SYS Fri Aug 17 14:02:58 2001 (3B7D8682)
f8c88000 f8c89f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 13:49:37 2001 (3B7D8361)
f8c8a000 f8c8b080 Beep Beep.SYS Fri Aug 17 13:47:33 2001 (3B7D82E5)
f8c8c000 f8c8d080 mnmdd mnmdd.SYS Fri Aug 17 13:57:28 2001 (3B7D8538)
f8c8e000 f8c8f080 RDPCDD RDPCDD.sys Fri Aug 17 13:46:56 2001 (3B7D82C0)
f8cc6000 f8cc7620 SYMDNS SYMDNS.SYS Tue Apr 05 11:10:54 2005 (4252D4AE)
f8cd6000 f8cd7100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 14:07:23 2001 (3B7D878B)
f8d00000 f8d00d00 pciide pciide.sys Fri Aug 17 13:51:49 2001 (3B7D83E5)
f8d01000 f8d01d80 OPRGHDLR OPRGHDLR.SYS Fri Aug 17 13:57:55 2001 (3B7D8553)
f8d34000 f8d34b80 Null Null.SYS Fri Aug 17 13:47:39 2001 (3B7D82EB)
f8dee000 f8deed00 dxgthk dxgthk.sys Fri Aug 17 13:53:12 2001 (3B7D8438)
f8dfd000 f8dfdc00 audstub audstub.sys Fri Aug 17 13:59:40 2001 (3B7D85BC)

Unloaded modules:
ee590000 ee5ba000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ee722000 ee74c000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ef11d000 ef147000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f8de8000 f8de9000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ef6bb000 ef6c8000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ef533000 ef541000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ef147000 ef16a000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f8c9c000 f8c9e000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
efe0e000 efe1e000 Serial.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
efac2000 efad6000 Parport.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f88a8000 f88b1000 processr.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f8b10000 f8b15000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f8be0000 f8be3000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

Hi Gary,

I'm not an expert in reading dumps, but there are several references to FAULTING_IP:
SAVRT+3f874

SAVRT is a Symantec file. Googled for it and here is one of several hits: http://www.mcse.ms/archive182-2004-5-605863.html

Where it is: http://www.file.net/process/savrt.sys.html

From what I'm reading, it can be invoked by other processes.

In that reference there is a Symantec response about fixing the Symantec Redirector.

What I would do is rename that file and see what happens - that may knock out Symantec, but that may pin this problem down.

Otherwise, if its a hardware problem, I think it would be the memory. Did you run MS's memory diagnostic tool?

Did you re seat the memory stick(s)?

Regards - Charles

 

Sudden Shutdown-Black Screen

Hi,
I have run the MS memory diagnostic and it made it through the 1st pass
and 6 of 6 tests. On the 2nd pass, test 3, I got sudden shutdown, black screen.
Restart w/ floppy and ran the test again and got sudden shutdown, black screen
on Pass 2 test 5 of 6. On both tests, prior to sudden shutdown no errors were
found.
Restart without floppy, no error messages, appeared to be normal startup.

Switched the RAM modules, restart without floppy, normal startup went fine.
Restart with floppy and ran Memory Diagnostic again and on Pass 2 got
sudden shutdown as test 6 started.

Restart without floppy, no error messages, seems normal. Amount of Physical
Memory showing in Task Mgr/Performance is correct.

I checked the location of savrt.sys and it is only in Program Files\Norton so I
thought that was ok. The file size is about what the article said it would be.

I have not tried disabling services yet as I interpreted the memory diagnosis
problem as point to a memory issue.

Is this pointing to a RAM issue or motherboard ?
Or something else ?

Thanks for your help !
Gary

 

Try a new Drive !

... me, I would pop in another hard drive leaving the one you remove intact. format and install everything and see what happens ... drives are cheap and spending too much time at the altar (otherwise known as the "Knowledge Base ") can be more frustrating than what I'm proposing. Simple enough - right?

You're welcome, in advance!

~ Mr. Fix It >

 

Sudden Shutdown-Black Screen

Well, unfortunately, this computer came with XP home preloaded and I
can't seem to find the cds that came with it. I believe they were recovery
cds and not the full win xp cd. Not sure how I would install xp without the
cds.

I like the idea but wonder about the memory test results.

Thanks for your suggestion.

Gary

 

Sudden Shutdown Black Screen

Arie,
How would I check the cpu temperature ?

Thanks,
Gary

 

Hi Gary,

Look in the BIOS and see if it supports reporting of CPU temperature.

You have Everest, look at what sensors your system has. Expand Computer > Sensor.

Regards - Charles

 

The Clock Is Ticking

... no offense to anyone but any of us could have reformat the drive, reinstalled the OS and applications and back on track by now - and that includes determining whether the drive was bad or not because it would probably plotzed (crashed) along the way as evidence is was sick ..

 

Hi Mr. Fix It,

Normally I would tend to agree with you're point, but the evidence so far points to problem with either memory or the motherboard.

And the issue isn't time as much as what might be lost in a reformat. The poster's system is working in normal circumstances, only when a CPU intensive load is placed on the system, does it error.

Regards - Charles

 

... OK, I'm with you!

 

Actually that doesn't always resolve problems. In fact that is always the very last step to take. It definitely will not help the OP seeing as there is no disk available to format and reinstall. I can determine a bad drive without reinstalling the OS by using the manufacturers utilities.

 

... yea, but then you don't get to go buy anything!

 

Sudden Shutdown Black Screen

Hi,
This began as BSOD sudden shutdown with Norton Virus Scan and morphed to this topic over time and the changing of symptoms and attempts to diagnose them. Since last post, I have purchased the PC beginner CD and ran a few tests with it. After rebooting with it many times as I went through some of the tests. the computer became very hot and began the sudden shutdowns again, black screen only. The tests, by the way, did not find anything wrong.

After entering the BIOS setup I noticed in the event logs(BIOS not XP) that there was a long string of "Thermal shutdown has occurred" spanning several months, roughly the time of my original problems, can't run complete Norton Virus Scan, can't run Spybot S&D, without sudden shutdown of the computer. So, it appears that in fact maybe there is a termal overheating problem. My question is, what is the fix ?

Additionally, the last sudden shutdown had this event log in BIOs, "POST Error CMOS config error ". This may have been because I set the
boot sequence to begin with the cd instead of A:\ or the Hard Drive. I reset the boot sequence to start with the Hard Drive and the computer
boots up fine once again. But I am still unable to run a complete Norton Virus Scan without the sudden shutdown. No event logs in XP\Control Panel\System etc. So, I have learned alot but still have the original problem. Any suggestions re the thermal shutdown ?

Thanks,
Gary