Well once again my new comp decides to kill it self over night, 1 day its fine the next it isn't, here's the problem.
I go to boot up normally, everything seems fine. But this new screen started to appear a couple of times, it was a blue screen (not BSOD) that had a "please wait......................." with several "dots" going across the screen (like a loading screen), now this only started to happen when I had to emergency restart (little black button) to exit a game i was playing. This got me worried that the ram could be buggered so I did a few fiddles here and there and it seemed fine.
OK well i went through a few days of this, got new AV software, did tedious deep scans and disk checks and defrags etc, thought nothing of it, but still thought the memory mite of been ballsed a bit. So that day i was too tired so i turned off.
Only to boot up the next day, go through same process, WinXP logo scroll bar (seems to hang on "fade in" 1 or 2 times...this is when i knew there was a problem) went through the "please wait........." screen again, only this took twice as long...and of course this is when I get the BSOD
. Its so useless it tells you nothing of what caused it, the only info it gave me was this exact message:
*** STOP : 0x0000007F (0x000000D, 0X00000000, 0x00000000, 0x00000000)
And that was it. Now for a list of what Ive tried:
- All of the options on the "F8" menu, right the way down from "safe mode" all the way down the list to "start normally"
- Tried taking one peace of my ram out, swapping them over in case for mem errors etc/vice versa, no dice
- Tried using my HD's on another comp to get a disk check going on...this comp currently wont recognise either HD for some reason no matter how i plug it in
- According to the bios and the "windows directory controller" boot options...both my "D: AND C:" volumes of my data are perfectly fine :S but I still get BSOD (oh yeah and my HD IS recognised in the bios BTW)
- I've tried booting using per sector boot instead of multi sector boot to check and see if I had severe sector issues, no luck
So as you can see Ive tried pretty much everything, my mate has said that it could be something to do with a corrupt system file, system32 file or something to do with the SP3 windows update. He said the only way could be for re-install of windows and possible format. Hell I could of already lost all the data on the HD from this error :S.
My K:\ drive I KNOW is perfectly fine and says so it self...but this dam computer wont pick up any of my HD's, maybe coz my HD's use SATA connections and this comp doesn't use that.
Well I'm all out of options, and of course you guessed it, I don't have any of the original boot disks or XP discs at all.
So what you guys reckon, do you recognise the error in the BSOD? Is it a simple "find a compatible comp and get the HD sorted out/disk checked etc"? Or has it completely failed on me?
I just don't get PCs, one day there fine the next...boom BSOD.
Any help would be great thanks
Oh and PS...I'm almost perfectly sure ITS NOT and kind of virus or bug or w/e, did endless scans.
I go to boot up normally, everything seems fine. But this new screen started to appear a couple of times, it was a blue screen (not BSOD) that had a "please wait......................." with several "dots" going across the screen (like a loading screen), now this only started to happen when I had to emergency restart (little black button) to exit a game i was playing. This got me worried that the ram could be buggered so I did a few fiddles here and there and it seemed fine.
OK well i went through a few days of this, got new AV software, did tedious deep scans and disk checks and defrags etc, thought nothing of it, but still thought the memory mite of been ballsed a bit. So that day i was too tired so i turned off.
Only to boot up the next day, go through same process, WinXP logo scroll bar (seems to hang on "fade in" 1 or 2 times...this is when i knew there was a problem) went through the "please wait........." screen again, only this took twice as long...and of course this is when I get the BSOD
. Its so useless it tells you nothing of what caused it, the only info it gave me was this exact message:*** STOP : 0x0000007F (0x000000D, 0X00000000, 0x00000000, 0x00000000)
And that was it
. Now for a list of what Ive tried:- All of the options on the "F8" menu, right the way down from "safe mode" all the way down the list to "start normally"
- Tried taking one peace of my ram out, swapping them over in case for mem errors etc/vice versa, no dice
- Tried using my HD's on another comp to get a disk check going on...this comp currently wont recognise either HD for some reason no matter how i plug it in
- According to the bios and the "windows directory controller" boot options...both my "D: AND C:" volumes of my data are perfectly fine :S but I still get BSOD (oh yeah and my HD IS recognised in the bios BTW)
- I've tried booting using per sector boot instead of multi sector boot to check and see if I had severe sector issues, no luck
So as you can see Ive tried pretty much everything, my mate has said that it could be something to do with a corrupt system file, system32 file or something to do with the SP3 windows update. He said the only way could be for re-install of windows
and possible format. Hell I could of already lost all the data on the HD from this error :S.My K:\ drive I KNOW is perfectly fine and says so it self...but this dam computer wont pick up any of my HD's, maybe coz my HD's use SATA connections and this comp doesn't use that.
Well I'm all out of options, and of course you guessed it, I don't have any of the original boot disks or XP discs at all.
So what you guys reckon, do you recognise the error in the BSOD? Is it a simple "find a compatible comp and get the HD sorted out/disk checked etc"? Or has it completely failed on me?
I just don't get PCs, one day there fine the next...boom BSOD
.Any help would be great thanks
Oh and PS...I'm almost perfectly sure ITS NOT and kind of virus or bug or w/e, did endless scans.
