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 Memory Management Error, didn't catch error code.

15 Dec 2013   #11
RaptorBuddha

Windows 7 Ultimate SP1 64 bit
 
 

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.

Attachment 297545

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


My System SpecsSystem Spec
.
16 Dec 2013   #12
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

I am seeing that you havent followed the suggestion of post #2.
Code:
*******************************************************************************
*                                                                             *
*                        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
Probably caused by : nvlddmkm.sys ( 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
    Image name: nvlddmkm.sys
    Timestamp:        Mon Nov 11 18:54:05 2013 (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.
My System SpecsSystem Spec
19 Dec 2013   #13
RaptorBuddha

Windows 7 Ultimate SP1 64 bit
 
 

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

20 Dec 2013   #14
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

A roll back using the device manager will not be enough. A complete uninstall and a clean install is required.
My System SpecsSystem Spec
20 Dec 2013   #15
RaptorBuddha

Windows 7 Ultimate SP1 64 bit
 
 

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.
My System SpecsSystem Spec
26 Dec 2013   #16
RaptorBuddha

Windows 7 Ultimate SP1 64 bit
 
 

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:

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.

Attachment 298868

Thanks in advance for the help, and happy holidays, Arc!
My System SpecsSystem Spec
26 Dec 2013   #17
RaptorBuddha

Windows 7 Ultimate SP1 64 bit
 
 

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.

Attachment 298888

Attachment 298889
My System SpecsSystem Spec
27 Dec 2013   #18
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.
___________________________________________________________________________________________________
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

Probably caused by : memory_corruption ( nt!MiStoreSetEvictPageFile+b )

Followup: MachineOwner
---------
My System SpecsSystem Spec
27 Dec 2013   #19
RaptorBuddha

Windows 7 Ultimate SP1 64 bit
 
 

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.
My System SpecsSystem Spec
28 Dec 2013   #20
RaptorBuddha

Windows 7 Ultimate SP1 64 bit
 
 

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.

Attachment 299189

Thanks again for all your help, Arc.
My System SpecsSystem Spec
Reply

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




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD Memory Management error
Hi all, I was on my laptop and received a BSOD that stated a MEMORY MANAGEMENT issue, then automatically restarted. I ran the Windows Memory Diagnostic tool and it did not locate any issues. I then ran, as admin, in the command prompts, the scannow command. I downloaded my .txt file to my...
BSOD Help and Support
BSOD of few random error, Memory Management.
I have the dump files and all the details attached. Please help. Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.120503-2030) Language: English (Regional Setting: English) System Manufacturer: Gigabyte Technology Co., Ltd. ...
BSOD Help and Support
BSOD Memory Management Error
Dear Friends, Recently I've got this error and it drives me crazy and shuts my laptop down without any notifications. I really need it to be solved. Report is attached. Thanks in advanced. Farzad
BSOD Help and Support
Seemingly random BSOD - didn't manage to get the error code
I'm not really sure what happened, walked away from my computer, came back and it had crashed. Restarted it and got a Bluescreen error message but forgot to copy it down. Any help would be greatly appreciated!
BSOD Help and Support
BSOD Memory Management, error 0x000000a1 (I think)
Is Windows 7 x64 Full Retail - Hardware is about a month old, got them all in and put it together the 22 of November. - Only installed the OS once. So I bought the components to my new computer and assembled them a month ago. Since then I have been getting BSOD errors every few days...
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:39.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App