How to induce a BSOD

I've decided the easiest way is to get a picture from the web and make it full screen, but windows live photo gallery has decided that in slideshow mode I want it to zoom and show different parts of the photo when it feels like it, rather than just the full image :/
 
Use something like RW everything and change a CPU MSR variable to something stupid :D

I edit the C-States on my Laptop CPU to prevent whine but you could set the CPU to an invalid C-State and this would almost certainly BSOD the system. You will need to read the white-papers/tech details on the CPU you are using to get the register address for C-States though.
 
Last edited:
Go into Device Manager (Start > Right click "Computer" > Manage > Device Manager). Update the driver for one of your components, manually select a driver, select the wrong one (for example, tell the PC your sound chip requires a graphics driver) and it should blue screen nicely and safely.

During Windows boot pressing F8 and selecting "Last known good profile" should get you back up and running, but I can't promise. Try it and let us know if this works, or if you had to do a fresh Windows install to fix! :D
 
Go into Device Manager (Start > Right click "Computer" > Manage > Device Manager). Update the driver for one of your components, manually select a driver, select the wrong one (for example, tell the PC your sound chip requires a graphics driver) and it should blue screen nicely and safely.

During Windows boot pressing F8 and selecting "Last known good profile" should get you back up and running, but I can't promise. Try it and let us know if this works, or if you had to do a fresh Windows install to fix! :D

i dont think that would work surely if you install the wrong drivers the device just doesnt work
 
i dont think that would work surely if you install the wrong drivers the device just doesnt work

Depends how vital the component is. I did this with the IR input on a Blackgold TV card (PCI-E) to see if it was causing an issue and the PC BSOD'ed straight away. After rebooting to the last known good profile, I switched my brain back on and simply disabled the device.

By the way, turned out the device wasn't causing the issue, a remnant of a Hauppauge driver was.
 
Back
Top Bottom