Outline · [ Standard ] · Linear+ Windows XP BSOD

after all, OS is software.. but anyways. does this happen with your system ?
1. burn something with Nero
2. leave it to "burning finished" (or whatever there reads when its done) state
3. let your computer crash.

on step 3 I didnt use the comp at all, I'm not sure if it has to be that way. time it took was more than 3 hours according to my irc-logs but.. would be of great help if I could say to MS that it happens on other ppl's comp and maybe we could get them to fix it :) and, this would tell me if its just my system :( (as for me, it happened also when I had burned with Alcohol 120%)
also, one thing - I havent been able to get my system to make up a memory dumb. not in any size. the ppl at MS requested full memory dumb. it this happens and you manage to get that dumb file, let me know :)

Do you get an actual blue screen of death or does it just turn it self off? If you do get a blue screen, what's the error message on it???

I didn't think that BSODs even existed in XP. I haven't recieved one since the Windows 98 days (I think I got one in Windows 2000 Server also... but I did that intentionally to prove that it was crashable). I actually think I've done what you've done and went out while something was burning. I'm pretty sure it would've been sitting there for 2 hours and I came back to it in working order. Maybe a bad version of Nero?

This post has been edited by TWINE006: May 29 2004, 04:09 PM

I think u might be on the right track Twine006. I remember reading something somewhere about Nero crashing XP.

Off the top of my head BSOD's are most often related to programs trying to access memory that they're not allowed to. Since you're experiencing the same problem with Alcohol 120% it could be that you've got a corrupted driver or something somewhere.

Anyways, you're probably best off looking at the Nero 6 Error Messages FAQ

In particular check:
1. I get an illegal operation while running Nero. What should I do?

9. I get an error while copying a CD without generating a log file. What can I do?

Let me know if this is helpful.

Cheers!

Windows XP gets BSOD's like all other versions of Windows. The only difference is that the default settings for XP makes it reboot automatically when it crashes. Makes it nigh impossible to get an actual error message. You can turn that off though.
I use Nero all the time. No problems.
You might want to uninstall all your cd-writers, and see if you can get an update for your ASPI layer. Then reinstall your programs. That might fix it.

Sounds like your ASPI layer - most likely Nero's ASPI drivers overwrote M$ drivers. And if that's the case, Alcohol 120% would also use the Nero ASPI drivers - thus both programs crash. Uninstall all your burning programs and after a re-boot try burning something using XP's built-in burner. If all is okay, I'd upgrade Nero to the latest build and reinstall.

well.. this had crashed, with BSOD.. I had burned something and then closed nero and almost everything, just left mirc & servers online. as well as MSN and so on but nothing that wouldnt always be on. the error messages are like these:

kernel_data_inpage_error
stop 0x0..07a (0x0c03dd610,0xc000009d,0xf7584d2d,0x2e122860)
in classpnp.sys: address f7584d2d base f757e000 stamp 3b7dc5af

kernel_data_inpage_error
stop 0x0000007a (0xc03ddb8c, 0xc000009d, 0xf76e36f2, 0x10c1c860)
in disk.sys: address f76e36f2 base f76de000 stamp 405178e2

so it sounds like it could be that there are nero's aspi-layer drivers or something installed. and the funny thing is, that I had the reboot selected but it didnt occur after these crashes.. I'm sure it wouldnt help too much to post more of these crashes but I could do that if u want, still have some reported to MS @ windowsbeta. neither Nero nor Alcohol gave any error messages.. the computer was just on BSOD. before it has done it on a regular intervals, at the worsest point it didnt take half an hour it to crash (at which point I went to reinstall and scan my hard-drives). any ideas if this could be caused by SATA-Raid ? just thinking cuz this also managed to do a BSOD while doing scandisk to that raid-station...

0x000007 Unknown Hard Error
Unknown Hard Error

I'm not yet ready to do the removal & reboot thing yet, thought.. lets see if this doesnt crash when not using the burning software's :)

edit: well since it crashed on its own without me burning I'm just going to try if updating those ASPI-drivers will help anything. found aspi_471a2.exe from the adaptec, hopefully it will help. at least its more up-to-date than any of the files... and btw this is what running adaptecs ASPICHK resulted in:

This post has been edited by Deepone: May 31 2004, 07:09 PM

this is its output now:

in other words, wowpost.exe and winaspi.dll remained to be at version 4.6 while the other two files were the only ones updated (to 4.712). is this the same for others, ie do you have those two other files at previous version or ?

oh well.. comp crashed while I watched anime, and then it crashed in about ten minuts after that. with the last thing me noticing an msg to be coming to MSN...
trying to see if this has anything to do with dc++. if someone has versions 4.712 of those two files that didnt seem to be updated for me, let me know. update didnt seem to help..

Check your RAM. 9 times out of 10 bad ram is the problem with the BSOD errors.

I was leaning towards hardware myself. When my harddrive started going bad, the comp would always blue screen while using Nero at the spot you mention. Most burning progs did it at that spot. And as my HD got worse, the random crashes started happening even with the puter at idle.

My guess would be hard drive .. Run a full blown chkdsk .. If it finds an error .. then run it multiple times .. If you see additional errors in subsequent runs .. then you know that it's the HD .. This just happened to me .. Started with one BSOD and disk i/o slowed to a crawled

What do you call 'bad RAM'? I added a 256 stick to my machine, and i have no probs under win2k, however in xp (it's a dual boot) sometimes i get the bsod. I atribute it to the soundcard drivers, since it's an old system. Anyway, I always thought RAM sticks never failed (unlike HD's).

well.. the funny thing is - it was working just fine before. and when this thing started to happen last time, I ran full tests for my HD's (since they were new anyway). took ages, but nothing was found. I've planned to run Memtest for the next night just to see if it would reveal anything new.
I'm also quite sure that if I just reinstall XP the problem will be gone.. like it was last time.. then after time has passed (I think it was more than month from the last time, dont remember the exact dates anyway) it now has started to reappear. apart from RAM & HD, other suggestions ? could the MB or ram-sticks heat too much and start to make errors ? asus probe reports the mobo is around 40degrees.. but these crashes are maybe a bit too random for it to be reason, othervice it would happen pretty usually around the same times if its idling or so, or ?

RAM Dies. Sad fact. But it does. There's some decent testers around, most need to run in DOS mode from a boot disk.

I woud hazzard a guess towards hardware errors to get BSOD's from Windows XP. Most of the time, software errors cause XP to recover without BSOD's and without having to reboot. Hence, M$ call it more stable. Pah.

In WinXP I've had BSOD's from:
RAM
HDD's
CPU's
PSU's
Video Cards
and once from a sound card.

there's a fairly decent RAM tester at www.simmtester.com that i have used often.