Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD, nvlddmkm.sys identified by driver verifier

25 Feb 2014   #11
ATAS

Windows 7 Ultimate x64
 
 

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?


My System SpecsSystem Spec
.
26 Feb 2014   #12
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.
My System SpecsSystem Spec
06 Mar 2014   #13
ATAS

Windows 7 Ultimate x64
 
 

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.

Attachment 309301

Also Driverview file

Attachment 309309

Thanks
My System SpecsSystem Spec
.

07 Mar 2014   #14
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Two drivers are failing here.

HD graphics driver.
Code:
fffff880`0a75d378  fffff880`0584dc00Unable to load image igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
 igdkmd64+0x240c00
Try to install Intel® Iris™ and HD Graphics Driver for Windows* 7?

Killer Wireless-N 1103 Network Adapter driver.
Code:
fffff880`0a75d438  fffff880`066b73caUnable to load image athrx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
 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.
___________________________________________
Code:
*******************************************************************************
*                                                                             *
*                        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
---------
My System SpecsSystem Spec
12 Mar 2014   #15
ATAS

Windows 7 Ultimate x64
 
 

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
My System SpecsSystem Spec
12 Mar 2014   #16
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

No, dont install an earlier driver right now. Wait and see how it goes. If needed, we will debug the issue again.
My System SpecsSystem Spec
09 Apr 2014   #17
ATAS

Windows 7 Ultimate x64
 
 

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.

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.

Attachment 313262

I'll enable driver verifier and upload the dump file once it crashes.
My System SpecsSystem Spec
09 Apr 2014   #18
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.
My System SpecsSystem Spec
09 Apr 2014   #19
ATAS

Windows 7 Ultimate x64
 
 

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.

Attachment 313306

I'll report back with any findings from memtest in a few days.
My System SpecsSystem Spec
10 Apr 2014   #20
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Quote   Quote: Originally Posted by ATAS View Post
in the meantime, if its any use, another BSOD occurred while driver verifier was on, i have posted the dump file below.

Attachment 313306
The uploaded BSOD is not Driver Verifier enabled.

But it somehow points to failing card reader driver. Update it from Realtek
Code:
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
---------
My System SpecsSystem Spec
Reply

 Random BSOD, nvlddmkm.sys identified by driver verifier




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Multiple BSOD. Driver Verifier Driver caught a driver corrupting
I have had BSOD for a while and being super busy I did not have time to look at it and get it fixed. Well Being a computer guy I assumed I could fix it myself. But with tons of research and trying to use every guide I can find I decided to try here(probably should have came here first). Today I...
BSOD Help and Support
BSOD from nvlddmkm (running verifier) when trying to open GeForce Exp
Hi all, Sorry in advance for the long and rambling post, but I've tried a few different sets of settings with driver verifier in an effort to pinpoint the problem, but I'm not at all experienced in the nitty gritty aspects of debugging BSODs. I'll try to explain the origin of all of my earlier...
BSOD Help and Support
Random BSOD, ran driver verifier now got 0x000000c9 BSOD
Hi All Have been following a number of threads to identify my issue. I can only assume that a driver is at fault as when i run verifier i have to start in safe mode. Attached is my mini dump, can anyone help me identify where the issue is? Thanks a lot Lordmwa EDIT - Added the full lot...
BSOD Help and Support
BSOD after driver verifier
Plz check, thanks for more infos.... It's ntoskrnl.exe Searching forum and no proper solution. Startup repair doesn't help - can't fix the problem sfc /scann... no errors chkdsk /r ... no errors
BSOD Help and Support
Random BSOD's + Driver verifier startup crash
Hello, I have recently build build my own pc. This pc has never worked stable, i've been experiencing random bsod's. Sometimes they come 20 in a row and the system is stable for only a few minutes. Sometimes, usually when I tweaked a little with the system, like increased the voltage over the...
BSOD Help and Support
Driver verifier BSOD
System will randomly lockup. It is very sporadic and I have tested vga, ram, and cpu using prime95, memtest as well as memtest86, furmark used for vga. 7hrs and 7 full runs of memtest 86, 0 errors. I feel hardware is solid. Upon enabling driver verifier the system bluescreens before even...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 21:32.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App