bsod page fault in nonpaged area

steegz · Dec 28, 2012

hey there been looking around online as to what i can do regarding this bsod. its been happening very frequently rarely whenever it happens does it happen immediately a second time but rather after 30 minutes or so of my pc being on. ive posted the zip below; steps ive done already are cmd chkdsk, nothing came up in there. virus scan. nothing there. ive system restored to 2 weeks ago. issue remains. ive read online some people are saying update graphics drivers and its a possible fix so im doing that as we speak. heres the zip let me know what you think, your help is appreciated!

edit: pc specs are as follows.
i7 2600k (not oc'd)
water cooled
3x hd radeon 6950 (running in crossfire)
asus maximus iv extreme mobo
ripjaw ram. 16 gb 4x4gb sticks
not sure what else i should add here but if you need more details feel free to let me know. almost finished updating drivers for my graphics cards as well.

edit2: gpu software is updated. for some reason it did not require me to restart my pc. so im going to do that manually and continue as normal until/if it happens again will be checking back every 10 minutes or so for a solution.

koolkat77 · Dec 28, 2012

Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.

Code:

[FONT="Lucida Console"]*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88006a1f7d8, fffff88006a1f030, fffff8800137e463}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff88006a1f7d8
Arg3: fffff88006a1f030
Arg4: fffff8800137e463

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


EXCEPTION_RECORD:  fffff88006a1f7d8 -- (.exr 0xfffff88006a1f7d8)
ExceptionAddress: fffff8800137e463 (Ntfs!NtfsOpenFcbById+0x0000000000000333)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff88006a1f030 -- (.cxr 0xfffff88006a1f030)
rax=fffffa800f862f70 rbx=0000000000000000 rcx=fffffa800dada300
rdx=0000000000000001 rsi=fffffa800f216e40 rdi=0000000000000000
rip=fffff8800137e463 rsp=fffff88006a1fa10 rbp=fffffa800f862c60
 r8=fffff88006a1fa78  r9=0000000000000004 r10=0000000000000004
r11=fffff8a0004bc000 r12=0000000000000000 r13=fffff88003361ef0
r14=00000000000001f0 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
Ntfs!NtfsOpenFcbById+0x333:
fffff880`0137e463 f0e980e10148    lock jmp fffff880`4939c5e9
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x24

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

LAST_CONTROL_TRANSFER:  from fffff880012b5b91 to fffff8800137e463

STACK_TEXT:  
fffff880`06a1fa10 fffff880`012b5b91 : fffffa80`0f216e40 fffffa80`0f862c60 00000000`00000000 00020000`0000023d : Ntfs!NtfsOpenFcbById+0x333
fffff880`06a1fb10 fffff880`0121dc0d : fffffa80`0f216e40 fffffa80`0f862c60 fffff880`03361ef0 fffffa80`0d09a600 : Ntfs!NtfsCommonCreate+0x1cdf
fffff880`06a1fcf0 fffff800`036c5d87 : fffff880`03361e60 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`06a1fd20 fffff800`036c5d41 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
fffff880`03361d30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


CHKIMG_EXTENSION: !chkimg -lo 50 -d !Ntfs
    fffff8800137e463 - Ntfs!NtfsOpenFcbById+333
	[ d0:f0 ]
1 error : !Ntfs (fffff8800137e463)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

STACK_COMMAND:  .cxr 0xfffff88006a1f030 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption[/FONT]

Upload a screenshot of your hard disk using CrystalDiskInfo:

Make a hard drive test from the hard drive manufacturers website:

Hard Drive Diagnostic Procedure

Run Disk Check on your hard disk for file system errors and bad sectors on it:

http://www.sevenforums.com/tutorials/433-disk-check.html

Hard drive test both short and long with:

SeaTools for Windows

Also the DOS version of:

SeaTools for DOS
SeaTools for DOS tutorial

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Information

Errors are sometimes found after 8 passes.

Tip

Do this test overnight, before going to bed.

steegz · Dec 28, 2012

koolkat77 said:
Please upload your msinfo32.nfo file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Save -> Save as msinfo32.nfo and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .nfo file, click send to compressed (zipped) folder -> Upload the .zip file here.

Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.

Code:

[FONT="Lucida Console"]******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {1904fb, fffff88006a1f7d8, fffff88006a1f030, fffff8800137e463} Probably caused by : memory_corruption Followup: memory_corruption --------- 7: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* NTFS_FILE_SYSTEM (24) If you see NtfsExceptionFilter on the stack then the 2nd and 3rd parameters are the exception record and context record. Do a .cxr on the 3rd parameter and then kb to obtain a more informative stack trace. Arguments: Arg1: 00000000001904fb Arg2: fffff88006a1f7d8 Arg3: fffff88006a1f030 Arg4: fffff8800137e463 Debugging Details: ------------------ EXCEPTION_RECORD: fffff88006a1f7d8 -- (.exr 0xfffff88006a1f7d8) ExceptionAddress: fffff8800137e463 (Ntfs!NtfsOpenFcbById+0x0000000000000333) ExceptionCode: c000001d (Illegal instruction) ExceptionFlags: 00000000 NumberParameters: 0 CONTEXT: fffff88006a1f030 -- (.cxr 0xfffff88006a1f030) rax=fffffa800f862f70 rbx=0000000000000000 rcx=fffffa800dada300 rdx=0000000000000001 rsi=fffffa800f216e40 rdi=0000000000000000 rip=fffff8800137e463 rsp=fffff88006a1fa10 rbp=fffffa800f862c60 r8=fffff88006a1fa78 r9=0000000000000004 r10=0000000000000004 r11=fffff8a0004bc000 r12=0000000000000000 r13=fffff88003361ef0 r14=00000000000001f0 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 Ntfs!NtfsOpenFcbById+0x333: fffff880`0137e463 f0e980e10148 lock jmp fffff880`4939c5e9 Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: CODE_CORRUPTION BUGCHECK_STR: 0x24 PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction. EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction. LAST_CONTROL_TRANSFER: from fffff880012b5b91 to fffff8800137e463 STACK_TEXT: fffff880`06a1fa10 fffff880`012b5b91 : fffffa80`0f216e40 fffffa80`0f862c60 00000000`00000000 00020000`0000023d : Ntfs!NtfsOpenFcbById+0x333 fffff880`06a1fb10 fffff880`0121dc0d : fffffa80`0f216e40 fffffa80`0f862c60 fffff880`03361ef0 fffffa80`0d09a600 : Ntfs!NtfsCommonCreate+0x1cdf fffff880`06a1fcf0 fffff800`036c5d87 : fffff880`03361e60 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsCommonCreateCallout+0x1d fffff880`06a1fd20 fffff800`036c5d41 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27 fffff880`03361d30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue CHKIMG_EXTENSION: !chkimg -lo 50 -d !Ntfs fffff8800137e463 - Ntfs!NtfsOpenFcbById+333 [ d0:f0 ] 1 error : !Ntfs (fffff8800137e463) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BIT STACK_COMMAND: .cxr 0xfffff88006a1f030 ; kb FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT Followup: memory_corruption[/FONT]

Upload a screenshot of your hard disk using CrystalDiskInfo:

CrystalDiskInfo - Software - Crystal Dew World

http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Make a hard drive test from the hard drive manufacturers website:

Hard Drive Diagnostic Procedure

Run Disk Check on your hard disk for file system errors and bad sectors on it:

http://www.sevenforums.com/tutorials/433-disk-check.html

Hard drive test both short and long with:

SeaTools for Windows

Also the DOS version of:

SeaTools for DOS

SeaTools for DOS tutorial

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Click to expand...

Information

Errors are sometimes found after 8 passes.

Tip

Do this test overnight, before going to bed.

alright both of the first 2 requests are uploaded as requested. the txt was too large to upload as a txt so i uploaded in a zip. the first one is the nfo 2nd is the txt.

steegz · Dec 28, 2012

so im running the test as the bsod happened again, been running the test for 30 minutes thus far and ran into errors going to continue running it to see if more errors but is there anything i can do besides going through the painful task of unplugging everything(due to where my desktop is located) and running the test with 1 stick in at a time? im not sure what the errors posted regarding the ram mean but anyone know if it specifies some how which stick is bad so i can replace?

koolkat77 · Dec 28, 2012

Those files are corrupted.

I've requested a friend to take a look at the RAM issues.

Please wait for a reply.

steegz · Dec 28, 2012

Thank you!

steegz · Dec 28, 2012

it says 65 errors im not sure what that means its on its 2nd almost 3rd pass.

Britton30 · Dec 28, 2012

Hi steegz, there is no advantage to running memtest past when an error is shown. The test write different values of specific types to various parts of RAM and expects ti to read back the exact value written. Testsing each RAM DIMM in each slot after any errors is done to try to determine if they are caused by the motherboard or, indeed, a bad RAM.

There is not a way for memtest to tell us which stick it is that throws errors.

I think if your PC is in such a place so hard to access it may be full of dust and dirt. Clean it out while swappinf the RAM around if so. Make sure BIOS recognises the RAM correctly as well.

steegz · Dec 28, 2012

yea recently cleaned it out its not in a tight area i play on 3 monitors so everything has to be unplugged to move the tower. inside is clean. looks like ill run mem test on 1 stick and so on and so forth to see if thats the issue. i pray its not the mobo the mobo is expensive lol. will post back with results.

Britton30 · Dec 28, 2012

Ok, that sounds good mate.

To better help us to help you would you please add your systems specs? Here's how:SystemInfo See Your System Specs Under System Manufacturer/Model Number add whether it is a desktop or laptop and whether self built. Very important

Log in to Seven Forums and you will be able to transfer the info directly to the specs page in your profile from within the System Info app.
After doing this your specs will be available in each of your posts. Click on My system Specs in the lower left of this post to see how it should look.

Full instructions are in the tutorial.
Interested in what PSU you have.

steegz · Dec 28, 2012

by the way britton how would i differ the ram from the mobo as far as which is the issue? im assuming if i run memtest on each of the sticks and get no errors that states its a problem with my mobo?

Britton30 · Dec 28, 2012

If all RAM gets errors in the same slot, that would be the board's fault. If one stick gets errors in any of the slots, that one RAM is bad.

steegz · Dec 28, 2012

so entire mobo wouldnt be bad if i find no errors in any of the sticks it would just be one of the slots had gone bad correct?

Britton30 · Dec 28, 2012

steegz said:
so entire mobo wouldnt be bad if i find no errors in any of the sticks it would just be one of the slots had gone bad correct?

Correct, but I wouldn't trust the board is a RAM slot is bad. RAM is connected to almost every other component on the board in some way.

steegz · Dec 28, 2012

did 2 passes on each stick of ram about to put the last one in. if nothing comes back its obvious its the mobo and ill be contacting asus regarding warranty. ill keep ya posted after this last stick's test

Britton30 · Dec 28, 2012

Mate, two passes is not enough.

bsod page fault in nonpaged area

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

R.I.P. 7/09/2014

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

R.I.P. 7/09/2014

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

R.I.P. 7/09/2014

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

R.I.P. 7/09/2014

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

R.I.P. 7/09/2014

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer