The Windows B.S.O.D.
0
For the tech illiterate that stand for Blue Screen Of Death and I got it a few days :cry: but I just shut my laptop down and rebooted it and everything was fine. So I was wondering should I get it checked out by a professional or just leave it be??
0
i don't know if mine was exactly like that but it looks pretty close i just restarted and it hasn't shown again for me.
0
Usually caused by a driver error. Maybe you upgraded a driver and the OS didn't like it or maybe it got corrupted or something? I've also had problems with USB devices disagreeing with one another. For some reason my razor mouse's firmware becomes corrupted about once every 5 months or so and I have to reflash it, but when it's corrupted it will act up like that when I restart the computer with it still plugged in.
0
Did this happen while running the recovery console? Windows points to the driver spcmdcon.sys which is used by the RC. The only thing i was able to find was this on another forum:
"When you run the RC, Session Manager loads and starts two device drivers that implement the RC: spcmdcon.sys and setupdd.sys. Setupdd.sys is a support driver that gives spcmdcon.sys a set of functions that let spcmdcon.sys manage disk partitions, load Registry hives, and display and manage video output. Setupdd.sys communicates with disk drivers to manage disk partitions and uses basic video support built in the Win2K kernel to display messages on the screen"
I'm probably never going to get a mouse from razer again, had to send my copperhead back because it kept disconnecting and reconnecting itself every 5 sec. The service is pretty good though, had a new one within a week, and so far so good, haven't had problem with the new one. You only need to look at this blog to see I'm not alone here: http://blog.razerzone.com/2005/11/13/new-products-coming-part-ii/ , they should test their products thoroughly before getting them out to consumers.
"When you run the RC, Session Manager loads and starts two device drivers that implement the RC: spcmdcon.sys and setupdd.sys. Setupdd.sys is a support driver that gives spcmdcon.sys a set of functions that let spcmdcon.sys manage disk partitions, load Registry hives, and display and manage video output. Setupdd.sys communicates with disk drivers to manage disk partitions and uses basic video support built in the Win2K kernel to display messages on the screen"
nsl41288 wrote...
Usually caused by a driver error. Maybe you upgraded a driver and the OS didn't like it or maybe it got corrupted or something? I've also had problems with USB devices disagreeing with one another. For some reason my razor mouse's firmware becomes corrupted about once every 5 months or so and I have to reflash it, but when it's corrupted it will act up like that when I restart the computer with it still plugged in.
0
well B.S.O.D is Better than total system failure or lost of Files..
yea but i do not get B.S.O.D much so i would not know.
last time i got it i let java run to long and it ate up all the system memory till their was non left for the computer to run its self and it shut down. :lol:
yea but i do not get B.S.O.D much so i would not know.
last time i got it i let java run to long and it ate up all the system memory till their was non left for the computer to run its self and it shut down. :lol:
0
A very good way to see if your drivers or I/O address's are causing the problem is to open Device Manager and click the + signs. If you see any ! symbols double-click that particular device and it should tell you why its' flagged. If there are any 'Driver Conflicts' it will tell you. Make sure to check each piece of hardwar in the Device Manager for this error. As for those of you that have had a blue screen once or twice and rebooted to find the problem was gone, XP and Vista are designed to pick up on any driver conflicts and fix/solve them after a reboot. It is important to note that some driver conflicts cannot be solved automatically. Now here's the interesting part; if you get General Protection Faults [blue screens of death] very frequently, and you cannot seem find any driver conflicts, you might have defective/damaged RAM. To test this, write down the 'address' that is shown on every blue screen. It will be a series of numbers and letters, and usually starts with 0x. Write this down for SEVERAL different blue screens. After about ten different blue screens, check the list and see if they are EXACTLY identical to each other. If they are, you most likely have a defective RAM stick. When this occurs, The OS randomly accesses the RAM [like it always does] but as soon as it tries to access the damaged part of the RAM stick, chaos insues and a blue screen is the result. I hope this helps anyone that ever has this problem. Don't jump to conclusions if you ever get one though, most computers experience a small handful of blue screens in their lifespan, with no real problems.
0
Hibia wrote...
Tegumi wrote...
What I want to know is how a screenshot was taken of a BSOD. >_>;;VMWare?
but how was it running with the B.S.O.D up
0
Tegumi wrote...
What I want to know is how a screenshot was taken of a BSOD. >_>;;Because your mom was there all night long. OH SNAP! :lol:
0
Cilx wrote...
Hibia wrote...
Tegumi wrote...
What I want to know is how a screenshot was taken of a BSOD. >_>;;VMWare?
but how was it running with the B.S.O.D up
A virtual machine is able to emulate operating systems, so whoever took that screenshot most likely had Windows running off a virtual drive. The operating system running within the virtual machine can crash just like it did but it won't directly effect your current operating system.
Look below, I posted a screenshot of FreeBSD running on a VM.
That being said, if I was to have a kernel panic while running FreeBSD, that's all that will happen. It'll restart and boot back up again without affecting my physical operating system.
0
Klorofolun wrote...
Tegumi wrote...
What I want to know is how a screenshot was taken of a BSOD. >_>;;Because your mom was there all night long. OH SNAP! :lol:
I was hovering over the delete button, but then I remembered you had a ZP avatar, so I couldn't.
