Random BSOD, nvlddmkm.sys identified by driver verifier

[ATAS]

Hi there, I've recently been getting random BSOD events, 8 so far, showing 5 different causes, (ndis.sys / ntoskrnl.exe (x3) / Rt64win7.sys / cdd.dll )
I've ran memtest on all 4 sticks of ram with no errors and ran the machine with driver verifier on.
this is when i got 2 BSOD within a few minutes of each other, both pointing to nvlddmkm.sys+9b0a1.
i have the latest drivers installed from nvidia for the graphics card (and had them installed at the time of the last two BSOD)

should i try an older video card driver?

any help would be greatly appreciated.

Edit: BSOD last night again, win32k.sys this time

View attachment 306899

 

[ATAS]

I've uninstalled all nvidia drivers, cleaned using the DDU tool and installed 334.89 driver. i'll see how it goes.

also noticed my processor has been running at 3.69GHz so ive disabled intel turbo boost to bring it back down to 2.79GHz. not sure if this will do anything at all but im willing to try it out.

 

[Arc]

Hi ATAS.

fffff880`0bc361d8  fffff880`0952e500Unable to load image \SystemRoot\system32\drivers\mfeavfk.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mfeavfk.sys
[COLOR=Red]*** ERROR: Module load completed but symbols could not be loaded for mfeavfk.sys[/COLOR]
 mfeavfk+0x13500

fffff880`0bc36038  fffff880`05859080Unable to load image \SystemRoot\system32\DRIVERS\mfencbdc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mfencbdc.sys
[COLOR=Red]*** ERROR: Module load completed but symbols could not be loaded for mfencbdc.sys[/COLOR]
 mfencbdc+0x59080

McAfee is vicious. It is most frequent BSOD causer. Uninstall McAfee Using McAfee Removal Tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one, for a safety reason only; as the installed antivirus is failing.

Let us know for any further BSODs.

 

[ATAS]

Thanks for the reply Arc. I've uninstalled McAfee as you said and using microsoft security essentials instead but im still getting BSODs

ive attached a newer sf diagnostic
View attachment 307046

 

[Arc]

Upload the list of all the third party drivers Using NirSoft DriverView :

• Download and execute Driverview
• View > Hide Microsoft Drivers
• Edit > Select all
• File > Save Selected Items
• In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
• Zip the .txt file and upload it.

usbehci
​

 

[ATAS]

Driverview txt file.

View attachment 307181

 

[Arc]

Uninstall Intel Extreme Tuning Utility. But before uninstalling it, run it and set everything to default.

Uninstall Virtual Clone Drive.

Update Intel USB3 drivers for Clevo p170sm .... I have no idea about the download location for the model unfortunately, so cannot guide you in it.

And, Disable USB Selective Suspense too.
USB Selective Suspend - Turn On or Off

Let us know the results.

 

[ATAS]

thanks again for the reply arc, regarding intel extreme tuning utility. everything is on default except Intel Turbo Boost which i disabled. would it be best to leave this disabled or put it back on (default was set to 'on' but my processor seemed to run at 3.69GHz all the time instead of 2.79 as standard?

 

[Arc]

Hi ATAS.

Apparently your issue is not caused for overclocking (it will remain stable over a few more months, IMHO). So it is not a must to pay the utmost attention on it right now. Intel Extreme Tuning is contributing to the issue otherwise.

You can disable those overclocks anytime by booting into the BIOS. And that is the right way to do it, other than using any program.

 

[ATAS]

i haven't had a chance to run the laptop properly yet but it did go a few hours the other day without crashing. ill run it over the next few days. early signs are looking good.

 

[ATAS]

scratch that. just had another damn BSOD. (INTERRUPT_EXCEPTION_NOT_HANDLED ntoskrnl.exe+75bc0) I can see my foot going through this laptop.

Would reinstalling windows be a viable option?

 

[Arc]

INTERRUPT_EXCEPTION_NOT_HANDLED. Stop 0x3D. Mostly it is not very frequent, and usually caused by verifier.exe running in the background.

Have you enabled Driver Verifier anyhow? If so, disable it.

If you haven't enabled driver verifier at all, it is some driver failing to act accordingly, which is not disclosed (ntoskrnl.exe, as you posted, is not any reason behind a BSOD; but it is actually the kernel on which it crashes. So there is no need to debug based on it). Here a clean reinstall would be a worthy shot.

 

[ATAS]

I've done a fresh install of windows. It ran fine for 2 days then BSOD. All drivers were installed on day 1, only some SSD tweeks were made on day 2. nothing else has been installed except firefox.

I've included a new SF Diagnostic zip.

View attachment 309301

Also Driverview file

View attachment 309309

Thanks

 

[Arc]

Two drivers are failing here.

HD graphics driver.

fffff880`0a75d378  fffff880`0584dc00Unable to load image igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
[COLOR=Red]*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys[/COLOR]
 igdkmd64+0x240c00

Try to install Intel® Iris™ and HD Graphics Driver for Windows* 7?

Killer Wireless-N 1103 Network Adapter driver.

fffff880`0a75d438  fffff880`066b73caUnable to load image athrx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrx.sys
[COLOR=Red]*** ERROR: Module load completed but symbols could not be loaded for athrx.sys[/COLOR]
 athrx+0x1f63ca

Update it from Driver Downloads | Qualcomm Atheros, Inc.

Also, as it shows some memory error, est your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.
___________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa811b238478, 2, 1, fffff80002c93f77}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa811b238478, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002c93f77, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec9100
GetUlongFromAddress: unable to read from fffff80002ec91c0
 fffffa811b238478 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeWaitForMultipleObjects+f7
fffff800`02c93f77 64887748        mov     byte ptr fs:[rdi+48h],dh

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xA

PROCESS_NAME:  FlashPlayerPlu

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  fffff8800a75cf00 -- (.trap 0xfffff8800a75cf00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c93f77 rsp=fffff8800a75d090 rbp=0000000000000002
 r8=0000000000000002  r9=0000000000000006 r10=0000000000000002
r11=fffffffffffffd80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KeWaitForMultipleObjects+0xf7:
fffff800`02c93f77 64887748        mov     byte ptr fs:[rdi+48h],dh fs:00000000`00000048=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c91169 to fffff80002c91bc0

STACK_TEXT:  
fffff880`0a75cdb8 fffff800`02c91169 : 00000000`0000000a fffffa81`1b238478 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0a75cdc0 fffff800`02c8fde0 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`1b2c2538 : nt!KiBugCheckDispatch+0x69
fffff880`0a75cf00 fffff800`02c93f77 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0a75d090 fffff800`02f87f6f : fffff880`00000002 fffff880`0a75d3e0 00000000`00000001 00000000`00000006 : nt!KeWaitForMultipleObjects+0xf7
fffff880`0a75d350 fffff800`02fb566d : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000000 : nt!ObpWaitForMultipleObjects+0x294
fffff880`0a75d820 fffff800`02c90e53 : 00000000`00000000 fffff800`00000002 00000000`00000000 00000000`00200293 : nt!NtWaitForMultipleObjects32+0xec
fffff880`0a75da70 00000000`74092e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`08c3ed58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74092e09


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002c93f77 - nt!KeWaitForMultipleObjects+f7
    [ 44:64 ]
1 error : !nt (fffff80002c93f77)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_memory_corruption_one_bit

FAILURE_ID_HASH:  {2dbb898e-c425-bad1-90fe-71c78117521f}

Followup: memory_corruption
---------

 

[ATAS]

Updated the intel hd graphics driver. The current Qualcomm wireless driver is the most recent one available, should I try an older driver?

Also ran memtest for 9 passes with zero errors.

Thanks

 

[Arc]

No, dont install an earlier driver right now. Wait and see how it goes. If needed, we will debug the issue again.

 

[ATAS]

Since updating the intel graphics driver its ran fine up until 2 days ago, then 3 blue screens within the space of 2 hours. I've included the latest SF zip file.

View attachment 313258


thanks again for taking the time to help out, its greatly appreciated.


edit.

also just had BSOD (DRIVER_IRQL_NOT_LESS_OR_EQUAL) 5 misn ago. dump file is attached below.

View attachment 313262

I'll enable driver verifier and upload the dump file once it crashes.

 

[Arc]

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.

 

[ATAS]

thanks for the reply Arc.

I'll test again with memtest. I ran it when i updated the graphics driver for 9 passes which took about 37 hours and got no errors, I'll run it again for more than 9 passes this time.

in the meantime, if its any use, another BSOD occurred while driver verifier was on, i have posted the dump file below.

View attachment 313306

I'll report back with any findings from memtest in a few days.

 

[Arc]

in the meantime, if its any use, another BSOD occurred while driver verifier was on, i have posted the dump file below.

View attachment 313306

The uploaded BSOD is not Driver Verifier enabled.

But it somehow points to failing card reader driver. Update it from Realtek

BugCheck 1000007E, {ffffffffc0000005, fffff88000f3e64b, fffff88007733818, fffff88007733070}

*** WARNING: Unable to verify timestamp for RtsBaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for RtsBaStor.sys
Probably caused by : pci.sys ( pci!PciExternalReadDeviceConfig+f3 )

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