More BSOD's

As suggested to make my own thread...

I've had multiple BSOD's, and I've finally got one of them to build a dump file.

kemo said:

As suggested to make my own thread...

I've had multiple BSOD's, and I've finally got one of them to build a dump file.

Kemo
There were two files involved in this crash Nero Vision and ntkrnlmp.exe. Nero is at best a problem in 64bit. there wasn't alot of info so it would be helpful if we could get info on what you were doing, how often its happened, etc

Ken


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\092209-23415-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02861000 PsLoadedModuleList = 0xfffff800`02a9ee50
Debug session time: Tue Sep 22 20:32:27.930 2009 (GMT-4)
System Uptime: 0 days 1:22:34.537
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff800028d4b62}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff800028d4b62

Debugging Details:
------------------


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: NeroVision.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff800028d2469 to fffff800028d2f00

STACK_TEXT:
fffff800`03bb2d28 fffff800`028d2469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`03bb2d30 fffff800`028d0932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`03bb2e70 fffff800`028d4b62 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`04be0148 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtContinue+0x222


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`028d0932 90 nop

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

Followup: MachineOwner

Ken
---------

I get blue screens all the time. Gaming, using nero, doing anything eventually leads to a BSOD. I'm just glad that something I JUST bought will bring me MORE bsod's. I'm gonna work on making another BSOD that always seems to happen so I can figure out why that one happens.

Kemo

there are so many things we need to find out that it going to take a little time.

Was it a clean install?

when did the bsod's start? was there ever a time with win 7 that you didnt have blue screens? ARe you overclocking?? do you have a raid?

ken

kemo said:

7 has been a LOT of BSOD's thus far. It was a clean install... can't go from XP 32 to 7 64. I got them on Day 2 of using Windows 7. All of them just pop up out of nowhere. According to my events, I have about 27 of them now... casual using, gaming, making dvd's, burning cd's. Such a wonderful experience.

No overclocking, no raid... just as basic as can be.

let see what kind of errors are in you event viewer go to start, search, type event viewer and go to the windows log, application tab. Look for anything with red "X" in the left hand column. using the snipping tool (built into win 7 type snipping tool in search) make a screenshot of the most comman type and upload it to us

ken

kemo said:

I get blue screens all the time. Gaming, using nero, doing anything eventually leads to a BSOD. I'm just glad that something I JUST bought will bring me MORE bsod's. I'm gonna work on making another BSOD that always seems to happen so I can figure out why that one happens.

First, I want to say my post is not meant to detract in any way from the excellent and always-helpful work done by my esteemed colleague ZigZag. You'd always do well to follow his advice :)

Short version: to me, your crash looks possibly related to the actions of your nVidia video driver - nvlddmkm.sys. Your version is dated Aug-17-2009, but if you can find an even newer build that would be the first thing to try. Otherwise, you should upload a few more minidumps so that we can check whether the pattern is always similar.



========================

Bore-me-to-tears version: counter-intuitively, the process whose thread is running at the time of the crash is almost always completely irrelevant. In this case, it may have been NeroVision.exe, but Nero is blameless. There's no simple way to explain this (well) without resorting to jargon, but one way of looking at it is that the OS _becomes_ Nero while it is servicing Nero's requests. Hence, crashes during the interval where the OS takes over cannot be blamed on Nero.

In fact, that's what WinDBG says, indirectly. It lists the running process as NeroVision, but it's quite clear on the point that ntkrnlmp ("NT KeRNeL, Multi-Processor version"), is the image where the crash occurred. While its automated analysis is very clever, it cannot possibly hope to always deduce the true cause of a crash. (An automated algorithm capable of doing that would be far more complex than the OS itself.)

To use the ever-popular car crash analogy, WinDBG is almost always right about the immediate crash cause: "the red car slammed into the blue car while doing warp 9 through the lights at the intersection." What it can't always do is tell you whether the driver of the red car had enough alcohol in his blood to start a distillery, or whether he had already died of a heart attack, or whether he was merely criminally insane. In debugging terms, figuring that out can be easy or complex - or even impossible - and it'll differ from crash to crash.

In your case, I have reason to suspect nvlddmkm.sys more so than other drivers.

the red car slammed into the blue car while doing warp 9 through the lights at the intersection." What it can't always do is tell you whether the driver of the red car had enough alcohol in his blood to start a distillery, or whether he had already died of a heart attack, or whether he was merely criminally insane.

That rat (insert word here).

Movin on... I've tried the latest Nvidia driver, turns out that it is the same version that came though windows update. Kinda SOL at the moment. When I get some spare time, I'll fire up GTA4, I've got it to BSOD in that a couple times too. Ever since the 6th bsod, someone had told me to disable the "automatically restart" and set it to minidump.

kemo said:

the red car slammed into the blue car while doing warp 9 through the lights at the intersection." What it can't always do is tell you whether the driver of the red car had enough alcohol in his blood to start a distillery, or whether he had already died of a heart attack, or whether he was merely criminally insane.

That rat (insert word here).

Movin on... I've tried the latest Nvidia driver, turns out that it is the same version that came though windows update. Kinda SOL at the moment. When I get some spare time, I'll fire up GTA4, I've got it to BSOD in that a couple times too. Ever since the 6th bsod, someone had told me to disable the "automatically restart" and set it to minidump.

Try going to the older 185 series Nvidia drivers, many have had problems using the newer 190 series. Yes the older drivers were for Vista but they work with Win7, sometimes better than the Win7 drivers.