Re: My PC just broke down.... :(

On Mon, 15 Aug 2005 22:57:30 +0200, Sandman <mr@xxxxxxxxxxx> wrote:

>In article <1h1ctvl.1m7hgja6tddu2N%not_in_use@xxxxxxxxxxxxxx>,
>not_in_use@xxxxxxxxxxxxxx (Peter Hayes) wrote:
>
>>>>> It wasn't until recently I actually learned you have to turn off
>>>>> the option to automatically reboot in order to actually see the
>>>>> BSOD, which only gave one line of information which I don't recall
>>>>> at the moment (something like DRIVER_IRQL_SOMETHING_SOMETHING
>>>>
>>>> This is hilarious. One driver went kablooey on you and you ended up
>>>> reloading the whole machine!?
>>>
>>> No, not at all. the above passage is about the frequent crashes I've
>>> had, where Windows just reboots mid-operation.
>>
>> Overheating or bad memory.
>
>Yeah, I suspected that at times, but it could happen at any time, even if I
>wasn't actually using the machine (i.e. I get home from work to find my PC at
>the login screen).
>
>>> The reason I re-installed Windows is because it wouldn't even boot.
>>> They are different things, although I'm sure they could be related.
>>> The frequent crashing most certainly was driver-related, but the
>>> Windows not being able to boot seems to be related to a HD problem
>>> (as in filesystem or MBR, not physical - or so I am assuming).
>>
>> So if you had a boot floppy you could have issued the undocumented but
>> well known command fdisk /mbr - assuming you had a FDD of course.
>
>As it is, I don't own a floppy reader since 1999 or something like that.

Perhaps you should spend the $5.00 and buy one so that you can save
yourself a lot of time should this happen again.

Josh

>> It might be an idea to invest a few kronas in one, especially as there
>> seems to be something amiss with your machine.
>
>We'll see if the random crashing resurfaces after this reinstallation. And it's
>"kronor". :-D
>
>>>>> The thing is that my goal at the moment was to find some form of HD
>>>>> diagnostics tool that could help me find out if the problem was
>>>>> with my filesystem (which was, and still is, my guess).
>>>>
>>>> Its called checkdisk.
>>>
>>> But its name is chkdsk. The MacOS installer has a Disk Utility with a
>>> big "Verify Disk" button. I know you'll fail to see the difference,
>>> so I only mention it for comic relief.
>>
>> You can run chkdsk on a "mounted volume" (in inverted commas because
>> Windows doesn't have the concept of unmounted volumes). To fully check
>> a Mac disk you need to boot off the installer CD/DVD.
>
>Yeah, that's nice. Not that it helped me here, but...

.

Relevant Pages