Creating BSODs? 40
mvanhorn asks: "This is not a joke, or a troll, but my company is testing a failover solution for NT and we were wondering about simple reliable ways to intentionally cause a BSOD. Please don't say "just fire up an application..." it will be neither useful, or funny. But really humorous answers that solve the problem are welcome."
Put in some flaky hardware? (Score:2)
programs (Score:2)
try:
hackers.com [hackers.com]
L0pht.com [l0pht.com]
hackers.com has a large archive of programs.
-----
If my facts are wrong then tell me. I don't mind.
Goto your local jr college... (Score:2)
Mark Duell
Device drivers are the key. (Score:3)
It used to be pretty easy to crash NT by simply stressing IIS, but I haven't had much luck with that of late. My suspicion is that Active Directory Services is the new IIS (in the sense that it's new, delivers lots of functionality that is relied upon by core components). So probably writing a program that recursively adds itself to ADS is probably pretty effective.
Re:Device drivers are the key. (Score:2)
Recursive Calling (Score:1)
Re:Recursive Calling (Score:2)
unplug a disk ? (Score:1)
Of course there are lots of derivate ways to cause a major failure, except unpluging the screen as you then wouldn't be able to see if it becomes blue.
"Good" Luck.
--
HALT! (Score:1)
nop
nop
nop
nop
halt
How much simpler can one get?
Re:Recursive Calling (Score:1)
Re:unplug a disk ? (Score:1)
Re:unplug a disk ? (Score:1)
--
Re:Device drivers are the key. (Score:1)
If you wrote a device driver to do this, shouldn't you be able to jump straight to the BSOD code? If this is possible, it seems like it would be much more straightforward than passing the kernel bad data. If i wanted to do something like this on a linux box, i'd just write a dev driver that would call panic() on some condition (like, say, as a misc char device, and panic when some value is written to the dev node). Maybe something like this is possible within an NT driver.
BSOD on NT4 ( dunno about W2K ) (Score:2)
BSOD
Winlogon.exe (Score:1)
Re:Recursive Calling (Score:3)
Re:BSOD on NT4 ( dunno about W2K ) (Score:1)
Sure, I had to try this. The tray is gone even as I type, everything gets minimized to a standard issue Windows minimized box right above where there used to be a tray. So, it must have been fixed in some SP.
I'll try to use the computer as long as I can before rebooting, just for the kick.
Re:Winlogon.exe (Score:1)
well, in win2k anyway... (Score:2)
load the driver...
now just TRY to boot without a STOP ERROR!
(this also works with an internal 9300 w/out updated drivers)
OR use a Realtek chipset NIC and do a Win2k online update and choose to use MS new online realtek drivers. (this works on 50% of the machines)
OR (heh) convert your NTFS directory (in win2k) to HPFS, it SEEMS to support it for a while, and then "decides" not to support it. (did MS really take HPFS support out, or just make it not work?)
Use old reference drivers for windows 98 to install video cards in win2k. works like a charm. if working means stop errors anyway.
Use Fast page and EDO simms mixed together.
or a variation on this, use an old BIOS and an ODD number of simms, or a version of the bios that lets you force the bios into thinking it has more ram than it does.
Use a Western digital mastered to a Seagate Slave drive (if it will boot, HDD errors will happen fo no good reason) This is neither WD's fault nor Seagates...They both use funny ways of determining master/slave
Load Office 95, then load Norton Windoctor and let it "fix" the registry.
I like this one, put your swap file on a zip drive, but dont use Iomega 2000 tools to install the zip, now eject the zip. Be sure the BIOS sees the zip as a 100Mb Hard drive, not a ARMD device.
Install win2k with ACPI support, using a bios that SUPPORTS it, then flash the version that came out before w2k, that doesnt fully support ACPI.
Dont know of any NT specific crashes other than con/con or nul/nul, but it was muck easier to crash NT, win2k seems pretty stable, as far as messing around with it, win2k is much more forgiving than NT was.
Re:here you go (Score:1)
I was going to suggest this, but then I thought, doesn't that only work on unpatched 95 machines? Even 98 shouldn't ship with port 139 listening, IIRC, because this (or a similar) nuker works *so* well -- a totally debilitating attack carried out in a mere second or two. My coworkers and I used to use this exploit to nuke a box we were using to monitor network status whenever we got bored.
Okay, so this is mostly reminiscing. Anyway, my point is, I doubt the port-139 attack will work on any versions of Windows post-95. If it does, well, Microsoft is even dumber than I gave them credit for.
There's a Dialup Networking patch for Win95 users that will fix this vulnerability, sort of; I'd post a link but I couldn't find it on MS' site. Maybe they're trying to force people to upgrade.
QBASIC (Score:1)
'causes GPF, but not BSOD
DEF SEG = &H0000
POKE 32, 32
END
Getadmin (Score:1)
Re:BSOD on NT4 ( dunno about W2K ) (Score:1)
This should be pretty easy (Score:1)
I'm not much of a Windows programmer, but I think you can write NT device drivers that run in kernel mode (meaning privilege level 0). Once you have that going, just use a few instructions in it to cause a processor exception, like maybe a page fault. You could then access the driver from other software. I do think this would be a slight security risk... :)
SysInternals has your answer (Score:4)
SysInternals [sysinternals.com] has a solution for this. One of its products is called BlueSave [sysinternals.com], which is a utility that will save the text of the BSOD to a file. BlueSave is conveniently packaged along with a companion utility that will cause your PC to crash to the BSOD.
C:/CON/CON (Score:1)
Use pre-SP3 (Score:2)
Re:Getadmin (Score:2)
SP4, which contained the initial fix for getadmin,
is still vunerable to it!
Adaptec EZ-CD Creator 3.5 (Score:1)
and watch the machine die a slow horrible painful death...at least it did for me. That's why everyone has to upgrade to EZ-CD v.4...
-Smitty
BSOD (Score:1)
This might not BSOD, but it will crash the machine for sure. Just leave the cover off the machine. When it is time to crash it, just unplug the power from the hard disk. It will crash very shortly. (besides, I'd hope your product can handle a crashed hard disk in one of the machines!)
Re:QBASIC (Score:2)
Re:Device drivers are the key. (Score:1)
---
Joseph Foley
Akamai Technologies
OOBD attack on the machine (WinNUKE) (Score:1)
BSOD answers.. (Score:1)
Also there is a pretty good procedure outline in the link below. The article is about clustering and testing it.
http://www.microsoft.com/TechNet/winnt/Winntas/
The Toddler
Re:BSOD answers.. (Score:1)
Perhaps they made it too stable? There is a registry entry that you can use to force a blue stop screen on Windows NT (hopefully this is because you won't ever see one otherwise). First, backup your registry, then make the following change:
Hive: HKEY_LOCAL_MACHINE
Key: System\CurrentControlSet\Services\i8042prt\Parame
Name: CrashOnCtrlScroll
Data Type: REG_DWORD
Value: 1 (0 or nothing will disable the feature)
After a restart, holding down the right-side CTRL key and pressing the Scroll lock key twice will generate the Blue Screen of Death.
Good luck.
hard freeze (Score:2)
Have a shortcut on your desktop to a folder on a network drive, rightclick-explore, wait 5 seconds,l try and do anything.
I was running NT4 SP5 with tons of random things. Try and do it without the server service running.
Re:Put in some flaky hardware? (Score:1)
It worked well for causing BSOD's, but took a few hours to work up to doing it.
Re:Adaptec EZ-CD Creator 3.5 (Score:1)
EZ-CD 4.0 was too bloated for me, so I just switched to Nero Burning Rom, which lets you overburn (something adaptec doesn't)
~tide~
"Linux is only free if your time has no value."
Try typing in "Linux" ... (Score:1)
One of the few anti-competitive (or too competitive?) measures undetected by judge or janitor.
One of the others is that Bill Gates uses hired goons to trash out other companies, thinly fictionalised in "The Simpsons".
Rename the display driver (Score:1)
Get the name of your display driver's main DLL (from the INF file of your display driver) and rename it. Next time you boot you'll get a BSOD.
To change it back just boot to safe mode and rename again.