Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD - ntoskrnl.exe, page fault, irql


06 Jun 2011   #1

Windows 7 Ultimate x64
 
 
BSOD - ntoskrnl.exe, page fault, irql

Hey all,

I built a computer from new parts I bought in December 2010.

Mainboard: Asus M4A89GTD-PRO/USB3
Bios: American Megatrends Inc.
Processor: AMD Phenom II X6 1090T @ 3.2 GHz (6 core)
Chipset: AMD 890GX
RAM: 8GB OCZ 8192MBDDR3-SDRAM
Video: nVidia GeForce GTX 460 SE
C Drive: OCZ-Agility2 SSD 120GB

- Windows 7 Ultimate x64
- home built machine, so Windows 7 was installed by me
- all hardware is from December 2010
- reformatted 6 days ago (due to 2-5 bluescreens per day)

so to sum up... i got a blue screen the day i built the machine in December... hoped it was a fluke, and pressed on. they persisted, so i installed "bluescreenview", which analyzes dump files, because i had no idea how to otherwise. the causes were very often ntoskrnl.exe, but other drivers and dll's were listed, i can't remember exactly what they were though. it got slowly worse as weeks went by, to the point where i was getting a blue screen an average of 3 times a day, and it seemed to be caused by firefox more often than not... but sometimes i would just be messing with some code in dreamweaver and bam. AVG caused it a few times also, but i eventually removed that and installed avast free. i think i'll switch to MSE though.

i got very mad last week and just reformatted, and purposely didn't install firefox or avg, but i did put avast on right away. i went 4 days without a blue screen, but then yesterday the first one showed up. then again today. all i was doing was listening to grooveshark in google chrome, both times.

i followed the new thread instructions, and zipped up the dmps and perfmon, attached. there are only two dmps right now, but i wanna try to fix this crap before i get everything organized again. i haven't messed with hardware at all. i was thinking about reseating the RAM, but again, i'd like to know exactly what is happening before i go switching things and then wonder what fixed it, if it does in fact stop. hopefully you guys can figure it out?!?

My System SpecsSystem Spec
.

06 Jun 2011   #2

Windows 8.1 Pro x64
 
 

ASACPI.sys the 2005 version is a huge cause of BSODs
information   Information
The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
Scroll down to the Utilities category, then scroll down to the "
ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005
)

Code:
ASACPI.sys        fffff880`13c51000    fffff880`13c59000    0x00008000    0x42476c4c    28/03/2005 06:30:36
Update any Garmin software Support
My System SpecsSystem Spec
06 Jun 2011   #3

Windows 7 Ultimate x64
 
 

you're like a sniper. thanks for the instantaneous assistance.

asacpi.sys new date stamp of 5/14/2009

why did you mention the garmin drivers? are they culprits as well? i just installed it today though, so it wouldn't explain yesterday's BS. hopefully it's not a cause... i use it to upload my airplane gps data to my employer... maybe i will have to tell them they can't spy on my flights anymore because my computer is suffering from siezures.

thanks again. i will see what happens in the next few days and update next time i get owned.
My System SpecsSystem Spec
.


06 Jun 2011   #4

Windows 8.1 Pro x64
 
 

Quote   Quote: Originally Posted by insidious View Post
you're like a sniper. thanks for the instantaneous assistance.

asacpi.sys new date stamp of 5/14/2009

why did you mention the garmin drivers? are they culprits as well? i just installed it today though, so it wouldn't explain yesterday's BS. hopefully it's not a cause... i use it to upload my airplane gps data to my employer... maybe i will have to tell them they can't spy on my flights anymore because my computer is suffering from siezures.

thanks again. i will see what happens in the next few days and update next time i get owned.
Monitor any more BSODs
The garmin drivers seems outdated, update the software using it since old software drivers can cause BSODs.
My System SpecsSystem Spec
07 Jun 2011   #5

Windows 7 Ultimate x64
 
 

welp, the garmin driver i got was directly from them, the day after my first BSOD since this most recent reformat. if it seems outdated, it's probably because it is. it's for an aviation GPS. aviation is a very tiny community compared to automotive, so i doubt they update this driver too often. i went to that support link, and typed in my device name (GPSmap 96C) and there was nothing for it.

got another blue screen 5 minutes ago. this time i had grooveshark going, a decent amount of tabs open in chrome, and i was renaming a pdf file in windows explorer. rebooted and immediately ran the jcgriff thing and made a new perfmon report, attached.

i'll begin perusing through the results... o_0
My System SpecsSystem Spec
08 Jun 2011   #6

Windows 8.1 Pro x64
 
 

Memory corruption is indicated
You should test the RAM RAM - Test with Memtest86+
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa8016bf2b78, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002f2aab7, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b00e0
 fffffa8016bf2b78 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiIdentifyPfn+317
fffff800`02f2aab7 488b4118        mov     rax,qword ptr [rcx+18h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff88007b5b4f0 -- (.trap 0xfffff88007b5b4f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffffa8016bf2b60
rdx=00000000000b2dd6 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f2aab7 rsp=fffff88007b5b680 rbp=fffffa8006c998f8
 r8=000000000019b5d9  r9=0000000000000001 r10=0000000000000042
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiIdentifyPfn+0x317:
fffff800`02f2aab7 488b4118        mov     rax,qword ptr [rcx+18h] ds:fffffa80`16bf2b78=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e77c69 to fffff80002e78700

STACK_TEXT:  
fffff880`07b5b3a8 fffff800`02e77c69 : 00000000`0000000a fffffa80`16bf2b78 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`07b5b3b0 fffff800`02e768e0 : 00000000`42506650 02000000`001d4dc3 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`07b5b4f0 fffff800`02f2aab7 : 00000000`00000000 02000000`00107059 00000000`000018c0 fffff800`0313ded7 : nt!KiPageFault+0x260
fffff880`07b5b680 fffff800`02f2b6bb : 00000000`00000000 00000000`00000004 fffffa80`08416b98 fffffa80`08416000 : nt!MiIdentifyPfn+0x317
fffff880`07b5b720 fffff800`0328abd5 : fffffa80`08416000 fffff880`07b5bca0 fffff880`07b5b7f8 00000000`00000000 : nt!MmQueryPfnList+0xbb
fffff880`07b5b760 fffff800`031d0a18 : 00000000`00000006 00000000`00000000 fffffa80`08416000 fffff800`02e08001 : nt!PfpPfnPrioRequest+0x115
fffff880`07b5b7b0 fffff800`03174fd3 : 00000000`00000000 fffff800`02e08000 00000000`00000000 fffffa80`09b1a001 : nt! ?? ::NNGAKEGL::`string'+0x46a9d
fffff880`07b5b840 fffff800`03175df5 : 00000000`01f5bcc8 fffff800`033ee895 00000000`01f5bd20 fffff880`07b5bca0 : nt!ExpQuerySystemInformation+0x11c2
fffff880`07b5bbe0 fffff800`02e77953 : 00000000`07642558 fffff880`07b5bca0 00000000`027c2f80 00000000`00000006 : nt!NtQuerySystemInformation+0x4d
fffff880`07b5bc20 00000000`776bfa1a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01f5bbe8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776bfa1a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiIdentifyPfn+317
fffff800`02f2aab7 488b4118        mov     rax,qword ptr [rcx+18h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiIdentifyPfn+317

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd34

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+317

BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+317

Followup: MachineOwner
---------
My System SpecsSystem Spec
08 Jun 2011   #7

Windows 7 Ultimate x64
 
 

13 errors. did 7 passes, it took just under 13 hours.
13 errors seems like a lot. these ram sticks are 6 months old, and i've been blue screening since day 1, so if they're at fault, they were bad when i got them. unless it's the mobo. in either case, something was shoddy when new. that sucks.

i wrote down all the failing addresses, err-bits, etc. wasn't sure if it would create a log or something, and then it slipped my mind to check in the configuration menu before rebooting. so i have all the errors but they're handwritten. i'm gonna shut down and start testing stick by stick. let me know if you want to see what addresses failed during which pass and i'll type it up.
My System SpecsSystem Spec
09 Jun 2011   #8

Windows 8.1 Pro x64
 
 

Quote   Quote: Originally Posted by insidious View Post
13 errors. did 7 passes, it took just under 13 hours.
13 errors seems like a lot. these ram sticks are 6 months old, and i've been blue screening since day 1, so if they're at fault, they were bad when i got them. unless it's the mobo. in either case, something was shoddy when new. that sucks.

i wrote down all the failing addresses, err-bits, etc. wasn't sure if it would create a log or something, and then it slipped my mind to check in the configuration menu before rebooting. so i have all the errors but they're handwritten. i'm gonna shut down and start testing stick by stick. let me know if you want to see what addresses failed during which pass and i'll type it up.
This means you have defective RAM, you should get new RAM
My System SpecsSystem Spec
09 Jun 2011   #9

Windows 7 Ultimate x64
 
 

well, yes, but i'd like to know which ones are bad. and they weren't cheap and they're basically brand new so it's also a little annoying just buying new ram.

stick 1 in slot 1 passed with flying colors... 16 passes and no errors. stick 2 in slot 2 is on pass 2 right now, with no errors so far. if i get zero errors doing it one by one, i'll be a little perplexed. gonna be a while and i gotta go fly so i'll be back and forth.

thanks for all the help thus far. i'll post again when i have results from each stick and slot.
My System SpecsSystem Spec
10 Jun 2011   #10

Windows 7 Ultimate x64
 
 

stick 1 slot 1, 16 passes, 0 errors.
stick 2 slot 2, 8 passes, 0 errors.
stick 3 slot 3, 10 passes, 2 errors.
stick 4 slot 4, 10 passes, 13 errors.

stick 1 slot 4, 3 passes, 0 errors.

stick 1 and stick 2, slot 3 and slot 4, 10 passes, 0 errors.

safe to say my motherboard is healthy and stick 3 and 4 are bad. also safe to say that OCZ is getting a phone call from me.

i'll run the computer on just the 4GB of RAM and wait for more BSODs.
My System SpecsSystem Spec
Reply

 BSOD - ntoskrnl.exe, page fault, irql




Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 04:52 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33