Help! Won't install drivers on 770m! :(

Hi all,

I've upgraded my MSI with a 675m (Dead), with a clevo 770m. After flashing the bios, and having Windows recognize it, I'm having a really hard time installing drivers that will work without crashing. I can't even render the nvidia control panel 3d logo.
It worked a couple of times, but then it crashes out of nowhere.

Here are the dumps from Windows Debugger if it's any help:

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff800333e8f7e to fffff800333cdca0

STACK_TEXT:
fffff800`34f0ac88 fffff800`333e8f7e : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt!KeBugCheckEx
fffff800`34f0ac90 fffff800`332b9871 : 00000000`00000000 00000000`00007c8a fffff800`96a3d590 0000011a`1168fe51 : nt! ?? ::FNODOBFM::`string'+0xadbe
fffff800`34f0ad20 fffff800`332157b5 : fffff800`00400a02 00000000`00000000 fffff800`9667ca90 00000000`00006101 : nt!KeClockInterruptNotify+0x91
fffff800`34f0af40 fffff800`33354143 : fffff800`34f0af60 00000000`00000008 fffff800`34f0af50 00000000`00000010 : hal!HalPerformEndOfInterrupt+0x1a5
fffff800`34f0af70 fffff800`333cf12a : fffff800`33261800 00000000`0000e11c 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa3
fffff800`34f0afb0 fffff800`333cf50f : ffffe000`d8f7cd30 ffffe000`d8f7c000 00000000`0000e118 fffff800`96fe8f8a : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff800`34f026b0 fffff800`96fc0fcd : fffff800`97034e1c ffffe000`d40c2000 ffffe000`d40c2540 ffffe000`d8d30920 : nt!KiInterruptDispatchLBControl+0x11f
fffff800`34f02848 fffff800`97034e1c : ffffe000`d40c2000 ffffe000`d40c2540 ffffe000`d8d30920 00000000`0000e11c : nvlddmkm+0x198fcd
fffff800`34f02850 ffffe000`d40c2000 : ffffe000`d40c2540 ffffe000`d8d30920 00000000`0000e11c 00000000`00000020 : nvlddmkm+0x20ce1c
fffff800`34f02858 ffffe000`d40c2540 : ffffe000`d8d30920 00000000`0000e11c 00000000`00000020 fffff800`34f02880 : 0xffffe000`d40c2000
fffff800`34f02860 ffffe000`d8d30920 : 00000000`0000e11c 00000000`00000020 fffff800`34f02880 fffff800`00000000 : 0xffffe000`d40c2540
fffff800`34f02868 00000000`0000e11c : 00000000`00000020 fffff800`34f02880 fffff800`00000000 00000000`0000000b : 0xffffe000`d8d30920
fffff800`34f02870 00000000`00000020 : fffff800`34f02880 fffff800`00000000 00000000`0000000b 00000000`0000e11c : 0xe11c
fffff800`34f02878 fffff800`34f02880 : fffff800`00000000 00000000`0000000b 00000000`0000e11c 00000000`00000004 : 0x20
fffff800`34f02880 fffff800`00000000 : 00000000`0000000b 00000000`0000e11c 00000000`00000004 fffff800`97472e48 : 0xfffff800`34f02880
fffff800`34f02888 00000000`0000000b : 00000000`0000e11c 00000000`00000004 fffff800`97472e48 fffff800`970786f9 : 0xfffff800`00000000
fffff800`34f02890 00000000`0000e11c : 00000000`00000004 fffff800`97472e48 fffff800`970786f9 00000000`00000000 : 0xb
fffff800`34f02898 00000000`00000004 : fffff800`97472e48 fffff800`970786f9 00000000`00000000 00000000`00000000 : 0xe11c
fffff800`34f028a0 fffff800`97472e48 : fffff800`970786f9 00000000`00000000 00000000`00000000 00000000`00000009 : 0x4
fffff800`34f028a8 fffff800`970786f9 : 00000000`00000000 00000000`00000000 00000000`00000009 fffff800`34f029b0 : nvlddmkm+0x64ae48
fffff800`34f028b0 00000000`00000000 : 00000000`00000000 00000000`00000009 fffff800`34f029b0 ffffe000`d8cb0270 : nvlddmkm+0x2506f9


STACK_COMMAND: kb

FOLLOWUP_IP:
nvlddmkm+198fcd
fffff800`96fc0fcd ?? ???

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: nvlddmkm+198fcd

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 52487d54

FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm+198fcd

BUCKET_ID: 0x133_ISR_nvlddmkm+198fcd

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x133_isr_nvlddmkm+198fcd

FAILURE_ID_HASH: {d7ba0cee-950a-e9ac-eed9-0a7219aa6862}


New dumps, same thing with driver 347.

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe00085eb5060, Physical Device Object of the stack
Arg3: ffffd000716b2960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe00089b34010, The blocked IRP

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

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for pci.sys

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53d0f1d4

MODULE_NAME: pci

FAULTING_MODULE: fffff8008c000000 pci

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

DPC_STACK_BASE: FFFFD000716B9FB0

STACK_TEXT:
ffffd000`716b2928 fffff802`00821782 : 00000000`0000009f 00000000`00000003 ffffe000`85eb5060 ffffd000`716b2960 : nt!KeBugCheckEx
ffffd000`716b2930 fffff802`008216a2 : ffffe000`897e35a0 00000000`00000008 ffffe000`897e35d8 fffff802`006bd391 : nt!PopIrpWatchdogBugcheck+0xde
ffffd000`716b2990 fffff802`006bf2d8 : 00000000`00000000 ffffd000`716b2ae0 00000000`00000001 00000000`00000002 : nt!PopIrpWatchdog+0x32
ffffd000`716b29e0 fffff802`0076d7ea : ffffd000`71688180 ffffd000`71688180 ffffd000`716943c0 ffffe000`896ee080 : nt!KiRetireDpcList+0x4f8
ffffd000`716b2c60 00000000`00000000 : ffffd000`716b3000 ffffd000`716ad000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION: 6.3.9600.17238

FAILURE_BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys

BUCKET_ID: 0x9F_3_nvlddmkm_IMAGE_pci.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x9f_3_nvlddmkm_image_pci.sys

FAILURE_ID_HASH: {a47222af-fbac-bc49-47e0-2cf5d31cc673}

Followup: MachineOwner

Any clues?

Bios is Aptios 2.15...

Thanks!

 

What would happen if you use the original VBIOS?

 

Hi Kevin, if I were to use the original VBIOS the card wouldn't get recognized in Windows. It's a CLEVO card being used on a MSI GT70. Thanks!

 

Have you tried instaling with a modified inf file? Perhaps the issue is that the GPU is not being properly recognized as an nvidia GPU?

 

The drivers will install and recognize the card as a proper Nvidia 770M, the problem is it'll crash after a few seconds of booting up. The Nvidia control panel comes up, but if I choose the 3D settings (where the logo spins) It can't even render that, and it crashes. I've tried the stock drivers, a modified inf, and the latest drivers. All three do the same.

Weird thing is, it was working for a few HOURS a couple of days ago, then I had one crash, and it went downhill since then. I dunno if Windows itself is going into a state of decay due to so many crashes, deprecating the drivers installation or what. I'll try to reinstall Windows today to see if that helps, but the crashes say the only issue is with the drivers :S

 

Hi all,

I've flashed my bios to 51x, and EC to 24T.

Drivers install but crash as soon as I try to render anything.

Any clues?

I'm getting TDR errors too

Thanks!

[

 

Quick question... my vbios says MSI 1462... and my current BIOS version is 1762 51x... are those related? Should my vbios be 1762, or bios be 1462?

Thanks!

 

Your BIOS is 1762, which is MS-1762, that's the model number.
1462 is VENDOR ID. Like 8086 is Intel.