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

[zwarmapapa]

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...

 

[zigzag3143]

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

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.


http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

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

 

[zwarmapapa]

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?

 

[Wrench97]

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.

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

 

[zwarmapapa]

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.

 

[zwarmapapa]

So I ran memtest v4.0a (still had it on a CD), and this are the results:

Pass 0, Test 9 [random number sequence] with memtest 32bit

Repeatingly getting 2 errors:
at 838mb with CPU 1
at 1962mb with CPU 3
over 90000 errors... and it's still increasing

 

[zwarmapapa]

The second try it gave errors at Pass 0 Test 9, at 22 MB with CPU 2, again over 90000 errors, still increasing.
Why do I get memtest errors at test 9?

Edit: 3th try also gave errors at Test 9, this time at 37MB with CPU 1, I'll try it with the latest version of memtest.

 

[zwarmapapa]

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).

 

[zigzag3143]

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

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

 

[Wrench97]

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)

 

[zwarmapapa]

I'm running memtest v4.20 atm, and currently it's at 4 passes without any errors.
I'm gonna leave it on at night to see what happens.

 

[zwarmapapa]

So I let memtest v4.20 run all night long, and I got 3 errors:
- pass 10 test 8 - 9246.9MB - Err-Bits 80000000
- pass 11 test 5 - 9246.9MB - Err-Bits 80000000
- pass 11 test 5 - 9310.9MB - Err-Bits 80000000

How can it give errors at RAM over 9000MB? I only got 8191MB? Besides that, what do to next?

Edit: just got another one, after pass 9 suddenly the errors pop up lol.
- pass 11 test 6 - 9246.9MB - Err-Bits 80000000

 

[Wrench97]

Test one stick at a time.

 

[zwarmapapa]

I've just tested one, and I didn't had any errors, I'll test the other stick tomorrow.

Another thing, I just checked my RAM sticks again, and I thought they were exactly the same, but one is 1.5v and the other one is 1.6v, could this give any problems?

 

[Wrench97]

Yes it certainly could, since that means they are not matched running different specs.

 

[zwarmapapa]

I've tested the other stick, it's currently at pass 8 and still no errors...

Both sticks separately don't give any errors, and together they only give errors after more than 10 hours testing, but outside memtest I get a BSOD around every 1-4 hours...

Could this problem be caused by the fact that the voltages of the ram sticks don't match? Could the problem be caused by another defect hardware, like the CPU or GPU? Could the problem be that I didn't set the right voltages in BIOS?

 

[Wrench97]

More likely the unmatched sticks are negotiating a compromise setting in order to boot, but neither are completely stable with it.

I would try a matched set of ram.