Thanks to sawce, who helped me repair a missing/corrupted Windows file. It seemed to fix a lot of issues BUT - ceretain things like video and sound drivers needed to be reinstalled.
Piece of cake, eh? NOT! Creative ran a diagnostics test, and told me that to install the drivers I had to uninstall current software. I did so, and that was it - it would NOT load Windows at restart, in SafeMode, Last Configuration, Normally, at all. I did notice a brief BSOD, but couldn't read it. Windows just would not load.
I'm formatting this hd one more time (this is the third time in as many weeks, I think. I may have done quick formats before - this time am doing the fullblown one).
If this fails, I have a brand new <a href="http://www.buy.com/prod/western-digital-raptor-x-hard-drive-150gb-10000rpm-150mbps-serial-ata/q/loc/101/202442761.html#prodInfoSec" target="_blank">WD Raptor</a> in the box ($302.00 at buy.com who is cheaper than Newegg usually). I got it for $192.00 at BestBuy. <img src="style_emoticons/<#EMO_DIR#>/smile-fix.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile-fix.gif" />
<!--quoteo(post=1619094:date=Apr 5 2007, 11:54 AM:name=Kouji_San)--><div class='quotetop'>QUOTE(Kouji_San @ Apr 5 2007, 11:54 AM) [snapback]1619094[/snapback]</div><div class='quotemain'><!--quotec--> Well the real problem is you are asking for an analysis trough the internet. Yet it could be many things, which are not possible to test for trough the internet.
For instance:<ul><li>mem could be bad, and when the Os tries to write something into the memory which is corrupted it can reboot.
Then I'd advice <a href="http://www.memtest86.com/" target="_blank">http://www.memtest86.com/</a> </li><li>Or it could be hear related asAnarkiThreeXSix said, go download some hardware temp monitor programs (probably included with the motherboard/pc) </li><li>It could any number of hardware conflicts (mem vs cpu, cpu vs pci-controller, hdd vs mem and the list goes on)
are there any conflicts (start->programs->accessories->system tools->system information in here have a look at shares/conflicts or something) </li><li>software related, try booting into safemode (for vista, is it still f8 for bootmenu? [edit]--> ACK! you've gone done and put a switch of OS on me!!! XP FTW!!!)</li><li>virus and spyware can kill the OS and make it reboot (most likely a bootsector virus on a fesh format, if it is viral)</li><li>gremlins, I swear!</li></ul>Basically all of the above could help you in determining what could be the cause, then the mighty internet/google can help you resolve it with tutorials. Or someone on here with a similar problem which was solved <!--QuoteEnd--></div><!--QuoteEEnd--> Update: I have since updated to a new hard drive. Although the computer hasn't restarted on it's own, programs left running overnight closed out without me being on it. The event log pointed towards a faulty cable between the hd and mobo. Although the SATA cable was new, I installed another new one, AND the power cable also.
Since then no proggys have self-terminated and there have been no restarts. However, the event log still shows the faulty cable error on occasion, so something's not right.
<!--quoteo--><div class='quotetop'>QUOTE</div><div class='quotemain'><!--quotec--><b>Details </b> Product: Windows Operating System ID: 11 Source: Disk Version: 5.2 Symbolic Name: IO_ERR_CONTROLLER_ERROR Message: The driver detected a controller error on %1.
Explanation This problem is typically caused by a failing cable that connects the drive to the computer.
User Action Replace the cable.
Version: 5.0 Symbolic Name: IO_ERR_CONTROLLER_ERROR Message: The driver detected a controller error on %1.
Explanation This problem is typically caused by a failing cable that connects the drive to the computer.
User Action Replace the cable.
Version: 5.2.3790.1830 Message: Disk - The driver has detected a controller or cable error.
Explanation This event indicates that I/O failures have occurred on the volume.
Cause Possible causes include:
A hardware failure that prevents communication with a disk (for example, a loose cable, a loose disk controller card, or a cable failure).
User Action Do one or more of the following:
Check the status of your hardware for any failures (for example, a disk, controller card, or cable failure). Check Event Viewer for additional events from lower-level storage drivers that might indicate the cause of the failure. Restart the computer. Contact Microsoft Customer Service and Support.<!--QuoteEnd--></div><!--QuoteEEnd--> The "faulty cables" have been replaced. Twice. yet this error persists. Yesterday I ran the memtest86, doing 6 passes. No errors. At all.
New hd, new cables, memory's ok... WTH is left? I'm leaning towards a bad chipset in the mobo... dunno. It's an ASUS still under warranty. Oh yeah, the puter shop is running an over-the-weekend diagnostics on my OLD hd.
It has most likely been the disk controller all along (at least according to my friends on the Setup team who only stare at disk errors all day... poor saps). I take it this is integrated on the motherboard and cannot be replaced?
If no replacement possible, only a new motherboard or using an add-on controller instead will fix this. Failing hardware. The cable error is spurious, and caused by the communication problems where the controller stops responding - i.e. 'bad cable'. The driver reporting the error has no way to know the difference, and in most cases it's the cable, so they go with that error.
Thanks mons, I've been leaning towards the mobo myself, especially after I ran the memtest (6 passes) and found no errors with the ram. The computer shop that installed the ASUS P5S800-VM last fall is running diagnostics this weekend on my hard drive to rule that out - I guess they want to be sure before they replace the mobo (under warranty).
Interesting development: I've had a couple of BSODs today, and I'm fairly certain I had this same one with the other hd. BAD_POOL_CALLER, stop # 0x000000c2
If you run amd, try turning off SATA support in your bios, some amd processors have issues with sata and it causes BSOD's and strange behavior. If you narrow down that those reboots are not being caused by the cable, hdd, or controller itself, it could be a ram issue (video or system ram). Reboots are often caused by faulty ram where I work at. Also check all your software and try swapping out parts with other spare parts laying around the house and see what will keep it from rebooting.
After running a diagnostics test on my OLD hard drive over the weekend (no errors in 30 hours), the shop that upgraded me last fall is leaning towards the disk controller (which is intergrated into the mobo). Good news is, the ASUS PS5800-VM is still under warranty.
Towards the close of business today, if they still find no errors on the hd (which I doubt they will, as this NEW hd gives the same symprtoms) they are ordering me a replacement mobo. Free! <img src="style_emoticons/<#EMO_DIR#>/wink-fix.gif" style="vertical-align:middle" emoid=";)" border="0" alt="wink-fix.gif" />
The shop replaced the ASUS with an ABIT (the PS5800-VM is no longer in production, so they said), which I wasn't crazy about but hey, it's free being it's under warranty.
Windows got corrupted somehow in the deal, so they did a fresh install (CRAP, another format job) but then couldn't get the new mobo to recognize my GEForce 4600 video card. Hours of research later determined this card is not compatible with this mobo (something to do with the voltage).
SOOOOOooooo....., for another $70.00 they're upgrading the card to a GEForce 6200. Hopefully this nightmare will soon be over, I'm sick of this crap...
yuck <img src="style_emoticons/<#EMO_DIR#>/sad-fix.gif" style="vertical-align:middle" emoid=":(" border="0" alt="sad-fix.gif" /> hope they work it out soon... I'm so glad my latest compy is stable.
I've finally got it back home, albeit a lack of sound (probably needs drivers installed). I dislike all the garbage this shop installs with SP2, but I guess I can uninstall it if I don't want it.
Now the daunting task of reinstalling all my proggys and tweaking XP.... ... .. . <img src="style_emoticons/<#EMO_DIR#>/mad-fix.gif" style="vertical-align:middle" emoid=":angry:" border="0" alt="mad-fix.gif" />
Wow... last Friday morning I dropped off the computer to get a new mobo. Since the ASUS PS5800-VM is no longer in production, the shop opted to install an <a href="http://www.abit-usa.com/products/mb/products.php?categories=1&model=321" target="_blank">ABIT SG-80DC</a>, which is SUPPOSED to be identical.
Somehow they managed to corrupt Windows (and tried to blame it on me) so a fresh install was ordered, wiping my data out of course. Once they got that done and the drivers installed, they found out, after hours of research, that this mobo does not support my GEForce 4600 video card (wrong voltage).
Would I like to upgrade to a 6200-LE for 70 bucks? Well crap, I wasn't planning on shelling out any cash here, but what the hey, can't hurt, so they installed it and they were finally finished. I picked it up last night.
Seems a lot of extra proggys got installed when they install SP2 (not sure why). Most I like and can use (AVG, CCLeaner, Adaware) but seems I'll be uninstalling a bunch of crap.
And THEN... I get to start the re-installing of programs. Hopefully it will all be worth it.
A new mobo has not fixed the issue/s. I am still seeing multiple entires in the event log, split between two different IDs.
<!--quoteo--><div class='quotetop'>QUOTE</div><div class='quotemain'><!--quotec-->Product: Windows Operating System ID: 7 Source: Disk Version: 5.2 Symbolic Name: IO_ERR_BAD_BLOCK Message: The device, %1, has a bad block.
Explanation The device has a bad block of memory, which Windows attempted to read. The data might be missing or corrupted.
User Action If this event is logged regularly, replace the hard disk drive.<!--QuoteEnd--></div><!--QuoteEEnd--> <!--quoteo--><div class='quotetop'>QUOTE</div><div class='quotemain'><!--quotec--> Product: Windows Operating System ID: 11 Source: Disk Version: 5.2 Symbolic Name: IO_ERR_CONTROLLER_ERROR Message: The driver detected a controller error on %1.
Explanation This problem is typically caused by a failing cable that connects the drive to the computer.
User Action Replace the cable.
Version: 5.0 Symbolic Name: IO_ERR_CONTROLLER_ERROR Message: The driver detected a controller error on %1.
Explanation This problem is typically caused by a failing cable that connects the drive to the computer.
User Action Replace the cable.
Version: 5.2.3790.1830 Message: Disk - The driver has detected a controller or cable error.
Explanation This event indicates that I/O failures have occurred on the volume.
Cause Possible causes include:
A hardware failure that prevents communication with a disk (for example, a loose cable, a loose disk controller card, or a cable failure).
User Action Do one or more of the following:
Check the status of your hardware for any failures (for example, a disk, controller card, or cable failure). Check Event Viewer for additional events from lower-level storage drivers that might indicate the cause of the failure. Restart the computer. Contact Microsoft Customer Service and Support <!--QuoteEnd--></div><!--QuoteEEnd-->
Keep in mind a new mobo is installed, cables have been changed several times, and a new hard drive was installed (same errors produced - I returned the new hard drive and re-installed my old one). I also made 4 passes with memtest86, with no errors.
I am pulling my hair out here. I installed NS last night on a clean WindowsXP install, and it restarted on me a couple of times while joining teams or changing servers.
I am pulling my hair out here! <img src="http://www.ibparcade.com/style_emoticons/default/hairpull.gif" border="0" alt="IPB Image" />
<b>UPDATE:</b> Trashed the AVG (resource hog), installed new soundcard drivers, and installed the Microsoft tool UPHClean (as I was getting errors indicating a problem with freeing memory when logging off - this error was very similar to the BSOD STOP message I was getting).
The event log errors are nearly non-existent, my computer restarts in half the time it used to, the new RAM is smokin'.... and all seems to be well. *knock on wood*
Comments
Piece of cake, eh? NOT! Creative ran a diagnostics test, and told me that to install the drivers I had to uninstall current software. I did so, and that was it - it would NOT load Windows at restart, in SafeMode, Last Configuration, Normally, at all. I did notice a brief BSOD, but couldn't read it. Windows just would not load.
I'm formatting this hd one more time (this is the third time in as many weeks, I think. I may have done quick formats before - this time am doing the fullblown one).
If this fails, I have a brand new <a href="http://www.buy.com/prod/western-digital-raptor-x-hard-drive-150gb-10000rpm-150mbps-serial-ata/q/loc/101/202442761.html#prodInfoSec" target="_blank">WD Raptor</a> in the box ($302.00 at buy.com who is cheaper than Newegg usually). I got it for $192.00 at BestBuy. <img src="style_emoticons/<#EMO_DIR#>/smile-fix.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile-fix.gif" />
Well the real problem is you are asking for an analysis trough the internet. Yet it could be many things, which are not possible to test for trough the internet.
For instance:<ul><li>mem could be bad, and when the Os tries to write something into the memory which is corrupted it can reboot.
Then I'd advice <a href="http://www.memtest86.com/" target="_blank">http://www.memtest86.com/</a>
</li><li>Or it could be hear related asAnarkiThreeXSix said, go download some hardware temp monitor programs (probably included with the motherboard/pc)
</li><li>It could any number of hardware conflicts (mem vs cpu, cpu vs pci-controller, hdd vs mem and the list goes on)
are there any conflicts (start->programs->accessories->system tools->system information in here have a look at shares/conflicts or something)
</li><li>software related, try booting into safemode (for vista, is it still f8 for bootmenu? [edit]--> ACK! you've gone done and put a switch of OS on me!!! XP FTW!!!)</li><li>virus and spyware can kill the OS and make it reboot (most likely a bootsector virus on a fesh format, if it is viral)</li><li>gremlins, I swear!</li></ul>Basically all of the above could help you in determining what could be the cause, then the mighty internet/google can help you resolve it with tutorials. Or someone on here with a similar problem which was solved
<!--QuoteEnd--></div><!--QuoteEEnd-->
Update: I have since updated to a new hard drive. Although the computer hasn't restarted on it's own, programs left running overnight closed out without me being on it. The event log pointed towards a faulty cable between the hd and mobo. Although the SATA cable was new, I installed another new one, AND the power cable also.
Since then no proggys have self-terminated and there have been no restarts. However, the event log still shows the faulty cable error on occasion, so something's not right.
<!--quoteo--><div class='quotetop'>QUOTE</div><div class='quotemain'><!--quotec--><b>Details </b>
Product: Windows Operating System
ID: 11
Source: Disk
Version: 5.2
Symbolic Name: IO_ERR_CONTROLLER_ERROR
Message: The driver detected a controller error on %1.
Explanation
This problem is typically caused by a failing cable that connects the drive to the computer.
User Action
Replace the cable.
Version: 5.0
Symbolic Name: IO_ERR_CONTROLLER_ERROR
Message: The driver detected a controller error on %1.
Explanation
This problem is typically caused by a failing cable that connects the drive to the computer.
User Action
Replace the cable.
Version: 5.2.3790.1830
Message: Disk - The driver has detected a controller or cable error.
Explanation
This event indicates that I/O failures have occurred on the volume.
Cause
Possible causes include:
A hardware failure that prevents communication with a disk (for example, a loose cable, a loose disk controller card, or a cable failure).
User Action
Do one or more of the following:
Check the status of your hardware for any failures (for example, a disk, controller card, or cable failure).
Check Event Viewer for additional events from lower-level storage drivers that might indicate the cause of the failure.
Restart the computer.
Contact Microsoft Customer Service and Support.<!--QuoteEnd--></div><!--QuoteEEnd-->
The "faulty cables" have been replaced. Twice. yet this error persists. Yesterday I ran the memtest86, doing 6 passes. No errors. At all.
New hd, new cables, memory's ok... WTH is left? I'm leaning towards a bad chipset in the mobo... dunno. It's an ASUS still under warranty. Oh yeah, the puter shop is running an over-the-weekend diagnostics on my OLD hd.
If no replacement possible, only a new motherboard or using an add-on controller instead will fix this. Failing hardware. The cable error is spurious, and caused by the communication problems where the controller stops responding - i.e. 'bad cable'. The driver reporting the error has no way to know the difference, and in most cases it's the cable, so they go with that error.
Interesting development: I've had a couple of BSODs today, and I'm fairly certain I had this same one with the other hd. BAD_POOL_CALLER, stop # 0x000000c2
Towards the close of business today, if they still find no errors on the hd (which I doubt they will, as this NEW hd gives the same symprtoms) they are ordering me a replacement mobo. Free! <img src="style_emoticons/<#EMO_DIR#>/wink-fix.gif" style="vertical-align:middle" emoid=";)" border="0" alt="wink-fix.gif" />
Windows got corrupted somehow in the deal, so they did a fresh install (CRAP, another format job) but then couldn't get the new mobo to recognize my GEForce 4600 video card. Hours of research later determined this card is not compatible with this mobo (something to do with the voltage).
SOOOOOooooo....., for another $70.00 they're upgrading the card to a GEForce 6200. Hopefully this nightmare will soon be over, I'm sick of this crap...
Now the daunting task of reinstalling all my proggys and tweaking XP.... ... .. . <img src="style_emoticons/<#EMO_DIR#>/mad-fix.gif" style="vertical-align:middle" emoid=":angry:" border="0" alt="mad-fix.gif" />
Somehow they managed to corrupt Windows (and tried to blame it on me) so a fresh install was ordered, wiping my data out of course. Once they got that done and the drivers installed, they found out, after hours of research, that this mobo does not support my GEForce 4600 video card (wrong voltage).
Would I like to upgrade to a 6200-LE for 70 bucks? Well crap, I wasn't planning on shelling out any cash here, but what the hey, can't hurt, so they installed it and they were finally finished. I picked it up last night.
Seems a lot of extra proggys got installed when they install SP2 (not sure why). Most I like and can use (AVG, CCLeaner, Adaware) but seems I'll be uninstalling a bunch of crap.
And THEN... I get to start the re-installing of programs. Hopefully it will all be worth it.
<!--quoteo--><div class='quotetop'>QUOTE</div><div class='quotemain'><!--quotec-->Product: Windows Operating System
ID: 7
Source: Disk
Version: 5.2
Symbolic Name: IO_ERR_BAD_BLOCK
Message: The device, %1, has a bad block.
Explanation
The device has a bad block of memory, which Windows attempted to read. The data might be missing or corrupted.
User Action
If this event is logged regularly, replace the hard disk drive.<!--QuoteEnd--></div><!--QuoteEEnd-->
<!--quoteo--><div class='quotetop'>QUOTE</div><div class='quotemain'><!--quotec-->
Product: Windows Operating System
ID: 11
Source: Disk
Version: 5.2
Symbolic Name: IO_ERR_CONTROLLER_ERROR
Message: The driver detected a controller error on %1.
Explanation
This problem is typically caused by a failing cable that connects the drive to the computer.
User Action
Replace the cable.
Version: 5.0
Symbolic Name: IO_ERR_CONTROLLER_ERROR
Message: The driver detected a controller error on %1.
Explanation
This problem is typically caused by a failing cable that connects the drive to the computer.
User Action
Replace the cable.
Version: 5.2.3790.1830
Message: Disk - The driver has detected a controller or cable error.
Explanation
This event indicates that I/O failures have occurred on the volume.
Cause
Possible causes include:
A hardware failure that prevents communication with a disk (for example, a loose cable, a loose disk controller card, or a cable failure).
User Action
Do one or more of the following:
Check the status of your hardware for any failures (for example, a disk, controller card, or cable failure).
Check Event Viewer for additional events from lower-level storage drivers that might indicate the cause of the failure.
Restart the computer.
Contact Microsoft Customer Service and Support
<!--QuoteEnd--></div><!--QuoteEEnd-->
Keep in mind a new mobo is installed, cables have been changed several times, and a new hard drive was installed (same errors produced - I returned the new hard drive and re-installed my old one). I also made 4 passes with memtest86, with no errors.
I am pulling my hair out here. I installed NS last night on a clean WindowsXP install, and it restarted on me a couple of times while joining teams or changing servers.
I am pulling my hair out here! <img src="http://www.ibparcade.com/style_emoticons/default/hairpull.gif" border="0" alt="IPB Image" />
The event log errors are nearly non-existent, my computer restarts in half the time it used to, the new RAM is smokin'.... and all seems to be well. *knock on wood*