Win XP restarts after shutdown

[chim666]

I am running Windows XP Pro SP2 and am having problems in that the machine keeps restarting after shutdown.
After it restarts, I get the Microsoft message stating 'a serious error has occured', inviting me to send/no send the error report.

It all started after my son downloaded itunes for his new iPod Nano ealrier this week.

I reverted back a few days using System Restore, (i.e. to the config before itunes was installed) and it shutdown ok.
I then downloaded itunes again and it shutdown ok the first time.
But when I restarted the PC and then shutdown once more, the problem re-occurred.

I have cleared out the registry with RegMechanic (or something like that), and have run CCleaner to clear out temp files, but no joy.

I disabled 'Restart after System Failure' in 'My Computer' and although it did not restart after shutdown, I got a memory dump message displayed.
So it appears that I'm actually getting a system failure when I do a shutdown which is resulting in an automatic restart, followed by the M.Soft serious error recovery message.

I do have some other media-typs things on the machine (CDex, Nero, Creative ZEN, Sony ATRAC and INCD - but these were all running ok before itunes came along!)

My question is; what can I do to get itunes to run happily within Win XP? - all suggestions gratefully received!

[sneakyneil]

Good work so far! A good next move is - the blue dump screen often refers to a particular file in the text near the top. Find out what program or driver that file relates to, and download the most up to date version of the package thats available. You can find out what it relates to either by the name being obvious, the folder that the file is in on the hard disk, or the information revealed by checking the properties of the file. As a last resort you could try opening it in wordpad and checking for identifiable text amongst the gobbledygook.

HTH

[chim666]

Thanks Neil...I'll give it a go.

Paul

[ThePassenger]

When it did the BSoD / Memory Dump what did it say near the top? Any way you could just it down? Maybe something like IRQ_NOT_LESS_EQUAL_TOO driver: nv4_disp.dll

[chim666]

It wasn't the 'real' BSoD, but it seemed to be just a basic error report, telling me that if it wasn't the first time it had happened, I should contact my administrator etc,.
There was also the following string of info at the bottom:
STOP: 0xC000008E, (0xC0000005, 0x8062A21D, 0xF790DA50, 0x00000000)

Once I rebooted, I then get the MSoft serious error window, and the following error data....

BCCode : 1000008e BCP1 : C0000005 BCP2 : 8062A21D BCP3 : F790DA50
BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

then after clicking on 'view tech info on the report' I got:

C:DOCUME~1DefaultLOCALS~1TempWER8f73.dir00Mini121606-06.dmp
C:DOCUME~1DefaultLOCALS~1TempWER8f73.dir00sysdata.xml

[ThePassenger]

Try this:

boot up in safe mode
delete the folder "WER1.tmp.dir00" of all the user on your computer
delete all in c:windows minidump
go to the DOS prompt and write "chkdsk /f" it will probably ask for doing the scan on the next bootup, select "yes"
then reboot

[chim666]

ThePassenger said:

Try this:

delete the folder "WER1.tmp.dir00" of all the user on your computer

I don't mean to question your advice Sarah (I'm very grateful...really I am! ), but is the folder "WER1.tmp.dir00" a temp folder that is created by Windows? (I'm always a bit cautious about deleting system folders!)

[ThePassenger]

chim666 said:

ThePassenger said:

Try this:

delete the folder "WER1.tmp.dir00" of all the user on your computer

I don't mean to question your advice Sarah (I'm very grateful...really I am! ), but is the folder "WER1.tmp.dir00" a temp folder that is created by Windows? (I'm always a bit cautious about deleting system folders!)

Hehe, no worries. It has all the hallmarks as a temp folder made either by a program or Windows itself (it looks machine named, has tmp in it, sequential numbering, etc). If you want, instead of deleting it/them on the first run move them all somewhere safe. If everything goes to plan you can kill them and if not, you can, if you wish copy them back

ETA: Ohh bum. Aim for "WER8f73.dir00" instead of "WER1.tmp.dir00", fat fingers and cut n' paste have gone awry.

Edited by ThePassenger on Saturday 16th December 12:56

[chim666]

ThePassenger said:

...Ohh bum. Aim for "WER8f73.dir00" instead of "WER1.tmp.dir00", fat fingers and cut n' paste have gone awry.

Sorry for the delay in replying....work called!
Thanks for the correction - that explains why search couldn't find the file!

[chim666]

Hmm - booted in safe mode but still can't find these two files.
I've also run chkdsk /f

I've searched the C drive with *WER8f73.dir*.* as the search string, but nothing was found

I've also looked around 'Documents and Settings/Default User/Local Settings' but still cannot see anything resembling these files in any folders.

But looking once more at the message, they seem to be just error reports which XP wants to send off, so will there be any benefit by deleting them?

Edited by chim666 on Saturday 16th December 14:37

[ThePassenger]

chim666 said:

Hmm - booted in safe mode but still can't find these two files.
I've also run chkdsk /f

I've searched the C drive with *WER8f73.dir*.* as the search string, but nothing was found

I've also looked around 'Documents and Settings/Default User/Local Settings' but still cannot see anything resembling these files in any folders.

But looking once more at the message, they seem to be just error reports which XP wants to send off, so will there be any benefit by deleting them?

Edited by chim666 on Saturday 16th December 14:37

I'm playing a hunch that something in the error reporting system might be causing the problem; it's odd that it only happens when iTunes is around... i hate to say it this way, but if your copy of Windows is legit try getting it to send the error reports.

[chim666]

No probs...I'll try and see what happens.

Thanks Sarah.

[chim666]

Update...
I 'sent' the error report off, and immediately received a response and link to Nero's site. Apparently it's a known problem with IN_CD ver4 (Nero 6).
So I updated to the latest ver 4, but during the instal it complained about Roxio's UDF reader, and provided a further link to disable it (which I did). It then said that a reboot would be required for it to take effect, and offered a 'yes/no' button to the reboot.
So one reboot later, and still the same error message, and the same link to Nero etc,. Twice more I carried out the Nero upgrade, before I wondered whether the reboot immediately after disabling UDF was actually resetting it again. So I said 'no' to the reboot, checked the IN_CD version - latest version installed. !
Then, I did a reboot - and Robert's your mother's brother! No more restarts after shutdown.

[sneakyneil]

Yaaaay! Nice one. Thepassenger prevails again!

[thepassenger]

sneakyneil said:

Yaaaay! Nice one. Thepassenger prevails again!

Nahh, that one was just guess work. Who'd have thunk it that InCD would be the cause... but if you want to buy me a beer... feel free

Nice to know it's sorted.

[chim666]

thepassenger said:

sneakyneil said:

Yaaaay! Nice one. Thepassenger prevails again!

Nahh, that one was just guess work. Who'd have thunk it that InCD would be the cause....

Yeah, particularly as nothing (apparently) had been changed in that department - only installing iTunes!

Thanks again Sarah - and collar me for that beer if ever you spot me around!