Has anyone seen this crash on Vista RC1?

NTDEV
1

kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at
an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 20205656, memory referenced
Arg2: 00000009, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 880106a0, address which referenced memory

Debugging Details:

READ_ADDRESS: 20205656

CURRENT_IRQL: 9

FAULTING_IP:
nvlddmkm!odbGetObject+10
880106a0 397908 cmp [ecx+0x8],edi

DEFAULT_BUCKET_ID: VISTA_BETA2

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 818d0313 to 8187c494

STACK_TEXT:
8191b664 818d0313 00000003 81910df4 00000000
nt!RtlpBreakWithStatusInstruction [d:\vistarc1\base\ntos\rtl\i386\debug2.asm
@ 47]
8191b6b4 818d0d80 00000003 20205656 880106a0 nt!KiBugCheckDebugBreak+0x1c
[d:\vistarc1\base\ntos\ke\bugcheck.c @ 271]
8191ba64 818395b0 0000000a 20205656 00000009 nt!KeBugCheck2+0x5f4
[d:\vistarc1\base\ntos\ke\bugcheck.c @ 1254]
8191ba64 880106a0 0000000a 20205656 00000009 nt!_KiTrap0E+0x2ac
[d:\vistarc1\base\ntos\ke\i386\trap.asm @ 5875]
8191bafc 880106c8 2020564e 00000046 00000001 nvlddmkm!odbGetObject+0x10
8191bb18 880106c8 83b14000 00000046 00000001 nvlddmkm!odbGetObject+0x38
8191bb34 880106c8 8a96b000 00000046 00000001 nvlddmkm!odbGetObject+0x38
8191bb50 88048179 83734a50 00000046 00000001 nvlddmkm!odbGetObject+0x38
8191bb6c 881ce43a 83734a50 00000046 00000000
nvlddmkm!notifyBufferHWComplete+0xda9
8191bbc8 88024815 83734a50 838e09c0 ffffffff
nvlddmkm!dispServiceVblank+0x14a
8191bbe4 88029390 83734a50 8191bc04 00000000
nvlddmkm!osInterruptPending+0x35
8191bc1c 880247cd 00000000 8395e9f8 83940000 nvlddmkm!osIsr+0xf0
8191bc2c 87fc8877 00000000 83aec500 831b0284 nvlddmkm!DoAgpTest+0x24d
8191bc3c 87fb5b30 8370bc28 87eaa212 83940000
nvlddmkm!CNvLAdapter::interruptRoutine+0x27
8191bc44 87eaa212 83940000 00000000 8191bc68 nvlddmkm!NvDM_StartDevice+0x140
8191bc54 87ebdfdd 83aec500 838c4430 00000000
dxgkrnl!DpiFdoMessageInterruptRoutine+0x17
[d:\vistarc1\windows\core\dxkernel\dxgkrnl\port\dpfdo.c @ 3533]
8191bc68 818744f4 83aec500 838c4430 004cf2b0
dxgkrnl!DpiFdoLineInterruptRoutine+0x12
[d:\vistarc1\windows\core\dxkernel\dxgkrnl\port\dpfdo.c @ 3474]
8191bc94 81874469 83940002 000000a4 8191bd50 nt!KiChainedDispatch2ndLvl+0x48
[d:\vistarc1\base\ntos\ke\i386\intsup.asm @ 378]
8191bc94 83e75ab4 83940002 000000a4 8191bd50 nt!KiChainedDispatch+0x29
[d:\vistarc1\base\ntos\ke\i386\intsup.asm @ 278]
8191bd14 83e76a53 81920610 83a5d5bc 8187fc32 amdk8!C1Halt+0x4
[d:\vistarc1\base\hals\processor\lib\i386\cpu.c @ 188]
8191bd20 8187fc32 83b388a0 81922300 8191e700 amdk8!C1Idle+0x25
[d:\vistarc1\base\hals\processor\lib\cstates.c @ 403]
8191bd50 81875f92 00000000 0000000e 00000000 nt!PopIdleDefaultHandler+0x239
[d:\vistarc1\base\ntos\po\ppmidle.c @ 267]
8191bd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xa
[d:\vistarc1\base\ntos\ke\i386\ctxswap.asm @ 1590]

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm!odbGetObject+10
880106a0 397908 cmp [ecx+0x8],edi

FAULTING_SOURCE_CODE:

SYMBOL_STACK_INDEX: 4

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nvlddmkm!odbGetObject+10

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 44cfa16f

FAILURE_BUCKET_ID: 0xD1_nvlddmkm!odbGetObject+10

BUCKET_ID: 0xD1_nvlddmkm!odbGetObject+10

Followup: MachineOwner

Regds,
-Praveen

2

The crash is in the pre-release NVIDIA display driver… Not that surprising given the extent of the changes in video drivers in Vista, the pre-release state of the OS and the drivers, and the complexity of graphics cards.

What are you asking, precisely?

Peter
OSR

3

Hi,

You answered my question. I was asking who the culprit is?

Thanks,
-Praveen

wrote in message news:xxxxx@ntdev…
> The crash is in the pre-release NVIDIA display driver… Not that
> surprising given the extent of the changes in video drivers in Vista, the
> pre-release state of the OS and the drivers, and the complexity of
> graphics cards.
>
> What are you asking, precisely?
>
> Peter
> OSR
>
>

4

Hi,
If you are interested in learning how to go one step further and be able to analyze the output of a crash dump yourself, you can look at the webcast “TechNet Webcast: Windows Hang and Crash Dump Analysis” by Mark Russinovich, which is located at:

http://www.microsoft.com/events/EventDetails.aspx?CMTYSvcSource=MSCOMMedia&Params=~CMTYDataSvcParams^~arg+Name%3D"ID"+Value%3D"1032298076"%2F^~arg+Name%3D"ProviderID"+Value%3D"A6B43178-497C-4225-BA42-DF595171F04C"%2F^~arg+Name%3D"lang"+Value%3D"en"%2F^~arg+Name%3D"cr"+Value%3D"US"%2F^~sParams^~%2FsParams^~%2FCMTYDataSvcParams^

You can also find the same link by going to www.sysinternals.com and clicking on the title of the webcast.

After looking at the webcast, you’ll see that !analyze -v provides the image name of the crashing driver (IMAGE_NAME: nvlddmkm.sys). Depending on the reason of the crash this might be accurate or not (because sometimes driver A might corrupt the memory that belongs to driver B and in the end driver B will crash, even though driver A is the root of the cause). In the case of DRIVER_IRQL_NOT_LESS_OR_EQUAL (which is really common), the name is correct.

After that a simple search in your favorite search engine (i.e. nvlddmkm.sys) would show the owner of the driver.

Ilias

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Praveen Kumar Amritaluru
Sent: Monday, September 11, 2006 9:59 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Has anyone seen this crash on Vista RC1?

Hi,

You answered my question. I was asking who the culprit is?

Thanks,
-Praveen

wrote in message news:xxxxx@ntdev…
> The crash is in the pre-release NVIDIA display driver… Not that
> surprising given the extent of the changes in video drivers in Vista, the
> pre-release state of the OS and the drivers, and the complexity of
> graphics cards.
>
> What are you asking, precisely?
>
> Peter
> OSR
>
>

—
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer