Blue screen of death

[Tomz_KV]

Sounds a desired feature. I got it for free. :)

TOMZ_KV

[Dirk Higbee]

When I first installed Vista I had to do some tweaking and once I saw the Black screen of death but not the Blue with Vista. :)

Member number three million seven hundred seventy two thousand nine hundred sixty three

[Richard Andrew x64]

Most likely a problem with a third-party driver, not Vista.

“Cannot find REALITY.SYS...Universe Halted.” ~ God on phone with Microsoft Customer Support

[Shog9 0]

Tomz_KV wrote:

Is this just me or a common problem for Vista?

It's you. Vista is flawless.

Citizen 20.1.01

'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'

[Paul Conrad]

:laugh: I do get this annoying "Windows Error" dialog box that pops up in Vista :rolleyes:

"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham

[Fernando A Gomez F]

Of course. The Windows Vista logo is next to the "flawless" word in any dictionary.

Stupidity is an International Association - Enrique Jardiel Poncela Die deutsche Sprache sollte sanft und ehrfurchtsvoll zu den toten Sprachen abgelegt werden, denn nur die Toten haben die Zeit, diese Sprache zu lernen. - Mark Twain

[pseudonym67]

You got Vists to RUN!!! :wtf:

pseudonym67 My Articles[^] Beginning KDevelop Programming[^]

[Tomz_KV]

I also see the "windows error" constantly.

TOMZ_KV

[El Corazon]

It was common in XP too. I crashed XP with blue screen in the first 2 days I had it. It became a badge of honor at our facility, my boss was the first to crash 2000, I was the first to crash XP. Of course the rules are you can't be deliberately trying, just doing your work. Hard to prove, but hey. I have reinstalled XP about two dozen times over its life, about 3 per machine, with a couple more at home. So far Vista has been no different, and maybe slightly more stable than early XP. One of the biggest problems is Programmer and vendor receiving of Vista. If you recall, everyone here discouraged any development for and on Vista, so of course, it will take longer to get stuff for Vista if no one is developing for it. That was a big mistake of MS, they should have courted the programmers. Vista has received very poor 3rd party support compared to previous OS's. So we are still paying the price of that.

[Miszou]

Haven't seen a blue screen for years - either on XP, Vista or Server 2003. Maybe it's your hardware?

Sunrise Wallpaper Project | The StartPage Randomizer | The Windows Cheerleader

[Anna Jayne Metcalfe]

I've never seen one under Vista (yet!), but I'm really used to them under XP...usually due to slightly iffy OEM-supplied drivers, it seems.

Anna :rose: Having a bad bug day? Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"

[Jerry Hammond]

I moved to Ultimate some months ago on a HP Laptop and have had no BSD...

“If we are all in agreement on the decision - then I propose we postpone further discussion of this matter until our next meeting to give ourselves time to develop disagreement and perhaps gain some understanding of what the decision is all about.”-Alfred P. Sloan

[xtravagan]

I would suggest download the Windows Debugging Tools and use windbg to open up the minidump that is created at the crash time to figure out which driver is causing the problem and fix it. Normally after a BSOD you will get a dialog in Vista telling you that Windows crashed, and in he dialog you will get links to 2 or 3 files, 2 of them are just collected environment info, one of them is the .dmp file. Open it in the windbg type .symfix !analyze -v This will take awhile as the symbols will be download for you OS setup, and then finally a report will spit out that usually gives you a stack trace location the problem. If not, you will bave to read up on some more advanced topics of windows debugging. Cheers

[originSH]

I had them occasionally, and the gfx subsystem rebooting (beats getting a bsod or crash for that ^_^) when I first got my system a year ago, but since then nvidia seem to have stablised their drivers a bit more and I haven't had any since.

[Mike Dimmick]

Microsoft claimed that data from their Online Crash Analysis programme, from Windows XP users up to April 2004, showed that: - 70% of all crashes were due to third-party device drivers; - 15% of crash dumps were too corrupt to be analyzed; - 10% were due to hardware errors; - 5% were attributable to Microsoft code. Most likely you have a bad driver or bad hardware. If the exception code is something like KMODE_EXCEPTION_NOT_HANDLED or IRQL_NOT_LESS_OR_EQUAL, it's most commonly a driver bug. The culprit should have been named on the blue screen. More esoteric crashes are generally the result of bad hardware. First, turn off any overclocking. It's called _over_clocking for a reason, you're going over the manufacturer's recommended settings. There's a reason they recommend those settings, it's for greatest stability. Overclocking is stupid. If nothing's overclocked, run a memory testing utility. Since you have Windows Vista, Microsoft's tester is already installed. Follow these steps[^] to run this tool.

DoEvents: Generating unexpected recursion since 1991