One of our machines has had BSOD's since 9-15. No known software or hardware additions or updates. The BIOS seems to be the up-to-date version for Dimension 9200 of 2.5.3 This is one of the errors. Additionally there are repeated errors with these particular elements:
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
MODULE_NAME: nt
IMAGE_NAME: ntfs.sys
Also there are a few errors involving IMAGE_NAME: ntkrnlmp.exe. and also Ntfs.sys. Any ideas about this issue?
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Helps\Desktop\Dump Files\100311-35615-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\debug_symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02c10000 PsLoadedModuleList = 0xfffff800`02e55670 Debug session time: Mon Oct 3 14:04:02.113 2011 (UTC - 5:00) System Uptime: 0 days 0:10:47.110 Loading Kernel Symbols ............................................................... ................................................................ .......................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************
Use !analyze -v to get detailed debugging information.
KMODE_EXCEPTION_NOT_HANDLED (1e) 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. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff80002f68ac0, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details: ------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
Turns out RAM was bad. The fix was simple, pull out a DIMM and reboot, press F10 at the Power On Self Test phase, run Memory Check, if problems were found then I shut it down again and replaced the RAM and pulled another stick and repleated. Eventually the memory test found no problems and the RAM in hand was the bad stick.
$39 for new RAM and the CPU is actually upgraded by 1GB. Now it runs as smooth as butter on a bald monkey!
Doing a google search the svchost.exe error is often caused by a Virus. See This
If it's not a virus or malware, run the hardware diagnostics as the hard drive may be failing or is corrupted. Many Dell's have hardware diagnostics on the hard drive accessed by F12 at POST (Power On Self Test). Run the tests to see if anything shows up.
Inspiron 16 5630 Laptop and WD22TB4 Docking Station
Self-built desktop for recording studio application
icctech
6 Posts
3446
1
Posted October 11th, 2011 09:00
Turns out RAM was bad. The fix was simple, pull out a DIMM and reboot, press F10 at the Power On Self Test phase, run Memory Check, if problems were found then I shut it down again and replaced the RAM and pulled another stick and repleated. Eventually the memory test found no problems and the RAM in hand was the bad stick.
$39 for new RAM and the CPU is actually upgraded by 1GB. Now it runs as smooth as butter on a bald monkey!