Blue screen occurs after occasional automatic updates

I followed your instructions, but most of the options you mentioned were already set, but there were a few exceptions:

All the options you instructed me to set were already correctly configured up to step 4. Upon opening the choose programs dialogue in step 4, "all programs" was already selected. However, I noticed a "Do not report errors for these programs" box just below it, and it had an entry called soffice.exe . I removed this entry.

Under startup and recovery, all the options you had requested were already selected, except for automatic restart, which I had previously unselected because I want the computer to show the bluescreen, and not inexplicably restart.

Also, when selecting write debugging information under the startup and recovery, small memory dump is listed as 128kb instead of 64kb. This was the default option. There is no small memory dump 64kb option, the only options are small memory dump 128kb, kernel memory dump, and complete memory dump.
 
Two days, so far so good. It might take as long as a month for this problem to manifest again.

In any case, thanks for all your help. I now have an approach to deal with this problem the next time it shows up. I will post on this board again one it does.
 
Ok, you know how I said it would probably be a month before a new problem occured, well I was wrong.

Absolutely nothing happened yesterday evening when I went to shut my computer off. However, when I came home today, my computer wouldn't start. It powered on, the cooling fans engaged(although only at their low, pre-boot speed), the power LEDs were on, but BIOS wouldn't start(or at least, the splash screen didn't come up). The system just hung in the pre-BIOS state. Note that the hard drive LED and was lit during this time, and one of the DVD-ROM drive LEDs periodically lit. After several more attempts, it still hung in the pre-BIOS state. After shutting down and waiting about 30 seconds to 1 minute, and disconnecting and reconnecting the peripherals, the machine finally booted. This occurred using the Samsung RAM.

Once I got the machine online and working normally, I cracked the case and switched the RAM, I am now running Centron RAM. I will now see if this problem occurs again under new RAM.

I the mean time, I don't suppose you have any idea what could be wrong with my computer. This problem is definitely in the hardware realm now, as the system wasn't even able to load the BIOS.

Thanks.
 
I'm wondereing if it is the motherboard itself. It is a shame you can't get a hold of one more set of RAM say Kingston or Crucial just to test it out.

Whatever, it seems to be your RAM in the mix but if there is an issue with the motherboard no amount of RAM is going to help. Let me see if I can get someone else's advice on this.
 
It definitely could be the motherboard. I have already replaced this model of motherboard once under warranty. I was hoping this one would last.

In any case, I am hoping only one of the two sets of RAM are the culprit. With any luck, it was the Samsung RAM that was causing the problem. Otherwise, this problem is going to be hard to fix.
 
Back