nForums.net -> Windows XP BSOD

Windows XP BSOD

Track this topic | Email this topic | Print this topic

Deepone	May 29 2004, 09:18 AM Post #1
The One Deep Down Group: Private Member Posts: 1137 Joined: 12-May 04 From: Masala / Kirkkonummi / Finland Member No.: 101	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 :) -------------------- This person is best talked to with the help of a computer..

Replies

Deepone	Jun 14 2004, 10:35 AM Post #2
The One Deep Down Group: Private Member Posts: 1137 Joined: 12-May 04 From: Masala / Kirkkonummi / Finland Member No.: 101	apparently I seem to have solved this one. there are actually three possible solutions, I'm not sure which one really did the trick. one of them should be okay to be eliminated tho.. since its been working with that way before :) 1) removing of smaller RAM-stick 2) defragment (this is what I actually guess) 3) reducing multiple IP's on the same card to a single one. number 3 is unlikely since its been working with that way before too. and, it didnt start to crash immediatly after I put them :) and number one isnt so likely because memtest reports the same errors with the other stick anyway. and, again, comp didnt start to crash immediatly after I reinstalled windows.. which, in turn, lets my to think that somehow the windows started to crash because something got corrupted/fragmented a bit too much or something. this makes sence in a way, since last time reinstallations of windows actually helped - which would most likely have more compact files. and with time, it started to fragment.. and MFT getting maybe too big and getting fragmented too, which might be something that then caused the crashings. now, I'm interested to find out.. does this make sense to you ? :) -------------------- This person is best talked to with the help of a computer..

Posts in this topic

Deepone Windows XP BSOD May 29 2004, 09:18 AM

Voidrunner Do you get an actual blue screen of death or does ... May 29 2004, 01:25 PM

TWINE006 I didn't think that BSODs even existed in XP. ... May 29 2004, 04:08 PM

mcelb1200 I think u might be on the right track Twine006. I ... May 30 2004, 04:42 AM

Voidrunner Windows XP gets BSOD's like all other versions... May 30 2004, 04:48 PM

Audiyoda Sounds like your ASPI layer - most likely Nero... May 30 2004, 07:38 PM

Deepone well.. this had crashed, with BSOD.. I had burned ... May 30 2004, 08:23 PM

Deepone this is its output now: in other words, wowpost.e... May 31 2004, 07:29 PM

Deepone oh well.. comp crashed while I watched anime, and ... May 31 2004, 10:30 PM

amc Check your RAM. 9 times out of 10 bad ram is the p... Jun 1 2004, 07:41 PM

Radnoken I was leaning towards hardware myself. When my ha... Jun 1 2004, 07:47 PM

forbin My guess would be hard drive .. Run a full blown c... Jun 1 2004, 10:05 PM

PimpScourge What do you call 'bad RAM'? I added a 256... Jun 2 2004, 03:49 PM

Deepone well.. the funny thing is - it was working just fi... Jun 2 2004, 08:35 PM

Xizor RAM Dies. Sad fact. But it does. There's some ... Jun 14 2004, 05:40 AM

Deepone apparently I seem to have solved this one. there a... Jun 14 2004, 10:35 AM

1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)

0 Members: