Hello,

There is a reason for allowing the computer operator to implement a bugcheck (a/k/a stop error or blue screen of death). A computer running Microsoft Windows can be configured to write the contents of kernelspace memory to disk in the event of a bugcheck, and the resulting file can then be sent to a developer for analysis to determine the faulting module.

So, in a nutshell, it is a debugging tool to allow a programmer to get a copy of the contents of memory.

Regards,

Aryeh Goretsky

Yeah, I was going to say that too…just install the DVD/CD onto a computer and wait n seconds and Voila! BSOD!

I haven’t actually tried it yet but i was wondering how do you get out of the BSOD once you do the steps?

Windows seems likely enough to crash without creating a key combo to make it do so. How about a way to interrupt a crash in progress, to save open files?

In my 1.5 year practice of using Vista (since the first beta version and on the RTM and SP1) I have never had Vista turning to BSOD. Though I have used it on my home desktop and work laptop PC. They both were running Vista Ultimate (RTM, then SP1).

So stop bothering with that insist on Vista crashes.

BTW, i were running a purchased and licensed Vista.

P.S. Thanks for the tip.Seems really to be made for debug purpose.

actually i have had BSODs on several occasions. at least one was caused by a poor driver.

i have also had it “lock”, becoming completely unresponsive. this is where forcing a bluescreen comes in. even tho the computer is “locked up”, everything is in memory. forcing a bluescreen will create the .dmp file so you can troubleshoot the cause of the lockup.

I bought a new laptop a few months ago with Vista and now I get the BSOD at least 3 times a day. Im buying a Mac.