BSOD mostly when playing games, DRIVER_IRQL_... and PAGE_FAULT_...

Hi, I'm getting DRIVER_IRQL_NOT_LESS_OR_EQUAL and PAGE_FAULT_IN_NONPAGED_AREA BSOD's when playing games (around once or twice a month), and sometimes (almost never) when my PC is just running idle.

I've been getting these BSOD's for more than 6 months now.
At first I ran memtest for an entire night, and it gave allot of errors, so I replaced 3x1GB RAM for 2x4GB, but the problem wasn't solved...
I think it could also be the CPU, but I don't know how to test that.

Is Windows 7 . . .
- x86 (32-bit) or x64? x64
- the original installed OS on the system? no, it came with vista
- an OEM or full retail version? full retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer
- What is the age of system (hardware)? 4 years I think, I can't remember really
- What is the age of OS installation (have you re-installed the OS?) I had windows 7 for a while on it before I got any BSOD's, I reïnstalled windows 7 but it didn't fix the BSOD's

See my attachments for more info.

I hope someone knows the problem for these BSOD's, it's kinda annoying to play games now, because you know you can get a BSOD at any second, lol...

These old drivers need updating before we can investigate the underlying issue

Code:

asusgsb.sys    9/27/2007 9:14:50 AM       
ATKDispLowFilter.sys    5/13/2008 11:03:13 PM       
VMNET.SYS    5/22/2008 6:33:54 AM       
vmnetadapter.sys    5/22/2008 6:33:57 AM       
vmnetbridge.sys    5/22/2008 6:34:05 AM        
vstor2-ws60.sys    10/2/2008 9:04:32 PM       
vmci.sys    10/28/2008 8:57:29 PM       
hcmon.sys    10/28/2008 9:27:43 PM       
vmnetuserif.sys    10/28/2008 9:40:59 PM        
VMkbd.sys    10/28/2008 10:36:36 PM                  
vmx86.sys    10/28/2008 11:04:03 PM       
Rt64win7.sys    2/26/2009 5:04:13 AM        
PxHlpa64.sys    6/23/2009 7:16:35 PM

How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference Table

- - Driver manufacturer links are on this page: Drivers and Downloads



In addition I would run a system file check to verify the OS files.


SFC /SCANNOW Command - System File Checker

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

I updated my drivers with a driver updating program, and then I restarted my PC.
After that I tried to make another system report but I got a BSOD lol.

Anyway, restarted my PC and tried it again, this time without a BSOD.
Can you check it again?

Are you currently runnng VMware on this PC?
There are some old VMware drivers in the stack

vmnetbridge.sys Thu May 22 06:34:05 2008
vmnetadapter.sys Thu May 22 06:33:57 2008
VMNET.SYS Thu May 22 06:33:54 2008
VMkbd.sys Tue Oct 28 22:36:36 2008

And a couple from the Asus Gamer utility(update from the Asus site)
asusgsb.sys Thu Sep 27 09:14:50 2007

That said it shows as PAGE_FAULT_IN_NONPAGED_AREA driver is not Identified.

I would also consider Downloading Memtest+ burn it to a CD using a free program like Imgburn if you need one then boot from the CD to test the ram, let it run for at least 6 passes or until you see an error.

Code:

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a024d0b170, 0, fffff88001250881, 2}


Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!NtfsTeardownFromLcb+f1 )

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

3: kd> !analyze -v;r;kv;lmtn;lmtsmn;.bugcheck;!sysinfo cpuinfo;!sysinfo machineid; !sysinfo cpuspeed; !sysinfo smbios .logclose;q
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a024d0b170, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88001250881, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fe100
 fffff8a024d0b170 

FAULTING_IP: 
Ntfs!NtfsTeardownFromLcb+f1
fffff880`01250881 498b4d30        mov     rcx,qword ptr [r13+30h]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

Yea I run VMWare on my PC, and about a week or 2 after I installed VMWare I started getting these BSOD's, but I didn't thought that could be the problem.

I tried memtest a couple months ago, and a couple times it didn't give errors, and a couple times it did, but that's only at 20 or 30 passes (when I had it running all night long).

At the moment it's 02:40 here, so running memtest will be the first thing I'll do in the morning. I'll reply again once I have the results.

When I started my PC, I went AFK to eat something. After I came back, I had a new kind of BSOD... a BAD_POOL_HEADER?

PS: I'm haven't memtested with latest version yet, will do asap (I've just burned the disk).

zwarmapapa said:

When I started my PC, I went AFK to eat something. After I came back, I had a new kind of BSOD... a BAD_POOL_HEADER?

PS: I'm haven't memtested with latest version yet, will do asap (I've just burned the disk).

Related to SAlpham64.sys HID Driver from SteelSeries Corporation. I would remove it at least to test.


Old drivers

Code:

asusgsb.sys    9/27/2007 9:14:50 AM       
ATKDispLowFilter.sys    5/13/2008 11:03:13 PM                        
VMNET.SYS    5/22/2008 6:33:54 AM                          
vmnetadapter.sys    5/22/2008 6:33:57 AM                            
vmnetbridge.sys    5/22/2008 6:34:05 AM                               
vstor2-ws60.sys    10/2/2008 9:04:32 PM                             
vmci.sys    10/28/2008 8:57:29 PM          
hcmon.sys    10/28/2008 9:27:43 PM         
vmnetuserif.sys    10/28/2008 9:40:59 PM                              
VMkbd.sys    10/28/2008 10:36:36 PM          
vmx86.sys    10/28/2008 11:04:03 PM                             
spldr.sys    5/11/2009 12:56:27 PM             
PxHlpa64.sys    6/23/2009 7:16:35 PM

How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference Table

- - Driver manufacturer links are on this page: Drivers and Downloads

If you have any errors in memtest, there is a memory issue, start testing then 1 stick at a time(removing all but a single stick in slot 1)