Solved Event ID 13 nvlddmkm errors, game crashed with GeForce GT 610

[Banqu0]

I just purchased a barebones machine that came with a BIOSTAR A880G+ Mobo and AMD Athalon II X3 460 CPU. I then bought a 530W PSU and an Geforce GT 610 (2GB version) and a 4GB stick of RAM. Got home, installed windows 7 x86, updated and began installing games.


First off was F.E.A.R which ran splendidly for about 20 minutes. Then I started noticing tearing in the graphics and some FPS lag. This lasted for about 15 seconds and the screen turned black and the computer rebooted. A similar occurrence happened with BF2. Minecraft froze repeatedly in worlds with complex builds but did not crash. I had one instance of VLC causing the computer to crash when attempting to play a 720p resolution video.



A google search suggest increasing TDR delay, so I increased it to 8 seconds. This stopped the computer from rebooting but the games still crashed. The Nvidia graphics setting are all set to "performance". 3D vision, network service, and streamer services have all been disabled. Doing those things has helped crashes to a degree but it's still rather random. I can play for 10 minutes or 3 hours without a crash. I don't know very much about adjusting clock speeds or voltages with graphics cards so I've been reluctant to tinker around with that but I'm wondering if the graphics card is demanding more juice than my mobo is providing.



Here are the last errors from the event viewer:

\Device\Video5
Graphics Exception: MISSING_MACRO_DATA

\Device\Video5
Graphics Exception: ESR 0x404490=0x80000001

\Device\Video5
Variable String to Large

\Device\Video5
Graphics MME Exception Type: MAX_INSTR_LIMIT

\Device\Video5
Graphics Exception: Shader Program Header 11 Error

\Device\Video5
Graphics Exception: Shader Program Header 18 Error

\Device\Video5
Graphics Exception: ESR 0x405840=0xa2040800

Not sure if this is a driver issue, a hardware issue or a configuration issue, though it seems these types of problems are relatively common with nvidia cards. Too bad there's no single known fix

. Some of the nvlddmkm errors were nowhere on google (ie MISSING_MACRO_DATA), which is...discouraging. If anyone can point me in the right direction and help me to avoid ulcers that would be great.

Thanks in advance

SPECS:

Motherboard: BIOSTAR A880G+
BIOS VERSION: American Megatrends 080016 (09/21/11)
CPU:AMD Athalon II X3 460 3400MHZ
OS: Windows 7 Ultimate x86
RAM: 4GB
GPU GeFOrce GT 610, 2048MB RAM, Driver: 347.52

 

[Golden]

Additional information is required.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

 

[Banqu0]

Thank you for the reply. I have since downgraded the graphics drivers to 312.44. I was sure to install only the graphics driver and the physx driver. This is the only change I have made since my original post

 

[Golden]

Does theis ZIP file contain any .dmp files from after you made the change?

If not, then please do the following so we get the latest .dmp file:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

 

[Banqu0]

The dump files in the .zip were created after the driver downgrade.

 

[Golden]

OK. Thats good enough. Let me have a look.

 

[Banqu0]

Thank you

 

[Golden]

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 865ae024, 0, 0}

Probably caused by : AuthenticAMD

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

0x124's are typically related to a hardware issue and can only be isolated by stress testing the major components.

If overclocking, reset all overclocks back to their default settings and then follow these:

RAM - run for a minimum of 8 consecutive passes
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

CPU - run the HIGH test
http://www.sevenforums.com/tutorials/220743-cpu-stress-test-using-intelburntest.html

Video - run the FURMARK test for 20mins
http://www.sevenforums.com/tutorials/330579-graphics-card-problems-diagnose.html
http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

Storage - run the SHORT test using the DOS version
http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

 

[Banqu0]

Thank you. I will run these tests tomorrow morning and get back to you (It's 12.08 am here)

 

[Banqu0]

Sorry for the late response. Here is an update: CPU stress test caused an "a hyper transport sync flood error occurred on last boot" error when the computer rebooted. the is has occurred before but I neglected to mention that. memtest was ok.

 

[Golden]

Here is an update: CPU stress test caused an "a hyper transport sync flood error occurred on last boot"

Was that with IntelBurnTest?

 

[Banqu0]

No, this was playing a game of minecraft. Oddly enough i tried to cause a crash by playing MC with the graphics set insanely high. this caused a memory error, but no crash. A bout 5 minutes ago the computer crashed after loading minecraft. There was the telltale flicker and then a BSOD Bluescreen viewer pointed to 2 drivers as the culprit:

hal.dll hal.dll+5ba9 0x82e1e000 0x82e55000 0x00037000 0x4ce788d2 11/20/2010 1:37:38 AM Microsoft® Windows® Operating System Hardware Abstraction Layer DLL 6.1.7601.17514 (win7sp1_rtm.101119-1850) Microsoft Corporation C:\Windows\system32\hal.dll

ntoskrnl.exe ntoskrnl.exe+d18ad 0x82a0b000 0x82e1e000 0x00413000 0x5147d331 3/18/2013 7:53:37 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.18113 (win7sp1_gdr.130318-1533) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe

 

[Banqu0]

I have continued to search Google for some answers. The common factor present in all of these errors seems to be CPU settings. Though i am not sure what the correct ones should be and I am unfamiliar with over/under clocking. Should I post BIOS settings?

 

[Banqu0]

THe more information, the better, I suppose...

AMD Athlon II X3 460

SPEED: 3400MHz
NB CLOCK: 2000MHz
ncHT SPEED: 2000MMHz
WIDTHI/O: 16/16 BIT
uCODE PATCH LEVEL: 0x10000C8

ADVANCED/CPU Configuration Settings:
-Secure Virtual Machine [ENABLED]
-Power Now [ENABLED]
-ACPI SRAT TABLE [ENABLED]
-Probe Filter [AUTO]
-ADVANCED CLOCK CALIBRATION [DISABLED]
-C1E SUPPORT [DISABLED]
-CORE LEVELING [AUTO]
-HTC LIMIT [ENABLED]
-HTC TEMPERATURE LIMIT [70]

PERFORMANCE SETTINGS
-CPU VCore [StartUp]
-CPU NB Over Voltage [StartUp]
-Chipset Over Voltage [1.23V]
-HT Over Voltage [1.22V]
-Memory Over Voltage 1.60V]

CPU Frequency [200]

CPU FID/VID Control
- Custom P-Sates [DISABLED]

DRAM Timing Configuration
-Memory Clock Mode [AUTO]
-DRAM Timing Mode [ AUTO]

Memory CLK :N/A, DDR3-1333

Hyper Transport Configuration
-HT Link Speed [ AUTO]
-HT Link Width [AUTO]

Memory Configuration
-Bank Interleaving [AUTO]
-Channel Interleaving [XOR of Address bit]
-Enable CLock to All DIMMs [DISABLED]
-MemClk Tristate c3/ALTVID [DISABLED]
-Memory Hole Remapping [ENABLED]
-DCT Unganged Mode [ALWAYS]
-Power Down Enable [DISABLED]
-Page Smashing [DISABLED]

ECC Configuration

(All Disabled)

 

[Golden]

See post 8

 

[Banqu0]

Here is the results of the intelburn test

 

[Banqu0]

I have hit an issue with the furmark test. The GPU hits the max temperature of 102C in about 15 seconds. I am afraid of cooking the card.

 

[Banqu0]

UPDATE: memtest passed without errors

 

[Golden]

Here is the results of the intelburn test

Re-run it again, this time posting a screen capture of HWINFO as it records the temps. during the test.

 

[Banqu0]

The cause of the issue has been identified. There was a piece of paper stuck in the fan. Because the fan on the card is facing down in the case, I was unable to see it. It appeared to be packing material. I hope that no permanent damage was done to the card.