Driver problem

[cmb99]

Ok, I get intermittent crashes. I think it is a driver problem,
possibly Nvidia. Anyone know how to read these?


*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {bad0b148, 0, 80563fe2, 0}


Could not read faulting driver name
Probably caused by : ntoskrnl.exe ( nt!ObpRemoveObjectRoutine+cb )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by
try-except,
it must be protected by a Probe. Typically the address is just plain
bad or it
is pointing at freed memory.
Arguments:
Arg1: bad0b148, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 80563fe2, If non-zero, the instruction address which referenced
the bad memory
address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: bad0b148

FAULTING_IP:
nt!ObpRemoveObjectRoutine+cb
80563fe2 833800 cmp dword ptr [eax],0x0

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 804e3c55 to 80563fe2

STACK_TEXT:
af0ccb48 804e3c55 e5889550 00000000 af0ccca0
nt!ObpRemoveObjectRoutine+0xcb
af0ccb6c 80563a83 af0ccbb8 af0ccb88 80563ad0
nt!ObfDereferenceObject+0x5f
af0ccb78 80563ad0 af0ccbb8 af0cccf4 af0ccc48
nt!SeReleaseSubjectContext+0x11
af0ccb88 80586496 af0ccb9c 00000000 00000000
nt!SeDeleteAccessState+0x42
af0ccc48 80585eff 00000000 00000000 af0ccb9c
nt!ObReferenceObjectByName+0x197
af0ccd10 80598c58 00162320 0012a3d4 0012a3dc
nt!NtSecureConnectPort+0x1e4
af0ccd3c 804df06b 00162320 0012a3d4 0012a3dc nt!NtConnectPort+0x24
af0ccd3c 7c90eb94 00162320 0012a3d4 0012a3dc nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be
wrong.
0012a4c4 00000000 00000000 00000000 00000000 0x7c90eb94


FOLLOWUP_IP:
nt!ObpRemoveObjectRoutine+cb
80563fe2 833800 cmp dword ptr [eax],0x0

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!ObpRemoveObjectRoutine+cb

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 41108004

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0x50_BADOBJREF_nt!ObpRemoveObjectRoutine+cb

BUCKET_ID: 0x50_BADOBJREF_nt!ObpRemoveObjectRoutine+cb

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

 

[Gerry Cornell]

Have you looked in Device Manager for yellow question marks and Device Error
codes?

You might try testing your memory

Memtest86 - Memory Diagnostic Page:
http://www.memtest86.com/

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Ok, I get intermittent crashes. I think it is a driver problem,
possibly Nvidia. Anyone know how to read these?


*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {bad0b148, 0, 80563fe2, 0}


Could not read faulting driver name
Probably caused by : ntoskrnl.exe ( nt!ObpRemoveObjectRoutine+cb )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by
try-except,
it must be protected by a Probe. Typically the address is just plain
bad or it
is pointing at freed memory.
Arguments:
Arg1: bad0b148, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 80563fe2, If non-zero, the instruction address which referenced
the bad memory
address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: bad0b148

FAULTING_IP:
nt!ObpRemoveObjectRoutine+cb
80563fe2 833800 cmp dword ptr [eax],0x0

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 804e3c55 to 80563fe2

STACK_TEXT:
af0ccb48 804e3c55 e5889550 00000000 af0ccca0
nt!ObpRemoveObjectRoutine+0xcb
af0ccb6c 80563a83 af0ccbb8 af0ccb88 80563ad0
nt!ObfDereferenceObject+0x5f
af0ccb78 80563ad0 af0ccbb8 af0cccf4 af0ccc48
nt!SeReleaseSubjectContext+0x11
af0ccb88 80586496 af0ccb9c 00000000 00000000
nt!SeDeleteAccessState+0x42
af0ccc48 80585eff 00000000 00000000 af0ccb9c
nt!ObReferenceObjectByName+0x197
af0ccd10 80598c58 00162320 0012a3d4 0012a3dc
nt!NtSecureConnectPort+0x1e4
af0ccd3c 804df06b 00162320 0012a3d4 0012a3dc nt!NtConnectPort+0x24
af0ccd3c 7c90eb94 00162320 0012a3d4 0012a3dc nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be
wrong.
0012a4c4 00000000 00000000 00000000 00000000 0x7c90eb94


FOLLOWUP_IP:
nt!ObpRemoveObjectRoutine+cb
80563fe2 833800 cmp dword ptr [eax],0x0

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!ObpRemoveObjectRoutine+cb

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 41108004

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0x50_BADOBJREF_nt!ObpRemoveObjectRoutine+cb

BUCKET_ID: 0x50_BADOBJREF_nt!ObpRemoveObjectRoutine+cb

Followup: MachineOwner

 

[cmb99]

Have you looked in Device Manager for yellow question marks and Device Error
codes?

Yes, there is one there. I have never figured out what it was. All of
my peripherals and ports seem to be accounted for.

You might try testing your memory

Memtest86 - Memory Diagnostic Page:

http://www.memtest86.com/

Doesn't this always produce errors. I mean woudln't memory have to be
perfect to pass?

 

[Gerry Cornell]

What is the name of the device? What is the Device Error code number? Look
at each tab in turn. Right click on the My Computer icon on your Desktop,
sand select Properties, Hardware, Device Manager.

Seeing as we have identified something to put right let's leave testing
memory for now. Testing memory does not always produce errors! The purpose
of testing is to find out whether there is a problem. If there is not we
look elsewhere.

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

The purpose of these newsgroups is to find out things we do not know,
however, computer literate we are!

 

[needlove]

Try downloading and installing the latest driver from nVidia. It fixed my
problem. Seems the old driver (nv4_disp.dll) had a problem with WMD.