Solved BSOD Memory Management Error, didn't catch error code.

[RaptorBuddha]

Hello again, BSOD Forum,

I've been free of frequent BSODs since earlier this year. Recently I must have installed some software or something else must have gone wrong, because the blue screens are back.

Here is what happened earlier this year, in case anyone needs any further context:

http://www.sevenforums.com/bsod-hel...g-power-outage-varying-bccodes-frequency.html

There isn't any specific behavior or action that triggers the crashes. I was listening to Spotify and browsing the internet with Chrome on the most recent crash. Also, I seem to be having trouble installing a security update from Microsoft (Security Update for Windows 7 for x64-based Systems (KB2892074)). I've tried using the "Update Readiness" tool supplied by Microsoft, but it doesn't seem to be working. It only asks if I want to install some hotfix instead of the security update that keeps failing. Not sure if these two things are related, just thought I'd throw it out there in case anyone has had experience with this issue.

View attachment 297074

Aside from that, virus scans have been clear. MSE does nightly scans (I believe), and its definitions are constantly up to date.

Attached are the SF zip files. The last crash I got was a Memory Management error. I will run Memtest86 tonight and post the results tomorrow morning. If anyone sees anything of interest in the dumps please don't hesitate to let me know.

View attachment 297071

Thanks in advance,
Jeremy

 

[Arc]

Not happy to see you again with the issues, RaptorBuddha.

Display drivers are failing. Install and try the NVIDIA DRIVERS 314.22WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Atheros network driver is failing, too. Update it from ATHEROS drivers for Microsoft Windows (Atheros?????), matching your devices model number.

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.

Edit: The msinfo32.nfo file is corrupt..... upload it again for any future need.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

__________________________________________________________________________________________

BugCheck 1A, {41790, fffffa80019985d0, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

Followup: MachineOwner
-------------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff800030488f3, fffff88008515dc0, 0}

Probably caused by : memory_corruption ( nt!MmCleanProcessAddressSpace+f7 )

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

 

[RaptorBuddha]

Hello again, Arc!

Believe me, I'm as upset about being back as you are about seeing me back.

I stripped the Nvidia clutter off the system. Now only have the drivers installed you recommended.

Atheros driver has been updated from version 2.1.0.7 to 2.1.0.12. This one was a bit tricky. The Atheros driver database you linked didn't have a windows 7 version of the 8161/8165 Atheros. I found one through Dell at this link:

Driver Details | Dell US

Do you know if there's a way to suggest an integration of this file into that database?

Attached will be the msinfo32.nfo in case you need it.

View attachment 297113

I'll run memtest overnight tonight and post back with those results in the morning. Thanks again for the help, man!

 

[Arc]

Let us know how it is going.

 

[RaptorBuddha]

Memtest ran all night through 14 passes with no errors. I'm on my phone at the moment, so I'll upload another round of SF tool information when I get back home.

 

[RaptorBuddha]

Hey arc, final pass count on Memtest was 19. So I think the RAM is clear.

I'll use the system for the next few days and see if it keeps acting up, but I think the driver updates may have solved my issues.

Here is the SF zip file I made a few minutes ago, just in case something still looks weird to you.

View attachment 297254

Thanks again for all your help!
Jeremy

Edit: Still can't download that last update from Microsoft. It was Security Update KB2892074, error code on the windows updater is 80073712.

 

[Arc]

No BSOD after the last check. It is good.

Now observe how it is working. Let us know for any further issue.

 

[RaptorBuddha]

Just had a blue screen a few minutes ago. Also, I still can't install that latest update from Microsoft. Do you have any idea what could be interfering with that? It's only one update, not the entire update process. I have installed 2-3 updates, and it always fails on the same security update. Just thought I'd ask.

Here are the most recent dump files.

View attachment 297416

Thanks again for all the help.

 

[RaptorBuddha]

Got another BSOD. This time it was a System Service Exception, the code at the bottom was 0x0000003B.

Here's another round of crash dump files.

View attachment 297445

 

[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.

If memtest 86+ results no error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[RaptorBuddha]

Enabled DV as instructed. Tried getting to the desktop twice, both attempts were greeted with BSODs, so it's gotta be a driver. I got into safe mode, disabled DV, and here I am again. Just got some more dump files and will be uploading them on this post.

View attachment 297545

Thanks again, Arc. You've been a huge help.

 

[Arc]

I am seeing that you havent followed the suggestion of post #2.

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, b4, fffffa8008dd67a0, fffff8800f106879}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
[COLOR=Red]Probably caused by : nvlddmkm.sys[/COLOR] ( nvlddmkm+9a879 )

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 00000000000000b4, Handle value being referenced.
Arg3: fffffa8008dd67a0, Address of the current process.
Arg4: fffff8800f106879, Address inside the driver that is performing the incorrect reference.

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


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  rundll32.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800035204ec to fffff80003093bc0

STACK_TEXT:  
fffff880`0867e888 fffff800`035204ec : 00000000`000000c4 00000000`000000f6 00000000`000000b4 fffffa80`08dd67a0 : nt!KeBugCheckEx
fffff880`0867e890 fffff800`03535bf4 : 00000000`000000b4 fffffa80`08dd67a0 00000000`00000004 fffff8a0`0351fe00 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0867e8d0 fffff800`032ed890 : fffff8a0`00000003 fffff880`0867eb20 fffff880`0867ed00 fffff880`0867eeb0 : nt!VfCheckUserHandle+0x1b4
fffff880`0867e9b0 fffff800`033636b5 : fffff8a0`0347ea00 fffff8a0`00000001 fffffa80`067317a0 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x2027e
fffff880`0867ea80 fffff800`03092e53 : fffffa80`09a42b50 fffff880`0867ee38 00000000`00000002 00000000`00000000 : nt!NtQueryValueKey+0x115
fffff880`0867ec10 fffff800`0308f410 : fffff800`03524d96 fffff880`0f106879 fffff880`0867eeb0 fffff880`0867eea8 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0867ee18 fffff800`03524d96 : fffff880`0f106879 fffff880`0867eeb0 fffff880`0867eea8 fffff800`0308f410 : nt!KiServiceLinkage
fffff880`0867ee20 fffff880`0f106879 : fffff880`0867f8ca fffff880`0867eef0 fffff880`0867f8b8 fffffa80`06cc7098 : nt!VfZwQueryValueKey+0x76
fffff880`0867ee70 fffff880`0867f8ca : fffff880`0867eef0 fffff880`0867f8b8 fffffa80`06cc7098 00000000`00000000 : nvlddmkm+0x9a879
fffff880`0867ee78 fffff880`0867eef0 : fffff880`0867f8b8 fffffa80`06cc7098 00000000`00000000 fffff880`0867eea0 : 0xfffff880`0867f8ca
fffff880`0867ee80 fffff880`0867f8b8 : fffffa80`06cc7098 00000000`00000000 fffff880`0867eea0 fffff980`00000000 : 0xfffff880`0867eef0
fffff880`0867ee88 fffffa80`06cc7098 : 00000000`00000000 fffff880`0867eea0 fffff980`00000000 00000000`000000b4 : 0xfffff880`0867f8b8
fffff880`0867ee90 00000000`00000000 : fffff880`0867eea0 fffff980`00000000 00000000`000000b4 fffffa80`00280026 : 0xfffffa80`06cc7098


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+9a879
fffff880`0f106879 3d340000c0      cmp     eax,0C0000034h

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  nvlddmkm+9a879

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5280da75

FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_nvlddmkm+9a879

BUCKET_ID:  X64_0xc4_f6_VRF_nvlddmkm+9a879

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

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f06c000 fffff880`0fcad000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
[COLOR=Red]    Image name: nvlddmkm.sys
    Timestamp:        Mon Nov 11 18:54:05 2013[/COLOR] (5280DA75)
    CheckSum:         00C10283
    ImageSize:        00C41000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

As far as you will not do it, the chances of crash will not be minimized and the troubleshooting area will not be shortened.

 

[RaptorBuddha]

Ok, rolled back to the 314 drivers. I'll use the system for a bit and see what happens.

 

[Arc]

A roll back using the device manager will not be enough. A complete uninstall and a clean install is required.

 

[RaptorBuddha]

I understand. I did the same thing described in your first post. I'm back where I was right after I initially changed the drivers.

 

[RaptorBuddha]

Had another BSOD a few minutes ago. System Service Exception, I think. I was just listening to music and browsing Amazon when it happened. Nothing strenuous. Here are the dumps:

View attachment 298867

Also, still can't update via Windows Update. I've checked that area of the forums for solutions and the .bat tool didn't solve my issues. Here's a screenshot. I will go start a thread over there about it, just thought I'd throw it on here too since it started after my BSOD's reemerged.

View attachment 298868

Thanks in advance for the help, and happy holidays, Arc!

 

[RaptorBuddha]

Here are more dumps. The one with a 2 in parentheses is the more recent. System has been very erratic the past few days. Not really sure which driver is messing me up. Let me know what you see, Arc! Thanks again for all your awesome help. I couldn't have remained sane through all this without you!

Last 2 crashes were bad pool headers and an IQRL Not less than or equal, or something to that effect.

View attachment 298888

View attachment 298889

 

[Arc]

Mate, first make it sure that nothing is overclocked, and all hardware are running at their stock settings.

Then, swap the RAM modules, on an assumption that memtest is detecting the faults.

At last, nothing remains other than swapping the motherboard

Crash dumps are pointing to memory issue again.
___________________________________________________________________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {8, 2, 0, fffff8000318f76b}

[COLOR=Red]Probably caused by : memory_corruption[/COLOR] ( nt!MiStoreSetEvictPageFile+b )

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

 

[RaptorBuddha]

The i5 I'm using and all other components are running at stock speeds. RAM is at 1600 MHz with the performance enhance in the BIOS set to normal instead of turbo. Shouldn't be trying to pump out more than it's capable of. I'm posting this from my laptop, as my desktop has recently become unusable. Whenever I try to open a program, such as Chrome, I get weird errors saying it can't be launched because the data at a particular memory address can't be read. So I think your theory about the RAM is correct.

I'll run Memtest throughout today with the RAM in their current slots, then I'll swap them around to different slots and run it again overnight. If no errors pop up with either of those tests, I will take your advice and try to use a different set of RAM entirely and see how the system functions.

If the system is still unstable I will look into rebuilding my system with a new mobo and possibly take this opportunity to upgrade some other components as well. My power supply is only just powerful enough for the components I'm using, but I was a bit strapped for cash when I assembled this rig. I will probably need to dump a bit more money into it to get it running smoothly with higher end components.

Thanks for all your help, man.

 

[RaptorBuddha]

Memtest didn't turn up anything. I got another bad pool header BSOD just now. It's probably the RAM or motherboard. Just going to throw up one last round of dump files for you to look at to make sure before I order new RAM to try.

View attachment 299189

Thanks again for all your help, Arc.