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: BSOD Random 0x000000BE nvlddmkm.sys

07 Sep 2012   #1

Windows 7 64bit home premium
 
 
BSOD Random 0x000000BE nvlddmkm.sys

I am randomly getting a BSOD. I have found no pattern to when I get it. (Gotten it gaming, browsing internet, and so on.) Browsed internet and the forums here and have not found anything useful looking. Attached is the .zip from the SF diagnostic tool.

Thanks in advanced for helping.

My System SpecsSystem Spec
.

07 Sep 2012   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Welcome

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Yusra\Downloads\StarrBurst\090712-29312-01.dmp] 
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols 
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`03200000 PsLoadedModuleList = 0xfffff800`03444670
Debug session time: Sat Sep  8 07:23:15.837 2012 (UTC + 6:00)
System Uptime: 1 days 12:30:52.992
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information. 

BugCheck BE,  {fffff8801361d630, 80000004108f7121, fffff8800af93410, b}

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
Probably caused by : nvlddmkm.sys ( nvlddmkm+e1a37 )

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

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

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be) 
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff8801361d630, Virtual address for the attempted write.
Arg2: 80000004108f7121, PTE contents.
Arg3: fffff8800af93410, (reserved)
Arg4: 000000000000000b, (reserved)

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


CUSTOMER_CRASH_COUNT:  1 

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT 

BUGCHECK_STR:  0xBE 

PROCESS_NAME:  java.exe 

CURRENT_IRQL:  0 

TRAP_FRAME:  fffff8800af93410 -- (.trap 0xfffff8800af93410) 
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8801361d5e0 rbx=0000000000000000 rcx=fffffa8010d734c0
rdx=fffffa800d60c010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880130eda37 rsp=fffff8800af935a0 rbp=fffff8800af93ab0
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000001
r11=fffff8801361d5e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nvlddmkm+0xe1a37:
fffff880`130eda37 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003227122 to fffff8000327f1c0 

STACK_TEXT:   
fffff880`0af932a8 fffff800`03227122 : 00000000`000000be fffff880`1361d630 80000004`108f7121 fffff880`0af93410 : nt!KeBugCheckEx
fffff880`0af932b0 fffff800`0327d2ee : 00000000`00000001 fffff880`1361d630 fffffa80`0cd8b300 00000000`c00000e8 : nt! ?? ::FNODOBFM::`string'+0x4522e
fffff880`0af93410 fffff880`130eda37 : 00000000`c00000e8 fffff880`0af935e0 fffffa80`0e01b010 fffffa80`0e52b5c0 : nt!KiPageFault+0x16e
fffff880`0af935a0 00000000`c00000e8 : fffff880`0af935e0 fffffa80`0e01b010 fffffa80`0e52b5c0 00000000`00000000 : nvlddmkm+0xe1a37
fffff880`0af935a8 fffff880`0af935e0 : fffffa80`0e01b010 fffffa80`0e52b5c0 00000000`00000000 fffffa80`0e50a000 : 0xc00000e8
fffff880`0af935b0 fffffa80`0e01b010 : fffffa80`0e52b5c0 00000000`00000000 fffffa80`0e50a000 fffff880`0af93600 : 0xfffff880`0af935e0
fffff880`0af935b8 fffffa80`0e52b5c0 : 00000000`00000000 fffffa80`0e50a000 fffff880`0af93600 fffff880`131a766a : 0xfffffa80`0e01b010
fffff880`0af935c0 00000000`00000000 : fffffa80`0e50a000 fffff880`0af93600 fffff880`131a766a fffffa80`00000000 : 0xfffffa80`0e52b5c0


STACK_COMMAND:  kb 

FOLLOWUP_IP:  
nvlddmkm+e1a37
fffff880`130eda37 ??              ???

SYMBOL_STACK_INDEX:  3 

SYMBOL_NAME:  nvlddmkm+e1a37 

FOLLOWUP_NAME:  MachineOwner 

MODULE_NAME: nvlddmkm 

IMAGE_NAME:  nvlddmkm.sys 

DEBUG_FLR_IMAGE_TIMESTAMP:  4fece178 

FAILURE_BUCKET_ID:   X64_0xBE_nvlddmkm+e1a37

BUCKET_ID:   X64_0xBE_nvlddmkm+e1a37

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

5: kd> lmvm nvlddmkm 
start             end                 module name
fffff880`1300c000 fffff880`13ced000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Jun 29 04:58:00 2012 (4FECE178)
    CheckSum:         00CC42A5
    ImageSize:        00CE1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
BSOD Index
STOP 0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY Usual causes: Device driver, Memory

Suggestions:
  • Download and install Driver_Sweeper
  • Reboot the computer to Advanced Boot Options, Safe Mode.
  • Click on the start and search for Driver Fusion
  • Uninstall the drivers of your nVidia display driver
Boot normally and go to Drivers - Download NVIDIA Drivers | Using option 2 from this link Drivers - Download NVIDIA Drivers | nvlddmkm.sys

The next thing to do is test your memory - following this tutorial preferably overnight for 8 passes at least:
RAM - Test with Memtest86+

Post back results
My System SpecsSystem Spec
07 Sep 2012   #3

Windows 7 64bit home premium
 
 

Re: KoolKat

Thanks for the quick reply. Just ran driver sweeper to remove nvidia driver, and I am installing the new driver now. Overnight I will run the Mem check and post results tomorrow after work.

Thanks.
My System SpecsSystem Spec
.


07 Sep 2012   #4

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

You're welcome
Keep us posted
My System SpecsSystem Spec
08 Sep 2012   #5

Windows 7 64bit home premium
 
 

As I said I did the graphics driver fix. I ran the Memtest86+ v4.20. I let it run 18 hr and 35 mins. it did over 5 passes with no error. If you would like me to upload a pic of results, let me know. Since the BSODs are few and far between, I will post down the road if anything else comes up.

Thanks
StarrBurst
My System SpecsSystem Spec
08 Sep 2012   #6

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Please upload the latest dumps
My System SpecsSystem Spec
08 Sep 2012   #7

Windows 7 64bit home premium
 
 

Upload again even though I haven't crashed yet?
My System SpecsSystem Spec
08 Sep 2012   #8

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Not now..just when the occur again
My System SpecsSystem Spec
11 Sep 2012   #9

Windows 7 64bit home premium
 
 

Crashed again. Had Arma 2 open, a java app, Chrome, and ventrilo.
Attached is Zip from SF Diag.
My System SpecsSystem Spec
11 Sep 2012   #10

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Caused by the Direct X

Try this: Run DirectX Diagnostic Tool

DirectX Diagnostic Tool helps you troubleshoot issues with the DirectX suite of multimedia technologies that come with Windows. If you're having trouble getting game animation or a movie to run properly, you should run DirectX Diagnostic Tool to try to find the source of the problem.
To run DirectX Diagnostic Tool

  • Open DirectX Diagnostic Tool by clicking the Start button , typing dxdiag in the Search box, and then pressing ENTER.


Using DirectX Diagnostic Tool to diagnose problems

Here are some of the things you should be looking for:
  • Lack of hardware acceleration. Some programs run very slowly or not at all unless Microsoft DirectDraw or Direct3D hardware acceleration is available. Click the Display tab, and then under DirectX Features, check to see whether DirectDraw, Direct3D, or AGP Texture acceleration is marked Not Available. If so, you might consider upgrading your hardware. You might also need to turn on graphics acceleration.
    To turn on graphics acceleration

    1. Open Display Settings by clicking the Start button , clicking Control Panel, clicking Appearance and Personalization, clicking Personalization, and then clicking Display Settings.
    2. Click Display Settings, and then click Advanced Settings.
    3. Click the Troubleshoot tab, and then click Change Settings. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
    4. Move the Hardware Acceleration slider to Full.

  • Devices are not connected. If a joystick or other input device fails to respond, it may not be properly set up. Make sure the device is present on the Input tab of DirectX Diagnostic Tool. If not, reinstall the game controller or input device by unplugging it and then plugging it back in.
  • Unsigned drivers are present. Microsoft has not tested unsigned drivers for full compatibility with the latest version of DirectX. We recommend that you use drivers that are digitally signed by Microsoft Windows Hardware Quality Labs (WHQL).

Also, if you have another graphics card or a built in video slot try using that and see if you're getting crashes
My System SpecsSystem Spec
Reply

 BSOD Random 0x000000BE nvlddmkm.sys




Thread Tools



Similar help and support threads for2: BSOD Random 0x000000BE nvlddmkm.sys
Thread Forum
Random BSODs: ntoskrnl, dxgkrnl, dxgmms1, nvlddmkm, BCCode 116 BSOD Help and Support
BSOD ocurring at random infrequent times (ntoskml, vsdatant, nvlddmkm) BSOD Help and Support
BSOD Watching youtube video, error 0x000000BE BSOD Help and Support
Random nvlddmkm.sys bluescreens BSOD Help and Support
Solved BSOD, RAM and Driver Problems of the 0x000000be Variety BSOD Help and Support
BSOD during general use, errors 0x0000003B and 0x000000BE BSOD Help and Support
Random BSOD/reboot on ASUS laptop - nvlddmkm.sys error 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 05:22 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33