Solved BSOD Random 0x000000BE nvlddmkm.sys

[StarrBurst]

Those BIOS Voltages: (see attachment)

NOTE: Originally the highlighted red setting (System Voltage Control) was set to AUTO. I changed it to Manual so it would display the following voltages that you see in the screen shot. I exited without saving, so BIOS is still set to AUTO.

 

[Dave76]

Those CPU core temps are high for an AMD, they usually run very cool.
Are you using the stock AMD CPU cooler?
You need to remove the CPU cooler, clean the old thermal paste off with isopropyl alcohol, re-apply new thermal paste and install the CPU cooler.

Post the snips of each RAM slot, if the RAM is different, from the CPUZ SPD tab. This is important information.

Your current BIOS version should be ok, the F6 version description states 'Fix Cool'n'Quiet compatibility', if you're having any issues with this you might consider updating.

From your motherboard manual, linked above.
Page 43

********System Voltage Optimized********
System Voltage Control

Determines whether to manually set the system voltages. Auto lets the BIOS automatically set the
system voltages as required. Manual allows all voltage control items below to be configurable. (Default:Manual)

Set this to Manual, so you can get the voltage readings below.
When finished getting all of the readings, Exit BIOS - DO NOT Save.

Page 44

CPU Voltage Control
Allows you to set the CPU voltage. Auto sets the CPU voltage as required. The adjustable range is dependent
on the CPU being installed. (Default: Normal)
Note: Increasing CPU voltage may result in damage to your CPU or reduce the useful life of the CPU.

This is the CPU voltage.

Page 43

DRAM Voltage Control
Allows you to set memory voltage.
Normal Supplies the memory voltage as required. (Default)
1.210V ~ 2.410V The adjustable range is from 1.210V to 2.410V.
Note: Increasing memory voltage may result in damage to the memory or reduce the useful life of the memory.

This is the RAM voltage.

Page 44

CPU NB VID Control
Allows you to set the CPU North Bridge VID voltage. Auto sets the CPU North Bridge VID voltage as
required. The adjustable range is dependent on the CPU being installed. (Default: Normal)
Note: Increasing CPU voltage may result in damage to your CPU or reduce the useful life of the CPU.

This is the CPU Integrated Memory Controller voltage, this controller runs the RAM.

Post these voltages in your next reply.

 

[StarrBurst]

I am using stock cooler. I did not put any extra paste than what already came on the fan. . If I am out of paste, I will pick some up on the way home tomorrow.

Thanks.

 

[Dave76]

See my post above, I have added information requests.

Also if you get a chance, post the CPU core idle temps.

 

[StarrBurst]

Those CPU core temps are high for an AMD, they usually run very cool.
Are you using the stock AMD CPU cooler?

I am using stock cooler. I did not put any extra paste than what already came on the fan. . If I am out of paste, I will pick some up on the way home tomorrow.

Thanks.

Also about the voltages see post 41. I did exactly what you asked in post 42. I set System Voltage Control to [Manual] and posted a pic of those voltages. I then exited without saving. (If this is not what you are wanting, let me know)

Thermal paste. I just replaced the thermal paste with OCZ Freeze Extreme. After 30 mins Prime95 it never passed 50 deg C. (previously by that time it had hit 60. Will run a 2-3 hour test tomorrow.

After letting the CPU idle for the last 10 mins, it is sitting around 25 deg C.

Only posted 1 snip of RAM. I ordered a 4 pack of identical RAM. All 4 tabs show the exact same information except slot number. It shows the correct type of ram.

Any other information, just let me know.

 

[Dave76]

Need the CPU NB VID Control, it's not shown in post #41.
Select it and you should see some options and hopefully a voltage.

Good news on the thermal paste, that's much better temps.

When you post the CPU NB VID Control voltage, I can recommend some RAM setting adjustments.

As always, if you get any more crashes post the full Crash Report.

 

[StarrBurst]

Finally figured out if I press + or - it will cycle between voltages for the CPU NB VID. (if I press ENTER it just gives me a list to choose from.) The voltage of the CPU NB VID is 1.15v it would seem.

 

[Dave76]

Set DRAM to 1.550v and CPU NB VID to 1.250v.

These are still conservative settings for 16GB RAM, If it's still unstable bump the CPU NB VID to 1.30v.

Let us know if you get any more crashes, upload the crash reports if you do.

 

[StarrBurst]

BSOD again. Like usual thanks for your continued help, and let me know if you have any questions.

 

[Dave76]

Did you change the Set DRAM to 1.550v and CPU NB VID to 1.250v?
Did you bump the CPU NB VID to 1.30v before this crash?

Run memtest86+ again for a full 7 passes, this will take a while but, is necessary.

The last two crashes, both are inconclusive with little usable information.

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION 
Usual causes:  System service, Device driver, graphics driver, ?memory
---------------------------------------------------------------------------------------------------------
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

From your App Event Logs:

Event[43489]:
  Log Name: Application
  Source: SideBySide
  Date: 2012-09-15T00:52:46.000
  Event ID: 63
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Zach-PC
  Description: 
Activation context generation failed for "c:\program files (x86)\spybot - search & destroy\DelZip179.dll".Error in manifest or policy file "c:\program files (x86)\spybot - search & destroy\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.

Event[43607]:
  Log Name: Application
  Source: SideBySide
  Date: 2012-09-17T02:47:27.000
  Event ID: 63
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Zach-PC
  Description: 
Activation context generation failed for "c:\program files (x86)\spybot - search & destroy\DelZip179.dll".Error in manifest or policy file "c:\program files (x86)\spybot - search & destroy\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.

Un-install Spybot, D/L and install new version if you want.

Event[43603]:
  Log Name: Application
  Source: Application Error
  Date: 2012-09-16T16:15:42.000
  Event ID: 1000
  Task: Application Crashing Events
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Zach-PC
  Description: 
Faulting application name: arma2oa.exe, version: 1.62.96.751, time stamp: 0x5049fafd
Faulting module name: arma2oa.exe, version: 1.62.96.751, time stamp: 0x5049fafd
Exception code: 0xc0000005
Fault offset: 0x00052fc4
Faulting process id: 0xa2c
Faulting application start time: 0x01cd9449e8db9603
Faulting application path: C:\program files (x86)\steam\steamapps\common\arma 2 operation arrowhead\Expansion\beta\arma2oa.exe
Faulting module path: C:\program files (x86)\steam\steamapps\common\arma 2 operation arrowhead\Expansion\beta\arma2oa.exe
Report Id: abc7cb03-0043-11e2-82b7-1c6f653df226

Several of your Steam games are crashing.

Event[44088]:
  Log Name: Application
  Source: Bonjour Service
  Date: 2012-09-20T21:07:56.000
  Event ID: 100
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Zach-PC
  Description: 
ERROR: handle_resolve_request bad interfaceIndex 1

Event[44110]:
  Log Name: Application
  Source: Bonjour Service
  Date: 2012-09-20T21:07:56.000
  Event ID: 100
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Zach-PC
  Description: 
ERROR: handle_resolve_request bad interfaceIndex 24

24 error messages for this service.
Bonjour Service is part of the iphone applications, update the programs and/or uninstall for testing purposes.

 

[StarrBurst]

I had forgot to change the voltages for the BSOD's in #49. I set the voltages as asked (shown in attached picture 1.jpg) The computer started and after the BIOS screen it failed to load windows. I tried a second time, and it blue screened (picture 2.jpg). So I set CPU NB VID to 1.30v since it was unstable. Windows loads fine and it blue screens in a matter of minutes, so I set all voltages back to default, and attached another .zip.

Also uninstalled Spybot and Bonjour. Had steam check for any problems with arma2oa (replaced 1 file).

thanks for all the help.

 

[Dave76]

From the first snip you lowered the 'CPU Voltage Control' to 1.250v, this is why your system crashed.
Set it back to 'Normal'.
You set the 'CPU NB VID' to 1.1250v, should have been 1.250v.
You lowered the CPU voltage and the CPU/NB Voltage (CPU Integrated Memory Controller), which caused your system to crash.

I asked you to bump the 'CPU NB VID' to 1.250v, Not the 'CPU Voltage Control'.
If it's unstable then bump the 'CPU NB VID' to 1.30v.

Carefully follow these step:
After you set the 'CPU Voltage Control' back to 'Normal' change the following settings.
'DRAM Voltage Control' to 1.550v
'CPU NB VID' to 1.300v

Double check that you set these voltage controls correctly, lowering them will cause your system to crash, raising them too high can damage system components, CPU, RAM, and possibly the motherboard.

Your last crash from your zip file.

STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR
Usual causes:  Hardware, Incompatibility, May be driver corruption
Probably caused by : AuthenticAMD
PROCESS_NAME:  chrome.exe
IMAGE_NAME:  AuthenticAMD
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

This crash is blaming your CPU.
If you lowered the 'CPU Voltage Control' to 1.250v, this is why you got this BSoD stop code.

Let me know if you have any questions.

 

[StarrBurst]

Hello again, I had my first blue screen since I last posted. Like usual the SF_diagnostic is attached. (it is the one that happened about 4:15 PM ish.

Thanks

StarrBurst

 

[Dave76]

Can you confirm the voltage settings that are listed above?
'DRAM Voltage Control' to 1.550v
'CPU NB VID' to 1.300v

Did you re-install any of the programs that were requested to be un-installed?

Your last crash:

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,
Probably caused by : cdd.dll ( cdd!CDDPDEV::FlushGdiOutput+4b ) - Canonical Display Driver
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034b8100
GetUlongFromAddress: unable to read from fffff800034b81c0
 ffffffffffffffff 
FAILURE_BUCKET_ID:  X64_0x7E_cdd!CDDPDEV::FlushGdiOutput+4b

Looks like a RAM error again.

If your DRAM voltage is at 1.550v now, then increase it to:
'DRAM Voltage Control' to 1.600v
Leave the 'CPU NB VID' at 1.300v

There is an indication that Steam and various games are causing the errors and likely the crashes.
Bump the DRAM voltage, and see if that helps.

 

[StarrBurst]

I had the voltage settings set as asked when it crashed yesterday:
'DRAM Voltage Control' to 1.550v
'CPU NB VID' to 1.300v

Now as you asked I set the DRAM Voltage Control to 1.610V (choices were 1.590 and 1.610, but no option for 1.600)

I did not re-install any of the programs. All steam games are kept up to date, and I had fixed one of the games that you mentioned had a problem.

Thanks

Starrburst

 

[Dave76]

That voltage is ok, AMD systems can take high voltages much better than Intel system.

Let us know if it is stable.

 

[StarrBurst]

Blue screen of death while playing Garry's Mod.

 

[Dave76]

It's blaming the graphics driver.
Update the graphics driver, if it still crashes then install an older driver.
There is a possibility that this is caused by the graphics card, load new/old drivers to see if it stops.

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
Probably caused by : nvlddmkm.sys ( nvlddmkm+211cc6 )
IMAGE_NAME:  nvlddmkm.sys
FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+211cc6
4: kd> lmvm nvlddmkm
start             end                 module name
fffff880`13014000 fffff880`13dd6000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Tue May 15 15:35:36 2012 (4FB20748)
    CheckSum:         00DA5E91
    ImageSize:        00DC2000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[StarrBurst]

Updated driver from 301.42 to version 306.97

 

[Dave76]

Hope it's stable now.

Let us know if you get any more crashes.