Unsolved
This post is more than 5 years old
1 Rookie
•
77 Posts
0
10818
April 2nd, 2007 18:00
Here’s a challenge!
Here’s a challenge!
Calling all computer gurus-I need your help!
I got my system in September 2005. Almost from the beginning-I started getting a message-windows has recovered from a serious error along with random BSOD-usually IRQ less or equal driver fault issues-. After troubleshooting with the dump files and running hardware diagnostics –memory tests (all passed)-I changed the video card, RAM, HD and no change-random crashes and the WinDebug analysis shows various things on each crash!-they range from ntkpramp causing crash to usbstor.sys, memory corruption, (even after I change the memory fully), Intel C51sys etc and sometimes unidentified driver fault-fact is there is no single driver identified each time-it is a different process causing a crash-and the fact is the same thing is happening under Vista as well (I set up a dual boot system to see if it was system related)-I have run all the hardwre diagnostics (the long version!) and everything passed everytime-I am just at my wits end and perhaps I should put it out of its misery by shooting it. I have an old Dim233 (now running XP Home) and an Inspiron 8000 (XP Pro) which are rock solid and this latest and greatest is virtually useless as it crashes randomly at least 5 times a day in the middle of something or even when I am not using it will crash! I did a clean install last week and te system still crashes even with minimal software-Windebug analyses still shows random reasons-no single process or driver-I would appreciate any help and I will post two of the dump file messages for perusal if that would help right at the bottom. Maybe I have a lemon! TIA...
Here are my system specs:
Dell Dim 9100 BIOS A03-
3 Ghz HT-2 GB Corsair RAM at 667 Mhz-
WinXP MCE 2005 now with IE 7-all updates current-
HDD-300 GB SATA 3Gb/sec X 2(Seagate Barracuda)-
LG Muti_Drive with lightscribe; Phillips DVD-DL (OEM) writers-
13-1 Internal Card reader (Samsung-Dell OEM)-
Internal Floppy HDD-
Nvidia GeForce 256 MB9600 GS PCI Express (Retail)-
Hauppage WINTV PVR PCI for MCE-
SoundBlaster Audigy 2 (Internal PCI)-
Intel Modem and Network cards (OEM)-
External USB Linksys WUSB 54G card-
Office 2003-AVG anti-virus-
ZA 7.0., Active Sync 4.2, Windows defender
____________________________________________________________
DUMP FILE analysIs follows (sorry its long)
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini040207-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:Program Files\WinDebug\symbols*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_gdr.061219-0316
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Apr 2 10:37:40.265 2007 (GMT-5)
System Uptime: 0 days 1:21:19.971
Loading Kernel Symbols
............................................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 805503d3, b9810c58, b9810954}
Unable to load image IntelC52.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for IntelC52.sys
*** ERROR: Module load completed but symbols could not be loaded for IntelC52.sys
Probably caused by : ntkrpamp.exe ( nt!KiDoubleFaultStack+2cd3 )
Followup: MachineOwner
---------
1: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: 805503d3, The address that the exception occurred at
Arg3: b9810c58, Exception Record Address
Arg4: b9810954, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt!KiDoubleFaultStack+2cd3
805503d3 80b0ff19b92830 xor byte ptr [eax+28B919FFh],30h
EXCEPTION_RECORD: b9810c58 -- (.exr ffffffffb9810c58)
ExceptionAddress: 805503d3 (nt!KiDoubleFaultStack+0x00002cd3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 28b91a03
Attempt to write to address 28b91a03
CONTEXT: b9810954 -- (.cxr ffffffffb9810954)
eax=00000004 ebx=00000000 ecx=b8f3ab60 edx=00000000 esi=804fa034 edi=804fa0ec
eip=805503d3 esp=b9810d20 ebp=b9810dac iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210202
nt!KiDoubleFaultStack+0x2cd3:
805503d3 80b0ff19b92830 xor byte ptr [eax+28B919FFh],30h ds:0023:28b91a03=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
WRITE_ADDRESS: 28b91a03
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 805ce84c to 805503d3
STACK_TEXT:
b9810dac 805ce84c 892a3cd0 00000000 00000000 nt!KiDoubleFaultStack+0x2cd3
b9810ddc 8054532e b8edf707 892a3cd0 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
nt!KiDoubleFaultStack+2cd3
805503d3 80b0ff19b92830 xor byte ptr [eax+28B919FFh],30h
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4587e148
SYMBOL_NAME: nt!KiDoubleFaultStack+2cd3
STACK_COMMAND: .cxr 0xffffffffb9810954 ; kb
FAILURE_BUCKET_ID: 0x7E_nt!KiDoubleFaultStack+2cd3
BUCKET_ID: 0x7E_nt!KiDoubleFaultStack+2cd3
Followup: MachineOwner
******************************************************************************
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini033107-06.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:Program Files\WinDebug\symbols*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_gdr.061219-0316
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Mar 31 14:33:27.562 2007 (GMT-5)
System Uptime: 0 days 3:54:08.268
Loading Kernel Symbols
............................................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 0, bacdfbb4, bacdf8b0}
Probably caused by : ntkrpamp.exe ( nt!CcUnmapVacbArray+e5 )
Followup: MachineOwner
---------
0: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: 00000000, The address that the exception occurred at
Arg3: bacdfbb4, Exception Record Address
Arg4: bacdf8b0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
+0
00000000 ?? ???
EXCEPTION_RECORD: bacdfbb4 -- (.exr ffffffffbacdfbb4)
ExceptionAddress: 00000000
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000008
Parameter[1]: 00000000
Attempt to execute non-executable address 00000000
CONTEXT: bacdf8b0 -- (.cxr ffffffffbacdf8b0)
eax=0000000e ebx=00000000 ecx=00000050 edx=00004ee4 esi=8a1a4a68 edi=88644008
eip=00000000 esp=bacdfc7c ebp=c061ec08 iopl=0 nv up ei ng nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287
00000000 ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 6
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
WRITE_ADDRESS: 00000000
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 8a1a4a68 to 00000000
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
bacdfc78 8a1a4a68 bacdfcb0 804e81ad 8a1a4a68 0x0
bacdfc80 804e81ad 8a1a4a68 88644008 00000000 0x8a1a4a68
bacdfcb0 804e51ec 00000000 00000000 8864406c nt!CcUnmapVacbArray+0xe5
bacdfccc 804e54a7 88644008 806e4a4c 88644008 nt!CcUnmapAndPurge+0x20
bacdfcfc 804e4aa9 00000001 80558690 8951cd80 nt!CcDeleteSharedCacheMap+0xc5
bacdfd34 804e7081 8a1b7288 80563720 8a1b9b88 nt!CcWriteBehind+0x357
bacdfd7c 805379bd 8a1b7288 00000000 8a1b9b88 nt!CcWorkerThread+0x12f
bacdfdac 805ce84c 8a1b7288 00000000 00000000 nt!ExpWorkerThread+0xef
bacdfddc 8054532e 805378ce 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
nt!CcUnmapVacbArray+e5
804e81ad 6a04 push 4
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!CcUnmapVacbArray+e5
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4587e148
STACK_COMMAND: .cxr 0xffffffffbacdf8b0 ; kb
FAILURE_BUCKET_ID: 0x7E_nt!CcUnmapVacbArray+e5
BUCKET_ID: 0x7E_nt!CcUnmapVacbArray+e5
Followup: MachineOwner
---------


BELL BOY
1.1K Posts
0
April 3rd, 2007 00:00
Depends on what changes/modifications (if any) have been made since original purchase or/& the BSoD etc, problems started.
Could be software & possibly hardware conflict problems, doubt there is a one-fix solution?
Unless you have extended warranty cover, options are:
Take your computer to a reputable PC repair shop to obtain a quote for guaranteed repair work.
Or a potential lengthy DIY investigation job to determine if the original computer was a lemon purchase!
Based on what you report, using the usual Windows troubleshooting commands like chkdsk /r or Recovery Console etc., may not identify the problem?
If you have made any significant changes/modifications since original purchase it’s probably necessary to go back to original Hardware & Software build spec status.
HardwareAssuming the replacement parts you mention are genuine & compatible (double-check your memory sticks) with original spec, then if relevant remove any/all other hardware installed since original build & also check all cable connections.
SoftwareUnless you intend to go around in circles?
With only monitor, keyboard & mouse peripherals connected to your PC.
Best to carry out a by the book, complete clean install of original operating system, includes using FULL formatting HDD (NTFS file system), installing ALL original drivers & in the correct order (Dell system drivers) & don’t forget the chipset driver.
Now work off-line to check if there are any conflicts or error problems – if any then use diagnostics tools.
At this stage you may be able to determine if it is indeed a lemon?
Only if there are no problems, should you proceed in a logical step-by-step process by installing each software application then rechecking for problems before going any further.
First install Firewall/AV software then go on-line for Windows updates.
After that it’s up to you on the sequence of software & hardware installs.
But unless you fully test after each install step, you will soon be back to square one – trying to fathom out the problem(s).
Good luck
dummy
1 Rookie
•
77 Posts
0
April 3rd, 2007 01:00
anonim
1 Rookie
•
109 Posts
0
April 3rd, 2007 04:00
What are peripheral attached to your computer?
dummy
1 Rookie
•
77 Posts
0
April 3rd, 2007 09:00
anonim
1 Rookie
•
109 Posts
0
April 3rd, 2007 16:00
All USB devices takes some power from USB port. Each attached internal device (HDD, FDD, CD/DVD, PCI or other kind of cards etc.) uses power.
If the power source cannot supply the power a device needs, Windows just crashes. You cannot do anything about it. This crash is random, so you don't know when the system will crash next time and who makes it crash.
I had the same problem and I had to replace the power source with 500W and now everything is OK.
dummy
1 Rookie
•
77 Posts
0
April 3rd, 2007 23:00
anonim
1 Rookie
•
109 Posts
0
April 4th, 2007 04:00
You can ask at Dell if they have any power supply with 500W or more if your computer in in warranty.
I don't say that power supply IS the problem in your case, but MOST LIKELY is the problem. It was the problem in my case.
Message Edited by anonim on 04-04-2007 12:37 AM
dummy
1 Rookie
•
77 Posts
0
April 4th, 2007 11:00
dummy
1 Rookie
•
77 Posts
0
April 7th, 2007 11:00
dummy
1 Rookie
•
77 Posts
0
April 7th, 2007 11:00
Dell Dim 9100 BIOS A03
3 Ghz HT-2 GB Corsair RAM at 667 Mhz-
WinXP MCE 2005 now with IE 7-all updates current-
HDD-300 GB SATA 3Gb/sec X 2(Seagate Barracuda)-
LG Muti_Drive with lightscribe; Phillips DVD-DL (OEM) writers-
13-1 Internal Card reader (Samsung-Dell OEM)-
Internal FDD-
Nvidia GeForce 256 MB 9600 GS PCI Express (Retail)-
Hauppage WINTV PVR 150 PCI for MCE-
SoundBlaster Audigy 2 (Internal PCI)-
Intel Modem and Network cards (OEM)-
External USB Linksys WUSB 54G card-
Office 2003-AVG anti-virus-
ZA 7.0., Active Sync 4.2, Windows defender
Dimension XPS D233
224 MHz, 40 GB Seagate HD
LG and Samsung CDRW, ZIP Drives
NIC, Pinnacle PCTV,
WinXPHome SP2
Office 97-SP2 w/OL 98
Inspiron 8000
P III 1 GHz, 384 MB, 60 GB IBM Deskstar (7200 RPM) HDD
NEC ND 7550A DVD-R/RW/DL (internal)
Win XP Pro-SP2
Mediacom cable on Toshiba PCX 1100U
Linksys 54G wireless Router
Astra 3400U, Samsung ML1430
Office 2003 w/ FP 2002 & Adobe Photoshop elemnts 3.0
NSW 2006, ZA 7, Windows defender
anonim
1 Rookie
•
109 Posts
0
April 7th, 2007 15:00
This is a very good reason for randomly crashes. Better go to some shop where they can test this.
dummy
1 Rookie
•
77 Posts
0
April 7th, 2007 16:00
Dell Dim 9100 BIOS A03
3 Ghz HT-2 GB Corsair RAM at 667 Mhz-
WinXP MCE 2005 now with IE 7-all updates current-
HDD-300 GB SATA 3Gb/sec X 2(Seagate Barracuda)-
LG Muti_Drive with lightscribe; Phillips DVD-DL (OEM) writers-
13-1 Internal Card reader (Samsung-Dell OEM)-
Internal FDD-
Nvidia GeForce 256 MB 9600 GS PCI Express (Retail)-
Hauppage WINTV PVR 150 PCI for MCE-
SoundBlaster Audigy 2 (Internal PCI)-
Intel Modem and Network cards (OEM)-
External USB Linksys WUSB 54G card-
Office 2003-AVG anti-virus-
ZA 7.0., Active Sync 4.2, Windows defender
Dimension XPS D233
224 MHz, 40 GB Seagate HD
LG and Samsung CDRW, ZIP Drives
NIC, Pinnacle PCTV,
WinXPHome SP2
Office 97-SP2 w/OL 98
Inspiron 8000
P III 1 GHz, 384 MB, 60 GB IBM Deskstar (7200 RPM) HDD
NEC ND 7550A DVD-R/RW/DL (internal)
Win XP Pro-SP2
Mediacom cable on Toshiba PCX 1100U
Linksys 54G wireless Router
Astra 3400U, Samsung ML1430
Office 2003 w/ FP 2002 & Adobe Photoshop elemnts 3.0
NSW 2006, ZA 7, Windows defenderst and tech support online or live has been woefully inadequate!
dummy
1 Rookie
•
77 Posts
0
May 21st, 2007 01:00
I think the problem I had of random BSODs looks like it has been solved. The new thermal paste helped-and that got me thinking-after I did some research, I realized that my Prescott 3 Ghz HT processor may be the one heating up and crashing the machine-because the same problems happened under Vista as well. Even though I had bought a new mobo, instead of swapping the old one out, I bought an OEM Pentium D 940 (Presler-Dual core 3.2 Ghz) from Tiger Direct for $109 and installed it with the paste yesterday and would you believe it?-No crashes -system running heavy loads for over 6 hours now -no BSODs at all! Vista and XP running great-with the old mobo itself! Hope this helps someone-I will keep the post alive-I still want to see how the machine does after a week...
Update-after more than 10 hours with multitasking-not even one crash-the fans are running a lot cooler as well (just by tactile sensation on the case side)-I would stay away from the Prescotts unless you can leave the case open I think-the Presler Penium D is great and the Dell A03 BIOS recognized it w/out any problem and XP and Vista did not ask for reactivation also! Thanks to all who volunteered thier help for me...
Final Post-success at last! 5 days after change in processors and not a single crash!!! Final verdict-guilty of heat related injury-Prescott 630 HT processor-condemned to sit in solitary confinement!!
Cheers! over and out!