I've had it with Windows XP Pro!

[scornduffer]

:mad: :confused: :eh?: I cannot for the life of me get windows xp pro to run without rebooting and restarting because of some mini dump or so called hardware conflict.

I try to play games or browse the web and it just quits and restarts. I thought it wa my power supply so I upgraded to a Sparkle 350watt with combined power output of 22o watt.

I went to Microsoft's worthless compatibility upgrade and downloaded all the upgrades. Windows xp pro claims that there is no conflicting devices and yet the error report claims that there is a device problem or a software problem.

I also loaded the latest bios from soyo's website and flashed it. I am running NTS instead of fat 32.

I have a Soyo Dragon Plus Motherboard with and Athlon 1800 xp, 512 DDR memory 2400 speed, 60 gig hard drive, cdrw, dvd, gforce 3 ti 200 64 meg video card.

Can anyone help me before I reinstall windows 98se(fresh)?

[madsam]

go to...start menu
settings...
control panel...
system...
advanced tab...
startup and recovery...
..settings
...unclick the box for the option that says automatically restart, under the system failure section on the bottom

it's just a setting....don't have a break down now.....although, i must admit, it did the same thing to me , and i was ready to trash xp pro.....xp home did it too....lol

good luck, and i hope this is the fix you need

;)

[redduc900]

Windows xp pro claims that there is no conflicting devices and yet the error report claims that there is a device problem or a software problemIf you could copy down the error report/log Exactly as it appears, and then post it into this thread (only any critical errors)...that would help us immensely in trying to determine where the problem lies.

As you probably know (since it sounds like you've already accessed the error logs), you can get to the logs by going to Start | All Programs | Administrative Tools (or Start | Administrative Tools) | Event Viewer. When Event Viewer opens up, you'll notice two panes...in the LH pane highlight "Application" and then "System" (these are the Windows error logs). Look for any RED colored errors/X's in the RH pane (these are critical errors), and if any are found...right click each error and select "Properties". Under the "Description:" field will be a short description of the error, including an error code.

...then like I suggested, please copy the error(s) descriptions and codes Exactly as they're displayed and post them in this thread. ;)

[scornduffer]

I will posts these arrows tonight when I get off work.

Thanks

Steve:)

[el]

try to repair/reinstall this will keep your settings and should fix the problem.

Start WindowsXP

Go to the location of your source files

Run WINNT32 /unattend

[Vfrjim1]

I've had similar errors for the last 3 months, ended up being a bad memory problem, try a "known" good stick from another computer, it solved my problem. GL

Jim

[scornduffer]

Originally posted by redduc900
If you could copy down the error report/log Exactly as it appears, and then post it into this thread (only any critical errors)...that would help us immensely in trying to determine where the problem lies.

As you probably know (since it sounds like you've already accessed the error logs), you can get to the logs by going to Start | All Programs | Administrative Tools (or Start | Administrative Tools) | Event Viewer. When Event Viewer opens up, you'll notice two panes...in the LH pane highlight "Application" and then "System" (these are the Windows error logs). Look for any RED colored errors/X's in the RH pane (these are critical errors), and if any are found...right click each error and select "Properties". Under the "Description:" field will be a short description of the error, including an error code.

...then like I suggested, please copy the error(s) descriptions and codes Exactly as they're displayed and post them in this thread. ;)

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 8/5/2002
Time: 7:52:12 PM
User: N/A
Computer: HOME-679R97DURK
Description:
Error code 000000d1, parameter1 00000001, parameter2 00000002, parameter3 00000000, parameter4 00000001.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 64 000000d
0020: 31 20 20 50 61 72 61 6d 1 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 31 2c 20 000001,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 30 30 30 30 00, 0000
0050: 30 30 30 31 0001

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 8/5/2002
Time: 5:15:31 PM
User: N/A
Computer: HOME-679R97DURK
Description:
Error code 0000000a, parameter1 00000000, parameter2 00000002, parameter3 00000001, parameter4 804f608a.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 30 0000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 30 2c 20 000000,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 31 2c 20 38 30 34 66 01, 804f
0050: 36 30 38 61 608a


Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 8/4/2002
Time: 8:43:48 PM
User: N/A
Computer: HOME-679R97DURK
Description:
Error code 1000008e, parameter1 c0000005, parameter2 bf876bed, parameter3 f21f27d0, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 62 66 38 37 36 62 65 64 bf876bed
0040: 2c 20 66 32 31 66 32 37 , f21f27
0048: 64 30 2c 20 30 30 30 30 d0, 0000
0050: 30 30 30 30 0000
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 8/4/2002
Time: 4:32:33 PM
User: N/A
Computer: HOME-679R97DURK
Description:
Error code 1000008e, parameter1 c000001d, parameter2 804f5502, parameter3 f8951e54, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 31 64 2c 20 00001d,
0038: 38 30 34 66 35 35 30 32 804f5502
0040: 2c 20 66 38 39 35 31 65 , f8951e
0048: 35 34 2c 20 30 30 30 30 54, 0000
0050: 30 30 30 30 0000
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 8/4/2002
Time: 4:13:51 PM
User: N/A
Computer: HOME-679R97DURK
Description:
Error code 000000e3, parameter1 81f8ffc8, parameter2 81c00540, parameter3 00000000, parameter4 00000002.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 65 000000e
0020: 33 20 20 50 61 72 61 6d 3 Param
0028: 65 74 65 72 73 20 38 31 eters 81
0030: 66 38 66 66 63 38 2c 20 f8ffc8,
0038: 38 31 63 30 30 35 34 30 81c00540
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 30 30 30 30 00, 0000
0050: 30 30 30 32 0002

Event Type: Error
Event Source: Cdrom
Event Category: None
Event ID: 7
Date: 8/4/2002
Time: 3:01:48 PM
User: N/A
Computer: HOME-679R97DURK
Description:
The device, \Device\CdRom0, has a bad block.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 03 00 68 00 01 00 b8 00 ..h...¸.
0008: 00 00 00 00 07 00 04 c0 .......À
0010: 00 01 00 00 9c 00 00 c0 ....œ..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 50 d5 24 00 00 00 00 .PÕ$....
0028: a2 21 08 00 00 00 00 00 ¢!......
0030: ff ff ff ff 01 00 00 00 ÿÿÿÿ....
0038: 40 00 00 c4 02 00 00 00 @..Ä....
0040: 00 20 0a 12 48 02 00 40 . ..H..@
0048: 00 00 00 00 0a 00 00 00 ........
0050: 00 30 51 02 30 9d e3 81 .0Q.0�ã�
0058: 00 00 00 00 70 fe e7 81 ....pþç�
0060: 02 00 00 00 aa 9a 04 00 ....ªš..
0068: 28 00 00 04 9a aa 00 00 (...šª..
0070: 02 00 00 00 00 00 00 00 ........
0078: f0 00 03 00 04 9a aa 0a ð....šª.
0080: 00 00 00 00 11 06 00 00 ........
0088: 00 00 00 00 00 00 00 00 ........

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7011
Date: 8/4/2002
Time: 2:36:08 PM
User: N/A
Computer: HOME-679R97DURK
Description:
Timeout (30000 milliseconds) waiting for a transaction response from the Netman service.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 8/3/2002
Time: 10:45:57 AM
User: N/A
Computer: HOME-679R97DURK
Description:
Error code 1000008e, parameter1 c0000005, parameter2 8051e89f, parameter3 f2ab6c5c, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 38 30 35 31 65 38 39 66 8051e89f
0040: 2c 20 66 32 61 62 36 63 , f2ab6c
0048: 35 63 2c 20 30 30 30 30 5c, 0000
0050: 30 30 30 30 0000

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 8/1/2002
Time: 6:21:57 PM
User: N/A
Computer: HOME-679R97DURK
Description:
Error code 1000008e, parameter1 c0000005, parameter2 8057e102, parameter3 f265abb4, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 38 30 35 37 65 31 30 32 8057e102
0040: 2c 20 66 32 36 35 61 62 , f265ab
0048: 62 34 2c 20 30 30 30 30 b4, 0000
0050: 30 30 30 30 0000

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 7/25/2002
Time: 8:48:14 PM
User: N/A
Computer: HOME-679R97DURK
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc000001d, 0x03ffdff1, 0x804d5636, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini072502-01.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 7/22/2002
Time: 7:26:15 PM
User: N/A
Computer: HOME-679R97DURK
Description:
Error code 000000d1, parameter1 487cc010, parameter2 00000002, parameter3 00000000, parameter4 487cc010.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E

0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 64 000000d
0020: 31 20 20 50 61 72 61 6d 1 Param
0028: 65 74 65 72 73 20 34 38 eters 48
0030: 37 63 63 30 31 30 2c 20 7cc010,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 34 38 37 63 00, 487c
0050: 63 30 31 30 c010

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4311
Date: 7/22/2002
Time: 10:00:30 AM
User: N/A
Computer: HOME-679R97DURK
Description:
Initialization failed because the driver device could not be created.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 01 00 58 00 ......X.
0008: 00 00 00 00 d7 10 00 c0 ....×..À
0010: 11 01 00 00 01 00 00 c0 .......À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

These are some of the errors I've been getting. I didn't know if you wanted all the info or not. Some I didn't copy because the were the same.

Could it be faulty memory even though the computer works when Im not playing games.

Steve

[Vfrjim1]

one of your errors comes close to mine:

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbf9df7dc, 0xf4e4dbe4, 0x00000000). A dump was saved in: F:\WINDOWS\Minidump\Mini051402-01.dmp.

BTW, looking back at my .dmp files, I see they are listed by date from 021002 through 071802. Seems like it started when I bought new memory :( just didn't realize it.


Jim

[macklin01]

It's quite possible that a game woudl turn up a memory error that normal usage wouldn't. You might not need enough memory to access the bad portion of the stick until high-demand usage, such as a game. Also, a game might have a particular data pattern than the (faulty) stick can't process properly.

I'd recommend a RAM stress check. A great utility is called memtest86. (Look at http://www.memtest86.com .) I use this to test memory stability whenever I try a new setting. (So far, I've tested my memory at 2-2-2 at 137MHz FSB.) It's a pretty picky test, so if there are any memory problems, it'll almost certainly find them.

It runs independently of the OS, so if an error turns up, it can only be in the bus/northbridge, CPU, or most likely, memory. (Loads from a floppy to about the first 76K of memory.)

Good luck! -- Paul

[FDUSMC]

Did you ever figure out the problem scornduffer? I have the same exact problem with XP Pro which I haven't been able to figure out. I've tried everything! Win98SE works perfect tough:confused: Let me know if you figure it out. Your the second person that I know who has posted a similar problem in this forum.

[scornduffer]

Originally posted by FDUSMC
Did you ever figure out the problem scornduffer? I have the same exact problem with XP Pro which I haven't been able to figure out. I've tried everything! Win98SE works perfect tough:confused: Let me know if you figure it out. Your the second person that I know who has posted a similar problem in this forum.

I haven't been able to run the memory test I just got back from out of town. I will check the memory and get on the computer via some games and see if I have the same problem.

If I do I'll try some new memory and if that doesn't work I'll go back to Windows 98SE.



:)

[macklin01]

Originally posted by scornduffer


I haven't been able to run the memory test I just got back from out of town. I will check the memory and get on the computer via some games and see if I have the same problem.

If I do I'll try some new memory and if that doesn't work I'll go back to Windows 98SE.:)
Thanks for the report back! If you do turn up some memory errors, you'll certainly want to repair the problem, no matter what OS you're in.

PS: Are you overclocking your FSB or running the memory at a higher than its rated CAS?

Thanks, and good luck! -- Paul

[FDUSMC]

Yeah, would definetly want to know what the deal is. I just went back to win98se because of it:(

[hkgonra]

I had the exact same problem but only with games after a while of fighting it I found it to be a bad memory stick as well . The really funky thing was that it only crashed with nvidia cards . I put my voodoo 5500 in it and it was rock stable. I guess the voodoo interacts with system memory different than nvidia cards.

[hkgonra]

Originally posted by macklin01

Thanks for the report back! If you do turn up some memory errors, you'll certainly want to repair the problem, no matter what OS you're in.

PS: Are you overclocking your FSB or running the memory at a higher than its rated CAS?

Thanks, and good luck! -- Paul

BTW, I ran several different memory tests none of them turned up any errors. However when I put known sticks of memory in it they worked fine . I ran several combos , I had two known good sticks and to unknowns . I twisted and changed the combo every way possible , then ran 3dmark2001 as the test . Whenever the bad stick was in the system it crashed . After a triple checked every combination I put the "bad" stick in and ran 3 different memory tests again with no errors. After that I don't have much faith in them.

I also put the bad stick in my stable system and it crashed it.

[macklin01]

wow, that's too bad! I'm really sorry to hear that, and would like to understand the circumstances.

Which utility were you using? If memtest86, did you run all the tests?

Thanks -- Paul

[hkgonra]

Originally posted by macklin01
wow, that's too bad! I'm really sorry to hear that, and would like to understand the circumstances.

Which utility were you using? If memtest86, did you run all the tests?

Thanks -- Paul

I honestly don't remember now what it was , it was in April.

I know I used sandra , and then I got two or three more that had high ratins at cnet download section .

[macklin01]

Originally posted by hkgonra


I honestly don't remember now what it was , it was in April.

I know I used sandra , and then I got two or three more that had high ratins at cnet download section .
Okay, that makes sense.

Well, so far, memtest86 has never let me down. You run it off a floppy in the first 76K of memory or so, so it's OS-independent. (And 4-in-1 driver independent, etc.) As it also implicitly tests the CPU and Northbridge, it's more likely to turn up a false positive than a false negative. For instance, it once turned up bad memory management on my old motherboard, which I eventually RMA'd. Now, with my current motherboard, I get 0 errors (and incidentally, 100% stability) with my current overclock, and a stick of PC150 I recently bougth off of ebay turned up massive errors in the test, as well as stability problems.

Now, I primarily use the test to see if my RAM timings will be stable before leaving the settings there.

Thanks for the report back!

Have a nice evening. -- Paul

[Conan]

I have the same restarting problem with winXP pro, and that happened after i got a gainward gf4 Ti 4200 which is a great card, i tried everything (formatting,updating drivers etc. i also got a new psu aswell),and was looking for long time in forums for a solution but still nothing....
The smile from my face has been wiped out :(
if u have any suggestions to help me, i will be very happy, if u don't, i think i'll just give up and will look like this ----> :( for the rest of my life

[scornduffer]

Conan, I had to go back to windows 98 se because of the same problem. I 'm not sure what the solution might be? But maybe you can try xp pro with fat 32 instead of NTFS. Have you tried xp pro with fat32?

[FDUSMC]

I have it still no fix.

[Conan]

Don't post again until you learn to clean up the language a bit. The filters are in place for a reason and it's not so that you can side-step them.

Jon
Forum Moderator

[daddyof2]

I also had mini dump errors which i figured to be memory. After trying three diff sticks and getting the same errors i almost gave up. I had the latest drivers for my vid card so i did not think that was it. But after downloading a new copy of the 2.2 catalyst drivers and instaling over the other copy my mini dumps errors quit.