[rodeognome]

Turning on PC to get nice big BSOD

"inaccessible boot device" message....

Did a quick google, and all the resolutions were either inplace reinstall or complete reinstall. Not fancying the prospect of this at all...i decided to tinker with it further. So I slaved it on to another system and ran check disk on startup...hey presto chk dsk actually found missing files and fixed them...( I've always seen chk dsk as just another Windoze gimmick but it worked this time).

Well I just thought I would share that you ye guyz.

So if you suspect the system has a BSOD because of a driver related issue just slave the hdd containing the faulty OS and run CheckDisk.


Well I just thought I would share that you ye guyz.

[Elvandil]

Chkdsk is certainly a neglected utility. File system errors can lead to all kinds of problems, from system slowdowns to the more serious like your example. It has saved my bacon more than once, and even helped me recover from a failed Partition Magic partitioning.

Another major cause of the error you mentioned on new installs and new systems is not having the correct 80-wire IDE cable for UDMA.

[primetime212]

Originally Posted by rodeognome

Turning on PC to get nice big BSOD

"inaccessible boot device" message....

Did a quick google, and all the resolutions were either inplace reinstall or complete reinstall. Not fancying the prospect of this at all...i decided to tinker with it further. So I slaved it on to another system and ran check disk on startup...hey presto chk dsk actually found missing files and fixed them...( I've always seen chk dsk as just another Windoze gimmick but it worked this time).

Well I just thought I would share that you ye guyz.

So if you suspect the system has a BSOD because of a driver related issue just slave the hdd containing the faulty OS and run CheckDisk.


Well I just thought I would share that you ye guyz.

here is a good article relating to that
good read

http://www.updatexp.com/stop-messages.html