Bluescreen every 5 minutes!

Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Aldirus

Thread Starter
Joined
Dec 29, 2012
Messages
6
Hey, I keep getting a BSOD that say either Memory Management or Page fault in nonpaged area. Now, I had this problem before, and it was bad ram (16 gb of corsair vengeance) but I replaced it with kingston hyperX and the problem seemed to go away until just recently. Its back and i have no clue what to do, since I replaced my ram and the problem came back. Could it be my motherboard that is somehow ruining my RAM? I have no idea what to do here..

Processor: AMD FX-8150
Motherboard: Asrock970 Extrem3
RAM: 16GB Kingston HyperX
HDD: 500GB Seagate
Graphics Card: Nvidia GTX 560 TI
OS: Windows 7 Ultimate
 

Frank4d

Retired Trusted Advisor
Joined
Sep 10, 2006
Messages
9,126
I usually suspect RAM first when blue screens are random like yours. Try running memtest86+ http://www.memtest.org.

Also, how many sticks of RAM are you using, 2 or 4?
 
Joined
Aug 4, 2003
Messages
5,622
That's a text file that has basic description. you need to go to C:\Windows\Minidump copy Minidump to the desktop, compress it and upload here.
 

Aldirus

Thread Starter
Joined
Dec 29, 2012
Messages
6
2x8GB sticks.. And yeah I think its ram too.. I had this problem before with my old RAM and I replaced it.. I just want to know why it happened with this new set of RAM I bought too..
 

Attachments

dai

Joined
Mar 6, 2003
Messages
11,198
multiple different bsod would indicate it

see if you can borrow a quality unit to check with
 
Joined
Aug 4, 2003
Messages
5,622
Are you playing League of Legends? one of the dump files point in that direction. Is there an update or patch for that game?

PHP:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\122912-15085-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*your local folder for symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`03062000 PsLoadedModuleList = 0xfffff800`032a6670
Debug session time: Fri Dec 28 22:24:56.811 2012 (UTC - 8:00)
System Uptime: 0 days 0:17:42.871
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+a2 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8007334a60
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  League of Lege

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000314cb50 to fffff800030e0fc0

STACK_TEXT:  
fffff880`0c6acf88 fffff800`0314cb50 : 00000000`0000001a 00000000`00041790 fffffa80`07334a60 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0c6acf90 fffff800`030cd81f : fffffa80`00000000 00000000`484fffff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35054
fffff880`0c6ad150 fffff800`030e0253 : ffffffff`ffffffff fffff8a0`08386288 fffff8a0`083862b0 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0c6ad250 fffff800`030dc810 : fffff880`048354b2 fffff8a0`081c21b0 fffffa80`103fdb30 fffffa80`10282f00 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0c6ad3e8 fffff880`048354b2 : fffff8a0`081c21b0 fffffa80`103fdb30 fffffa80`10282f00 fffff8a0`08386280 : nt!KiServiceLinkage
fffff880`0c6ad3f0 fffff880`04820b5a : fffff880`0c6ad4f0 fffff8a0`02c8fe70 00000000`00000001 fffffa80`0e529000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0xa2
fffff880`0c6ad420 fffff880`0481b523 : fffffa80`0feb22a0 00000000`00000001 fffff8a0`081c21b0 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x112
fffff880`0c6ad4d0 fffff880`04801ecc : fffff880`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`0c6ad5a0 fffff880`04924ccc : 00000000`00000000 fffff8a0`00fd9000 fffff8a0`00fd9000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0c6ad5d0 fffff880`0492465f : fffff8a0`00fd9000 fffff8a0`00fda300 fffff8a0`00000000 fffffa80`00000799 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`0c6ad6c0 fffff880`049248e1 : 00000000`00000000 fffff8a0`00fd9000 00000000`00000001 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
fffff880`0c6ad710 fffff880`0492879c : fffff8a0`08098800 fffff880`0c6adb60 fffffa80`0f327000 fffff880`048ef3af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9
fffff880`0c6ad760 fffff880`0492ae57 : fffff8a0`00fd9000 fffff880`0c6ad870 00000000`7eede001 00000000`00000001 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x448
fffff880`0c6ad7f0 fffff960`001a045a : 00000000`00000000 fffffa80`0f571570 00000000`00000020 00000000`747c6168 : dxgkrnl!DxgkDestroyAllocation+0x9bf
fffff880`0c6adab0 fffff800`030e0253 : fffffa80`0f571570 fffff880`0c6adb60 00000000`00000000 fffffa80`1046cc60 : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`0c6adae0 00000000`747e141a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`18fee7e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x747e141a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_PROCESS_HEAP::Free+a2
fffff880`048354b2 488b0e          mov     rcx,qword ptr [rsi]

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

BUCKET_ID:  X64_0x1a_41790_dxgmms1!VIDMM_PROCESS_HEAP::Free+a2

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

Aldirus

Thread Starter
Joined
Dec 29, 2012
Messages
6
Yeah.. I play that game a lot, but I've played that game for months with no problems, and yeah it updates every 2 weeks or so
 
Status
This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue. View our Welcome Guide to learn how to use this site.

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 807,865 other people just like you!

Latest posts

Staff online

Top