robbel1
asked on
Windows xp reboots
Three weeks ago a put a few bits together. Asrock AS741 motherboard, AMD 2600 cpu, DDr 400Mhz 512meg, Nvida 5700 graphics card
The machine randomly kept showing the screen of death so i went about fixing it. So far I have updated all the drivers, changed the original hard drive, changed the power pack to 450V, formated the hard drive and reinstalled windows xp - this was very difficult as the machine kept rebooting at exactly 34 minutes left until it finally worked ( i had previously installed service pack 2 - heard it can cause problems) still kept crashing although at some time stopped showing the blue screen and started rebooting.
Today a changed the memory - machine was fine all day at work but when i got home rebooted 6 times in 10 mins after I activated parental controls on BT Yahoo - although i think the two things are not related.
Created a disk splicing windows xp and service pack 2 together but when I try to boot from it the machine restarts.
i have run all the diagnostic tools nothing comes up wrong although the machine sometimes reboots before they have finished. Software that monitors cpu and case temp say they are fine.
The machine is going out of the window in one week.
So your challenge is - what the bloody hell is going on..........
Processor
Model : AMD Athlon(tm) XP 2600+
Speed : 1.93GHz
Model Number : 2600 (estimated)
Performance Rating : PR2801 (estimated)
Type : Standard
L2 On-board Cache : 512kB ECC Synchronous, Write-Back, 16-way set, 64 byte line size
Mainboard
Bus(es) : ISA AGP PCI USB i2c/SMBus
MP Support : 1 CPU(s)
MP APIC : No
System BIOS : American Megatrends Inc. P1.70
System : American Megatrends Inc. K7S41
Mainboard : K7S41
Total Memory : 512MB DDR-SDRAM
Chipset 1
Model : ASRock Inc SiS741 CPU to PCI Bridge
Front Side Bus Speed : 2x 168MHz (336MHz data rate)
Total Memory : 512MB DDR-SDRAM
Memory Bus Speed : 2x 168MHz (336MHz data rate)
Video System
Monitor/Panel : Plug and Play Monitor
Adapter : NVIDIA GeForce FX 5700LE
Imaging Device : Logitech QuickCam Web
Physical Storage Devices
Removable Drive : Floppy disk drive
Hard Disk : SAMSUNG SP0812N (75GB)
CD-ROM/DVD : LITE-ON DVDRW SOHW-1633S (CD 48X Rd, 48X Wr) (DVD 6X Rd, 6X Wr)
CD-ROM/DVD : TEAC CD-W58E (CD 8X Rd, 4X Wr)
Logical Storage Devices
1.44MB 3.5" (A:) : N/A
Hard Disk (C:) : 75GB (70GB, 93% Free Space) (NTFS)
CD-ROM/DVD (D:) : N/A
Wxpccp_en (E:) : 627MB (CDFS)
Peripherals
Serial/Parallel Port(s) : 1 COM / 1 LPT
USB Controller/Hub : SiS 7001 PCI to USB Open Host Controller
USB Controller/Hub : SiS 7001 PCI to USB Open Host Controller
USB Controller/Hub : SiS PCI to USB Enhanced Host Controller
USB Controller/Hub : USB Root Hub
USB Controller/Hub : USB Root Hub
USB Controller/Hub : USB Root Hub
USB Controller/Hub : Logitech USB Camera (Web)
USB Controller/Hub : USB Composite Device
Keyboard : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
Keyboard : HID Keyboard Device
Mouse : HID-compliant mouse
Human Interface : HID-compliant game controller
Human Interface : HID-compliant consumer control device
Human Interface : HID-compliant device
Human Interface : HID-compliant device
Human Interface : USB Human Interface Device
Human Interface : USB Human Interface Device
Human Interface : USB Human Interface Device
MultiMedia Device(s)
Device : Standard Game Port
Device : C-Media AC97 Audio Device
The machine randomly kept showing the screen of death so i went about fixing it. So far I have updated all the drivers, changed the original hard drive, changed the power pack to 450V, formated the hard drive and reinstalled windows xp - this was very difficult as the machine kept rebooting at exactly 34 minutes left until it finally worked ( i had previously installed service pack 2 - heard it can cause problems) still kept crashing although at some time stopped showing the blue screen and started rebooting.
Today a changed the memory - machine was fine all day at work but when i got home rebooted 6 times in 10 mins after I activated parental controls on BT Yahoo - although i think the two things are not related.
Created a disk splicing windows xp and service pack 2 together but when I try to boot from it the machine restarts.
i have run all the diagnostic tools nothing comes up wrong although the machine sometimes reboots before they have finished. Software that monitors cpu and case temp say they are fine.
The machine is going out of the window in one week.
So your challenge is - what the bloody hell is going on..........
Processor
Model : AMD Athlon(tm) XP 2600+
Speed : 1.93GHz
Model Number : 2600 (estimated)
Performance Rating : PR2801 (estimated)
Type : Standard
L2 On-board Cache : 512kB ECC Synchronous, Write-Back, 16-way set, 64 byte line size
Mainboard
Bus(es) : ISA AGP PCI USB i2c/SMBus
MP Support : 1 CPU(s)
MP APIC : No
System BIOS : American Megatrends Inc. P1.70
System : American Megatrends Inc. K7S41
Mainboard : K7S41
Total Memory : 512MB DDR-SDRAM
Chipset 1
Model : ASRock Inc SiS741 CPU to PCI Bridge
Front Side Bus Speed : 2x 168MHz (336MHz data rate)
Total Memory : 512MB DDR-SDRAM
Memory Bus Speed : 2x 168MHz (336MHz data rate)
Video System
Monitor/Panel : Plug and Play Monitor
Adapter : NVIDIA GeForce FX 5700LE
Imaging Device : Logitech QuickCam Web
Physical Storage Devices
Removable Drive : Floppy disk drive
Hard Disk : SAMSUNG SP0812N (75GB)
CD-ROM/DVD : LITE-ON DVDRW SOHW-1633S (CD 48X Rd, 48X Wr) (DVD 6X Rd, 6X Wr)
CD-ROM/DVD : TEAC CD-W58E (CD 8X Rd, 4X Wr)
Logical Storage Devices
1.44MB 3.5" (A:) : N/A
Hard Disk (C:) : 75GB (70GB, 93% Free Space) (NTFS)
CD-ROM/DVD (D:) : N/A
Wxpccp_en (E:) : 627MB (CDFS)
Peripherals
Serial/Parallel Port(s) : 1 COM / 1 LPT
USB Controller/Hub : SiS 7001 PCI to USB Open Host Controller
USB Controller/Hub : SiS 7001 PCI to USB Open Host Controller
USB Controller/Hub : SiS PCI to USB Enhanced Host Controller
USB Controller/Hub : USB Root Hub
USB Controller/Hub : USB Root Hub
USB Controller/Hub : USB Root Hub
USB Controller/Hub : Logitech USB Camera (Web)
USB Controller/Hub : USB Composite Device
Keyboard : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
Keyboard : HID Keyboard Device
Mouse : HID-compliant mouse
Human Interface : HID-compliant game controller
Human Interface : HID-compliant consumer control device
Human Interface : HID-compliant device
Human Interface : HID-compliant device
Human Interface : USB Human Interface Device
Human Interface : USB Human Interface Device
Human Interface : USB Human Interface Device
MultiMedia Device(s)
Device : Standard Game Port
Device : C-Media AC97 Audio Device
Take a look at the following web page,
http://aumha.org/win5/kbestop.htm
which is presented using frames. Click on the error code (0A) in the left pane of the page, which is a link to the following quotation:
0x0000000A: IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1539.)
Typically due to a bad driver, or faulty or incompatible hardware or software. Use the General Troubleshooting of STOP Messages checklist above. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)
Troubleshooting “Stop 0x0A” Messages in Windows {KB 165863} Win NT, Win 2000, Win XP
Troubleshooting a Stop 0x0000000A Error in Windows XP {KB 314063} Win XP
Possible Resolutions to STOP 0x0A, 0x01E, and 0x50 Errors {KB 183169} Win NT, Win 2000, Win XP
During upgrade to Win XP {KB 311564} Win XP
STOP 0x0000000A Error Message When You Change from AC Power to DC Power {KB 316676} Win XP
“Stop 0x0000000A” Error Message When You Fast Switch Between Users {KB 310918} Win XP
While booting NT on same partition as Win 2000 or XP {KB 227301} Win NT, Win 2000, Win XP
Partial List of Driver Error Codes That the Driver Verifier Tool Uses to Report Problems {KB 315252} Win XP
Windows XP Restarts When You Try to Shut Down Your Computer {KB 311806}
“Fatal System Error” When You Try to Use a Hewlett-Packard 5100C ScanJet {KB 307129} Win XP (with Brother printer)
Computer May Hang During a Heavy Load with an Ericsson HIS Modem {KB 319810} Win 2000, Win XP
STOP 0x4E, STOP 0x1A, STOP 0x50, and STOP 0xA Errors Occur When You Try to Start the Computer {KB 271955} Win NT 4.0 (corrupt physical RAM)
“Stop: 0x0000000A (00000063, 0000001c, 00000000, parameter4)” error message on a Windows 2000-based computer {KB 837384} Win 2000 (program error, hotfix available)
You should go to the actual page in order to read the links given in the quotation above.
http://aumha.org/win5/kbestop.htm
which is presented using frames. Click on the error code (0A) in the left pane of the page, which is a link to the following quotation:
0x0000000A: IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1539.)
Typically due to a bad driver, or faulty or incompatible hardware or software. Use the General Troubleshooting of STOP Messages checklist above. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)
Troubleshooting “Stop 0x0A” Messages in Windows {KB 165863} Win NT, Win 2000, Win XP
Troubleshooting a Stop 0x0000000A Error in Windows XP {KB 314063} Win XP
Possible Resolutions to STOP 0x0A, 0x01E, and 0x50 Errors {KB 183169} Win NT, Win 2000, Win XP
During upgrade to Win XP {KB 311564} Win XP
STOP 0x0000000A Error Message When You Change from AC Power to DC Power {KB 316676} Win XP
“Stop 0x0000000A” Error Message When You Fast Switch Between Users {KB 310918} Win XP
While booting NT on same partition as Win 2000 or XP {KB 227301} Win NT, Win 2000, Win XP
Partial List of Driver Error Codes That the Driver Verifier Tool Uses to Report Problems {KB 315252} Win XP
Windows XP Restarts When You Try to Shut Down Your Computer {KB 311806}
“Fatal System Error” When You Try to Use a Hewlett-Packard 5100C ScanJet {KB 307129} Win XP (with Brother printer)
Computer May Hang During a Heavy Load with an Ericsson HIS Modem {KB 319810} Win 2000, Win XP
STOP 0x4E, STOP 0x1A, STOP 0x50, and STOP 0xA Errors Occur When You Try to Start the Computer {KB 271955} Win NT 4.0 (corrupt physical RAM)
“Stop: 0x0000000A (00000063, 0000001c, 00000000, parameter4)” error message on a Windows 2000-based computer {KB 837384} Win 2000 (program error, hotfix available)
You should go to the actual page in order to read the links given in the quotation above.
Upgrade NVIDIA GeForce FX 5700LE display card driver as I've resolved 4 cases relating to faulty NVIDIA display card cause XP crash with bugcheck code 0A, 50 and 8E.
Check system evnent log and look for record id 1001. If you find bugcheck code 0A, 50 and 8E, I believe that it is worth while to upgrade Nvidia Display card driver.
Procedure to find system event log
Control Panel --> Adminstrative tools --> Event Viewe --> System --> Record id 1001 (ie sysdump).
Procedure to find system event log
Control Panel --> Adminstrative tools --> Event Viewe --> System --> Record id 1001 (ie sysdump).
I had a similar problem andfigured it out thus:
1) Does this happen in safe mode? If it does then we are back to hardware.
2) On a hunch, (this is how i got through), disable the Video card from device manager. Trust me, the screen would not go blank. If you don't get the restarts(I did not) and you have installed the latest Nvidia display drivers(as I had), then you would want to zero in on the video card.
In any case, the procedure if it works in safe mode is, you need to disable items in the device manager one by one till you find the culprit.
1) Does this happen in safe mode? If it does then we are back to hardware.
2) On a hunch, (this is how i got through), disable the Video card from device manager. Trust me, the screen would not go blank. If you don't get the restarts(I did not) and you have installed the latest Nvidia display drivers(as I had), then you would want to zero in on the video card.
In any case, the procedure if it works in safe mode is, you need to disable items in the device manager one by one till you find the culprit.
ASKER
Thanks for all the help so far.
I had already updated all my drivers. I have aslo tried removing the graphics card and disbled the driver - system still crashes.
Help only six days and its out of the window....................
ASKER
Just rebooted in safe mode and run CPU stability test 5.0 in hardcore mode.
got an mmx test failed
error code:1
calculation error
does this maen it has been my cpu all along
only 5 and a half days left -- help............
got an mmx test failed
error code:1
calculation error
does this maen it has been my cpu all along
only 5 and a half days left -- help............
Whenever windows crashes, a system event 1001 record and a minidump is written.
Control Panel -> Adminstrative Tools -> Event Viewer -> System -> Record 1001.
Can you copy the content of all the record 1001 and paste them back here and it will help me to find out the culprit.
Control Panel -> Adminstrative Tools -> Event Viewer -> System -> Record 1001.
Can you copy the content of all the record 1001 and paste them back here and it will help me to find out the culprit.
Can you attach the last minidump to any webspace so I can process the dump and find out the culprit. You can find the minidump at the folder \windows\minidump\*.dmp
Run ramtest and you can download it from http://www.memtest86.com and use Prime 95 (CPU test utility) http://www.mersenne.org/freesoft.htm.
ASKER
here are the last few 1001 minidumps - hope it helps
sorry dont understand the webspace bit
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 25/11/2004
Time: 14:12:02
User: N/A
Computer: HOME-XVLC1HI3PV
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbf87a1fa, 0xf682ca44, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini11
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 25/11/2004
Time: 13:24:49
User: N/A
Computer: HOME-XVLC1HI3PV
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbf87fb60, 0xf5227b98, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini11
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 25/11/2004
Time: 13:23:10
User: N/A
Computer: HOME-XVLC1HI3PV
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x8053cbb1, 0xf45ede38, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini11
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 25/11/2004
Time: 10:25:22
User: N/A
Computer: HOME-XVLC1HI3PV
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0900808e, 0x000000ff, 0x00000000, 0x804ecabb). A dump was saved in: C:\WINDOWS\Minidump\Mini11
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 24/11/2004
Time: 21:38:06
User: N/A
Computer: HOME-XVLC1HI3PV
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x00000004, 0x00000002, 0x00000000, 0x804efb93). A dump was saved in: C:\WINDOWS\Minidump\Mini11
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 24/11/2004
Time: 18:44:53
User: N/A
Computer: HOME-XVLC1HI3PV
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x8053cf89, 0xf8a11bd0, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini11
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
sorry dont understand the webspace bit
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 25/11/2004
Time: 14:12:02
User: N/A
Computer: HOME-XVLC1HI3PV
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbf87a1fa, 0xf682ca44, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini11
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 25/11/2004
Time: 13:24:49
User: N/A
Computer: HOME-XVLC1HI3PV
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbf87fb60, 0xf5227b98, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini11
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 25/11/2004
Time: 13:23:10
User: N/A
Computer: HOME-XVLC1HI3PV
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x8053cbb1, 0xf45ede38, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini11
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 25/11/2004
Time: 10:25:22
User: N/A
Computer: HOME-XVLC1HI3PV
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0900808e, 0x000000ff, 0x00000000, 0x804ecabb). A dump was saved in: C:\WINDOWS\Minidump\Mini11
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 24/11/2004
Time: 21:38:06
User: N/A
Computer: HOME-XVLC1HI3PV
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x00000004, 0x00000002, 0x00000000, 0x804efb93). A dump was saved in: C:\WINDOWS\Minidump\Mini11
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 24/11/2004
Time: 18:44:53
User: N/A
Computer: HOME-XVLC1HI3PV
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x8053cf89, 0xf8a11bd0, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini11
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
How do you disable the display card driver?
ASKER
ran ram test before was fine i have also changed my ram
ASKER
through device manager display options right click disable
I doubt whether you can disable display card using device manager. If you can attach the minidump to any webspace and I can confirm whether your display card driver is disable or not.
From the last three event record, your PC crashes with bugcheck code 8E and the failing module is win32k.sys (Base upon the failing instructioin address, I guess it is win32k.sys because I don't have the minidump). I don't think win32k.sys is the culprit as it is windows core component. I suggest you upgrade nVidia Display Card Driver as you can uninstall the display card driver at any any time. It is worth while to try as the download and upgrade only takes around 20 mins.
From the last three event record, your PC crashes with bugcheck code 8E and the failing module is win32k.sys (Base upon the failing instructioin address, I guess it is win32k.sys because I don't have the minidump). I don't think win32k.sys is the culprit as it is windows core component. I suggest you upgrade nVidia Display Card Driver as you can uninstall the display card driver at any any time. It is worth while to try as the download and upgrade only takes around 20 mins.
ASKER
thanks for the advce but i downloaded the nVidia Display card driver a few days ago after I replaced the graphics card still no change. How do i save the dump and send it to you?
Go to google and search the free webspace as some free webspace provide freespace from photos and html.
I also want your software list
Run msinfo32 and navigate to Software > Program Group. Click anywhere in the right pane. Press CTRL-A and then CTRL-C. Copy that data to the clipboard and paste that data here.
I also want your software list
Run msinfo32 and navigate to Software > Program Group. Click anywhere in the right pane. Press CTRL-A and then CTRL-C. Copy that data to the clipboard and paste that data here.
Ok,
I wonder if you've had a look at the Blue screen when the system actually stopped. What I'm trying to verify is if it was a STOP or Bugcheck and as a resource tells me, these 2 codes usually don't come without a file name.
Just in case u don't know: Right CLick My computer->Properties->adva
Although that MMX test was pretty damning.
I wonder if you've had a look at the Blue screen when the system actually stopped. What I'm trying to verify is if it was a STOP or Bugcheck and as a resource tells me, these 2 codes usually don't come without a file name.
Just in case u don't know: Right CLick My computer->Properties->adva
Although that MMX test was pretty damning.
hey....this problem is usually caused by a USB device...I had a similar problem...but I figured it after hours of working on it - went upto the point of frustration!!...you have pointed out "Logitech USB Camera" "HID" and "Game Controllers" on the hardware list...disconnect the USB devices and see how the system performs......if it goes good - i.e. without restart...that is a positive sign :)...let me know how it goes...Cheers!
If you provide your email address here, all the experts which are interested to read the minidump will email you to get a copy of the minidump. Are you using XP SP1 or SP2? If you are using SP2, the outdated nVidia Display Card crashes XP SP2.
I'm afraid that your display card driver is not the latest.
I've just resolved a system crash problem relating to nVidia Display Card Driver.
https://www.experts-exchange.com/questions/21221550/stop-0x000000008e-when-starting-windows.html
I'm afraid that your display card driver is not the latest.
I've just resolved a system crash problem relating to nVidia Display Card Driver.
https://www.experts-exchange.com/questions/21221550/stop-0x000000008e-when-starting-windows.html
I've put my email address in my profile.
Hi Robbel1,
Have you fixed your problem? If not, email the minidump to me and you find the minidump at the folder \windows\minidump
cpc2004
Have you fixed your problem? If not, email the minidump to me and you find the minidump at the folder \windows\minidump
cpc2004
ASKER
Problem is not yet fixed. When I send the minidump (as attachment?) what do I save it as?
Thanks for all your help - been away for a few days hence the delay.
Robbel1
Send the minidump as attachment.
I've studied your minidump. My conclusion 60% is software driver problem and 40% is related faulty ram.
Mini112904-07.dmp 0x1000008E (0xc0000005, 0x8053cf89, 0xf8675a68, 0x00000000) ( win32k+7c978 )
Mini112904-08.dmp 0x0000000A (0xf000ed8a, 0x00000002, 0x00000000, 0x804ec969) ( win32k+7a2b2 )
Mini112904-09.dmp 0x10000050 (0xe6212e57, 0x00000000, 0x8053cf89, 0x00000002) ( win32k+7c978 )
Mini112904-10.dmp 0x1000008E (0xc0000005, 0x804da121, 0xf8968cf4, 0x00000000) ( sr+d2c3 )
Mini112904-07.dmp and Mini112904-09.dmp have the same failing instruction address, that is the reason why I think software problem is higher than hardware problem. Usually hardware problem generates unpredicatable result, the system crash does not have pattern.
Suggestion
1. Your windows core component such as ntoskrnl.exe and win32k.sys are two years behind. Your service level of XP SP1 is very low. It had better upgrade to highest patch at SP1 and I don't suggest you upgrade SP2. As I find a some of your drivers are very old. Upgrade to SP2 will cause more system crashes.
804d4000 806c6980 nt ntoskrnl.exe Thu Aug 29 17:03:24 2002 (3D6DE35C) <-- 2 years behnid
806c7000 806e6380 hal hal.dll Thu Aug 29 16:05:02 2002 (3D6DD5AE)
bf800000 bf9bac80 win32k win32k.sys Thu Aug 29 17:14:13 2002 (3D6DE5E5) <-- 2 years behind
f8bf5000 f8bf5740 BCMNTIO BCMNTIO.SYS Sat Jun 20 08:25:06 1998 (358B0162)
f8bfd000 f8bfdc00 audstub audstub.sys Sat Aug 18 04:59:40 2001 (3B7D85BC)
f8c18000 f8c188a0 MAPMEM MAPMEM.SYS Sat May 09 05:25:04 1998 (35537830)
f8c19000 f8c19fc0 HSMPORT HSMPORT.SYS Tue Jun 03 03:35:25 1997 (3393207D)
2. It is worthwhile to stress test your hardware and make sure it has no hardware problem such as faulty ram, faculty cache memory at CPU and meory, bad PSU (power supply unit).
Download Prime 95 to stress test your hardware http://www.mersenne.org/freesoft.htm
Hope it can help you.
cpc2004
Mini112904-07.dmp 0x1000008E (0xc0000005, 0x8053cf89, 0xf8675a68, 0x00000000) ( win32k+7c978 )
Mini112904-08.dmp 0x0000000A (0xf000ed8a, 0x00000002, 0x00000000, 0x804ec969) ( win32k+7a2b2 )
Mini112904-09.dmp 0x10000050 (0xe6212e57, 0x00000000, 0x8053cf89, 0x00000002) ( win32k+7c978 )
Mini112904-10.dmp 0x1000008E (0xc0000005, 0x804da121, 0xf8968cf4, 0x00000000) ( sr+d2c3 )
Mini112904-07.dmp and Mini112904-09.dmp have the same failing instruction address, that is the reason why I think software problem is higher than hardware problem. Usually hardware problem generates unpredicatable result, the system crash does not have pattern.
Suggestion
1. Your windows core component such as ntoskrnl.exe and win32k.sys are two years behind. Your service level of XP SP1 is very low. It had better upgrade to highest patch at SP1 and I don't suggest you upgrade SP2. As I find a some of your drivers are very old. Upgrade to SP2 will cause more system crashes.
804d4000 806c6980 nt ntoskrnl.exe Thu Aug 29 17:03:24 2002 (3D6DE35C) <-- 2 years behnid
806c7000 806e6380 hal hal.dll Thu Aug 29 16:05:02 2002 (3D6DD5AE)
bf800000 bf9bac80 win32k win32k.sys Thu Aug 29 17:14:13 2002 (3D6DE5E5) <-- 2 years behind
f8bf5000 f8bf5740 BCMNTIO BCMNTIO.SYS Sat Jun 20 08:25:06 1998 (358B0162)
f8bfd000 f8bfdc00 audstub audstub.sys Sat Aug 18 04:59:40 2001 (3B7D85BC)
f8c18000 f8c188a0 MAPMEM MAPMEM.SYS Sat May 09 05:25:04 1998 (35537830)
f8c19000 f8c19fc0 HSMPORT HSMPORT.SYS Tue Jun 03 03:35:25 1997 (3393207D)
2. It is worthwhile to stress test your hardware and make sure it has no hardware problem such as faulty ram, faculty cache memory at CPU and meory, bad PSU (power supply unit).
Download Prime 95 to stress test your hardware http://www.mersenne.org/freesoft.htm
Hope it can help you.
cpc2004
Maybe it is overheat problem. Can you open the case for three to four hours. If windows does not crash, overheat is the culprit.
You have upgrade nVidia Display to the latest version which is an unstable version. Install nVidia Display Card Driver Version: 61.77 Release Date: July 27, 2004 and this is more stable version.
http://www.nvidia.com/object/winxp_2k_61.77.html
http://www.nvidia.com/object/winxp_2k_61.77.html
ASKER
someone upgraded to sp2 should i uninstall this then add the patches to sp1?
I ran a cpu check and got an mmx error but dont know what this means - also got a shop to change my motherboard a few weeks ago and they said the cpu had been scratched, should i replace the cpu?
I ran a cpu check and got an mmx error but dont know what this means - also got a shop to change my motherboard a few weeks ago and they said the cpu had been scratched, should i replace the cpu?
ASKER
ran prime 95 results as follows - but dont understand what the error means?
[Sat Dec 11 11:48:12 2004]
FATAL ERROR: Rounding was 0.4999866486, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Sat Dec 11 11:54:23 2004]
FATAL ERROR: Rounding was 0.4999732971, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Compare your results to other computers at http://www.mersenne.org/bench.htm
That web page also contains instructions on how your results can be included.
AMD Athlon(tm) XP 2600+
CPU speed: 1931.81 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX, SSE
L1 cache size: 64 KB
L2 cache size: 512 KB
L1 cache line size: 64 bytes
L2 cache line size: 64 bytes
L1 TLBS: 32
L2 TLBS: 256
Prime95 version 23.8, RdtscTiming=1
Best time for 384K FFT length: 34.869 ms.
Best time for 448K FFT length: 40.827 ms.
Best time for 512K FFT length: 43.129 ms.
Best time for 640K FFT length: 56.763 ms.
Best time for 768K FFT length: 67.576 ms.
Best time for 896K FFT length: 81.011 ms.
Best time for 1024K FFT length: 90.365 ms.
Best time for 1280K FFT length: 123.475 ms.
Best time for 1536K FFT length: 142.431 ms.
Best time for 1792K FFT length: 178.047 ms.
Best time for 2048K FFT length: 192.243 ms.
[Sat Dec 11 11:48:12 2004]
FATAL ERROR: Rounding was 0.4999866486, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Sat Dec 11 11:54:23 2004]
FATAL ERROR: Rounding was 0.4999732971, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Compare your results to other computers at http://www.mersenne.org/bench.htm
That web page also contains instructions on how your results can be included.
AMD Athlon(tm) XP 2600+
CPU speed: 1931.81 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX, SSE
L1 cache size: 64 KB
L2 cache size: 512 KB
L1 cache line size: 64 bytes
L2 cache line size: 64 bytes
L1 TLBS: 32
L2 TLBS: 256
Prime95 version 23.8, RdtscTiming=1
Best time for 384K FFT length: 34.869 ms.
Best time for 448K FFT length: 40.827 ms.
Best time for 512K FFT length: 43.129 ms.
Best time for 640K FFT length: 56.763 ms.
Best time for 768K FFT length: 67.576 ms.
Best time for 896K FFT length: 81.011 ms.
Best time for 1024K FFT length: 90.365 ms.
Best time for 1280K FFT length: 123.475 ms.
Best time for 1536K FFT length: 142.431 ms.
Best time for 1792K FFT length: 178.047 ms.
Best time for 2048K FFT length: 192.243 ms.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
did not belive shop owner thought he was trying to get out of the fact he had sold me a damaged motherboard. Does the prime95 error back up faulty cpu?
Prime95's torture test is an excellent cpu/memory test. the torture test performs intense math, and verifies the answers yielded with an existing 100% correct file. if there is a problem, the program halts and lets you know. stability isn't always an on or off thing - there are instances where your cpu virtually 'forgets to carry the 1.' for hyperthreading cpus, you can start 2 instances of prime95 using the -a0 and -a1 parameters when opening the app.
PC does not have good diagnostic tools to diagostic hardware problem. My computer background is st IBM MainFrame and Unix. Unlike OS/390, Sun Solaris and AIX, I never have to worry hardware problem as they are well look after by the hardware engineers. Main frame and Mid-Range computer has good diagnostic tools to diagnostic the hardware.
Resolve hardware problem is much easier than software problem. The hardware guy can swap CPU, MB, RAM or PSU and find out the failing component. I suggest you to setup a pointer question at EE hardware forum to ask the hardware experts to help you to resolve this problem.
For software problem, it is much harder. First you have to diagnostic which software driver is the culprit. Only few people have the skill to perform problem determination. Second apply the solution. For example, you know nVidia Display card driver is in trouble, upgrade the nVidia Display Card Driver may not fix the problem because even the latest Display card driver may have software error. I always have the problem, I know the culprit but I have no solution. Nowadays, manpower cost is more expansive than hardware cost.
Resolve hardware problem is much easier than software problem. The hardware guy can swap CPU, MB, RAM or PSU and find out the failing component. I suggest you to setup a pointer question at EE hardware forum to ask the hardware experts to help you to resolve this problem.
For software problem, it is much harder. First you have to diagnostic which software driver is the culprit. Only few people have the skill to perform problem determination. Second apply the solution. For example, you know nVidia Display card driver is in trouble, upgrade the nVidia Display Card Driver may not fix the problem because even the latest Display card driver may have software error. I always have the problem, I know the culprit but I have no solution. Nowadays, manpower cost is more expansive than hardware cost.
ASKER
0X00000004
0X00000002
0X00000000
0X804EFB93
HELP PLEASE