BSOD - Help - memory manager

Toggle sidebar Toggle sidebar
R

reggae234

Honorable
Aug 10, 2013
25
0
10,530
ok i have had the same rig for about 2 years years. i5-3570k, gigabyte ga-z68xp-ud3, MSI r7970 hawk, and corsair cmz8gx3m2a1866c9b memory. I knew nothing really about choosing components when i built it (now i know enough to know i dont know much....), However since I have been having problems lately (rarely in the last year during gaming, frequently in the last couple months running star citizen ( very graphically intensive game), I went back and looked at the QVL memory list on ASUS's website. My ram is not on the approved list, it has the same timing and voltage as some of the approved modules but mine is not listed. I would imagine this is my problem but i thought i would ask before spending money on new ram (strapped for cast atm). So, is this really my problem, and if so will new ram from the approved list fix my problem, or have I likely done damage to cpu/mobo from running the wrong ram. Computer NEVER conks out if not gaming, no noticeable issues. ambient temps and cpu/gpu temps are high but within where they should be.I have been having BSOD with header MEMORY MANAGER giving codes STOP: 0x0000001A, 0X0000000000005002, 0XFFFFF700001080000, 0X0000000000008D84, X01008657FFFFFFFE).

Any help greatly appreciated.

Thanks
Thomas
 
Solution
A


Correct. Should be a sticker on the RAM with the proper timings. Match that exactly. If you are overclocking, set it back to normal settings.

I'd run a benchmark on the videocard, like Furmark, and see if it overheats (90C) or locks up.
Sort by date Sort by votes
A

Alec Mowat

Honorable
Jan 8, 2014
3,244
0
13,460
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\amowat\Desktop\070614-6583-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03c51000 PsLoadedModuleList = 0xfffff800`03e94890
Debug session time: Sun Jul 6 11:37:39.922 2014 (GMT-4)
System Uptime: 0 days 1:10:58.816
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5002, fffff70001080000, 8d84, 1008657fffffffe}

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

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005002, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 0000000000008d84
Arg4: 01008657fffffffe

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


BUGCHECK_STR: 0x1a_5002

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: StarCitizenLau

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80003c606e7 to fffff80003cc6bc0

STACK_TEXT:
fffff880`07b1d978 fffff800`03c606e7 : 00000000`0000001a 00000000`00005002 fffff700`01080000 00000000`00008d84 : nt!KeBugCheckEx
fffff880`07b1d980 fffff800`03cc4cee : 00000000`00000001 00000000`0975f000 00000000`10b0a601 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x45f68
fffff880`07b1dae0 00000000`6a1b7355 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0018cce0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6a1b7355


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+45f68
fffff800`03c606e7 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+45f68

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 531590fb

FAILURE_BUCKET_ID: X64_0x1a_5002_nt!_??_::FNODOBFM::_string_+45f68

BUCKET_ID: X64_0x1a_5002_nt!_??_::FNODOBFM::_string_+45f68

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

2: kd> lmvm nt
start end module name
fffff800`03c51000 fffff800`04236000 nt (pdb symbols) C:\Program Files\Debugging Tools for Windows (x64)\sym\ntkrnlmp.pdb\BF9E190359784C2D8796CF5537B238B42\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: C:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\531590FB5e5000\ntoskrnl.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Timestamp: Tue Mar 04 03:38:19 2014 (531590FB)
CheckSum: 00554C03
ImageSize: 005E5000
File version: 6.1.7601.18409
Product version: 6.1.7601.18409
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 6.1.7601.18409
FileVersion: 6.1.7601.18409 (win7sp1_gdr.140303-2144)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.
 
Upvote 0 Downvote
R

reggae234

Honorable
Aug 10, 2013
25
0
10,530
I have the most up to date catalyst and have had this issue thru an official version, the beta, and now the most current version. any suggestions as to what I should change/update? Should i leave my ram as is?

Thanks a lot for looking into this for me Alex, greatly appreciated.
 
Upvote 0 Downvote
A

Alec Mowat

Honorable
Jan 8, 2014
3,244
0
13,460
If it's ONLY in Starcitizen, I am just going to go ahead and say Starcitizen is causing the BSOD, and not your hardware (it is beta, afterall).

I'd just report the bug.


If it's anywhere outside of that game, then I'd recommend just running a memtest for a few hours.
 
Upvote 0 Downvote
R

reggae234

Honorable
Aug 10, 2013
25
0
10,530
it has happened on a couple other games but not i quite a while, ran a default memtest which came back clean. Il run a longer test tomorrow while im at work and see. thanks for the help.
 
Upvote 0 Downvote
A

Alec Mowat

Honorable
Jan 8, 2014
3,244
0
13,460


Correct. Should be a sticker on the RAM with the proper timings. Match that exactly. If you are overclocking, set it back to normal settings.

I'd run a benchmark on the videocard, like Furmark, and see if it overheats (90C) or locks up.
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom