PDA

View Full Version : BSOD with 91.x series Forceware Drivers


damicatz
07-30-06, 06:28 PM
I have a Geforce Go 6800 on a Dell Inspiron 9300.

The 87.xx series drivers work fine. Anytime I try to install the 90x series drivers, I get a blue-screen of death regarding nv4mini.sys. It's happened with a clean install of Windows and on an existing install.

Any suggestions?

grey_1
07-30-06, 06:34 PM
http://www.laptopvideo2go.com/

Try his modded inf, maybe the 91.33's. I think the general consensus is the 91.31's are pretty lacking anyway.

damicatz
07-30-06, 06:37 PM
http://www.laptopvideo2go.com/

Try his modded inf, maybe the 91.33's. I think the general consensus is the 91.31's are pretty lacking anyway.

I am using the modded inf from that site. Without it, the drivers won't even install (installer will exit with a message about unsupported hardware) and I'd have to use the year-old drivers that Dell supplies.

grey_1
07-30-06, 06:50 PM
I am using the modded inf from that site. Without it, the drivers won't even install (installer will exit with a message about unsupported hardware) and I'd have to use the year-old drivers that Dell supplies.

Just curious if you've tried the 33's yet. The 31's were bsod-ing on alot of systems I believe. Other than that maybe someone else with a 68go will jump in if they found a solution.

damicatz
08-10-06, 08:20 PM
Still can't get any 90x series drivers to work. The 80x ones work fine.

I opened up the memory dump from the BSOD


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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: ba0e5e21, The address that the exception occurred at
Arg3: b5d7d584, Trap Frame
Arg4: 00000000

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

ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.
ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,213F80,42250FF9
************************************************** ********

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 44d91261

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
nv4_mini+226e21
ba0e5e21 ff9088000000 call dword ptr [eax+88h]

TRAP_FRAME: b5d7d584 -- (.trap ffffffffb5d7d584)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=00000001 edx=00000000 esi=8953d008 edi=894f2970
eip=ba0e5e21 esp=b5d7d5f8 ebp=8953d008 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nv4_mini+0x226e21:
ba0e5e21 ff9088000000 call dword ptr [eax+88h] ds:0023:00000088=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 8953d008 to ba0e5e21

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b5d7d5f4 8953d008 00000000 00000000 00000001 nv4_mini+0x226e21
b5d7d5f8 00000000 00000000 00000001 89374a50 0x8953d008


STACK_COMMAND: kb

FOLLOWUP_IP:
nv4_mini+226e21
ba0e5e21 ff9088000000 call dword ptr [eax+88h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nv4_mini+226e21

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner