BSOD when gaming/transferring files - Page_Fault_In_NonPaged_Area

onyxaj · 24 Mar 2012

Okay. RAM tested good. I know the system isnt running too hot (my fans don't even blow warm, they are cool).
I bought a new video card, and the system ran in game for longer than normal, but then I got BSOD: IRQL_NOT_LESS_OR_EQAUL.
I'm hoping this is a new type of issue that can be resolved. I attached the new dump files. Thanks for all the help so far.

writhziden · 24 Mar 2012

What makes you think the fans blowing cool air indicates the system is not overheating? When I received my previous laptop back from having it serviced, the fans were blowing cool air. The system was still turning off due to overheating. Turned out the heat sink/fan apparatus was not in proper contact with the CPU to provide adequate thermal management through heat transfer.

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\onyxaj\Windows_NT6_BSOD_jcgriff2\032412-19078-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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 Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e11000 PsLoadedModuleList = 0xfffff800`03055650
Debug session time: Sat Mar 24 20:22:28.467 2012 (UTC - 6:00)
System Uptime: 0 days 2:05:00.295
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa8045d66ed0, 2, 1, fffff88003d8f0a4}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffa8045d66ed0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88003d8f0a4, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bf100
 fffffa8045d66ed0 

CURRENT_IRQL:  2

FAULTING_IP: 
dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30
fffff880`03d8f0a4 48897108        mov     qword ptr [rcx+8],rsi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Majesty2.exe

TRAP_FRAME:  fffff8800a94ef10 -- (.trap 0xfffff8800a94ef10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8045d66ec8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003d8f0a4 rsp=fffff8800a94f0a0 rbp=fffffa800cc2f6a0
 r8=fffff8800a94f0c0  r9=0000000000000000 r10=0000000000000000
r11=fffff88001456120 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+0x30:
fffff880`03d8f0a4 48897108        mov     qword ptr [rcx+8],rsi ds:fffffa80`45d66ed0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e8d2e9 to fffff80002e8dd40

STACK_TEXT:  
fffff880`0a94edc8 fffff800`02e8d2e9 : 00000000`0000000a fffffa80`45d66ed0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0a94edd0 fffff800`02e8bf60 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0cc2f8a8 : nt!KiBugCheckDispatch+0x69
fffff880`0a94ef10 fffff880`03d8f0a4 : 00000000`00000000 fffffa80`0cc2f8a8 fffffa80`0cc2f898 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0a94f0a0 fffff880`03db9ae1 : 00000000`00000200 fffffa80`0f7d3010 fffffa80`00000000 fffffa80`0cda1010 : dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+0x30
fffff880`0a94f0f0 fffff880`03dbc523 : 00000000`00000200 fffff880`0a94f3c0 fffffa80`1051f270 00000000`00000000 : dxgmms1!VidSchiAllocateQueuePacket+0x45
fffff880`0a94f1d0 fffff880`03cfb764 : 00000000`00000000 00000000`00000200 fffff880`0a94f900 00000000`00000000 : dxgmms1!VidSchSubmitCommand+0x1f7
fffff880`0a94f230 fffff880`03cfa773 : fffff8a0`00000001 fffff8a0`00000004 fffff880`0a94f8b0 00000000`00000002 : dxgkrnl!DXGCONTEXT::Render+0xadc
fffff880`0a94f840 fffff960`0018f936 : 00000000`06a3e6b0 00000000`7efaa000 00000000`00000011 fffff800`02ed8e13 : dxgkrnl!DxgkRender+0x3e7
fffff880`0a94fab0 fffff800`02e8cfd3 : 00000000`00000011 fffff880`0a94fb60 00000000`0e33b8c0 00000000`0e4cd3c0 : win32k!NtGdiDdDDIRender+0x12
fffff880`0a94fae0 00000000`7464164a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`06a3e688 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7464164a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30
fffff880`03d8f0a4 48897108        mov     qword ptr [rcx+8],rsi

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30

BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30

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

Still pointing to a DirectX/graphics card problem. At this point, it is most likely the graphics card causing the issues since you re-installed DirectX and are still having the same crash. Try different graphics card driver versions to see how the system responds.

onyxaj · 25 Mar 2012

As the the overheating, I forgot to mention that the system has BSOD while idle too sometimes, and with 4 case fans and no overclocking, overheating seems VERY unlikely.

Anyway, I have tried 3 cards so far. I've tried a GTX460 (with performance boost), another GTX460 (little less poerful then the pervious), and a GT520. Granted, all these cards use the same driver from Nvidia, but will using a older driver actually work? I thought using the latest was always a must in most cases.

Also, I noticed that the file that seems to be in question here is dxgmms1. Searching for that, it seems the file is under folders with the name AMD in them. I don't have any AMD components in my computer. Could I delete these folders and see if the issue resolves?

writhziden · 25 Mar 2012

Can you show us the location of these amd folders? I am guessing they are amd64, which does not mean they are AMD, but that they contain 64-bit components that are vital to your system to run. If you delete them, your system will no longer function in Windows.

Screenshots and Files - Upload and Post in Seven Forums

onyxaj · 25 Mar 2012

They are AMD64 files.... so I guess I should leave thos alone. Do you know what older driver version I should go with from NVidia? I'm really thinking of turning to ATI cards with all the crap I am going through now. I never had issues with NVidia cards before, but I am ay my wits end at this point.

writhziden · 25 Mar 2012

It may be your graphics card memory or the GPU itself that is at fault. Have you had a chance to run the Furmark and Graphics Card RAM test? Even if your system is not overheating, your GPU could be. I have seen problems with GPU fans not spinning due to a defect the card or due to being blocked from spinning by another PCI card or power wire inside the system.

onyxaj · 25 Mar 2012

I doubt its the GPU since I have tried three different cards all with the same issue. All of the cards were NVidia, so maybe its a driver problem, but I don't know why the latest driver would cause these issues.

writhziden · 26 Mar 2012

The latest driver shouldn't be causing problems. Just to be sure, though, see if you can revert to an older driver; if you have a CD/DVD that came with the graphics card, that would be one method to do so. Make sure to use the following method to revert:Re-install or install the latest drivers for your display card. Your current drivers may be corrupt and/or outdated. Use the following method to re-install the drivers.

Get the display card driver version you want to test ready to install
Click Start Menu
Right Click My Computer/Computer
Click Manage
Click Device Manager from the list on the left
Expand Display adapters
Do the following for each adapter (in case you have multiple display cards)
- Right click the adapter
- Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
- Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer after uninstalling drivers for all display cards
Install the test driver for the display card(s) once Windows starts

Alternatively:

Login as an adminstrative user
Get the display card driver version you want to test ready to install
Click Start Menu
Click Control Panel
Click Hardware and Sound
Click Device Manager (the last link under Devices and Printers)
Expand Display adapters
Do the following for each adapter (in case you have multiple display cards)
- Right click the adapter
- Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
- Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer after uninstalling drivers for all display cards
Install the test driver for the display card(s) once Windows starts

onyxaj · 26 Mar 2012

Okay, so I installed the driver off the CD that same with my graphics cards and I'll see how that works. I did think of one thing that might be causing my problem, but I'm not sure. My motherboard apparently has onboard video (Intel HD Graphics), even though when I bought it, the specs said it didnt have onboard. Could this be causing the issue? Should I disable this, or am I just grasping at straws at this point?

writhziden · 26 Mar 2012

You could try disabling the Intel graphics and see if it helps. Wait and see how the system responds to the older driver for your graphics card first, though. If it still has stability issues, then you may consider disabling the Intel driver.