Page Fault and Memory Management after video card installation

ColossalMenace · 02 Aug 2011

I ran memtest for 6 passes with both RAM sticks in and didn't get any errors, and I haven't overclocked anything with my system as far as i know. I went to the bios and found the DRAM Voltage but there is no "Manual" setting, it just says "Auto", but it will let me put in a number for it so i'm not really sure whats going on there, and it tells me Min: 1.20000V Max:2.20000V Interval=0.00625V and Standard=1.50000V. I'll go to the blue screen posting page you linked and follow the steps on there and add another post here soon.

P.S. I have my motherboard manual, luckily for me I was smart and decided to keep EVERYTHING that came with my comp parts in a safe place :P

ColossalMenace · 02 Aug 2011

Hey just restarted my comp and got a black screen with "The file is possibly corrupt. The file header checksum does not match the computed checksum." No clue what that means, but thought i'd let ya know.

ColossalMenace · 02 Aug 2011

Here is the additional info you wanted, lemme know if i did anything wrong.

Dave76 · 03 Aug 2011

I'm trying to find out if you used the old RAM test called "memtest" or the newer version called "memtest86+", can you confirm?

If you used "memtest" then you need to D/L 'memtest86+' and run it again.

You have to be completely sure of these voltage settings, if you increase the CPU NB voltage (CPU integrated memory controller) too high it can burn up your CPU.
Haven't seen one set at "CPU/NB Offset Voltage 1.175 [Auto]" before without someone raising the value. Stock default voltage setting is 1.100v.
If yours is at 1.175v, it is safe but, needs to be raised a little bit. If it is higher or lower, we won't be able to get the desired result or it might damage the CPU.
Can you open your BIOS and take a picture of that page with a camera and post it here?
Better to be 100% sure.

The JCGriff files look fine, will look at them in a little while.

You need to confirm the voltage settings before we can make any adjustments, this is the first step that needs to be taken.

ColossalMenace · 04 Aug 2011

I used memtest86+ and i've attached photos of the "AI tweaker" page of my BIOS. Also, if it matter or not, the BSOD's have become much more frequent now, to the point where i really need to use my laptop to do these posts. Seems to happen quicker when i try to play WoW or something.

Dave76 · 04 Aug 2011

Thanks for the BIOS pics.
When you have more than 4GB RAM, you will likely need to adjust the RAM settings. More voltage is usually required.

Go to your BIOS and change:

DRAM RAS# ACT Time to 22CLK.
The first four RAM timings will be:
8
8
8
22

DRAM Command Rate to 2T.

Change the CPU & NB Voltage Mode to 'manual', then to 1.20v.

Save and Exit BIOS.

Run memtest86+ for a minimum of 8 passes, best to run overnight.

Let us know the results.

ColossalMenace · 12 Aug 2011

Hey sorry i haven't responded for a while, was on vacation and just got back a couple days ago. I changed all the voltages and it seemed to have fixed my computer, because it started up and ran like a champ for 2 days straight with no problems. Today however, i had left it on overnight and when i started it up this morning it worked for about 2-3 minutes then i got a BSOD, and now when i start it up it's stuck in the repair screen where it tells me it can't figure out why windows won't work. I'm going to let it run memtest when i leave today and let it go through the night, and i'll let you know what comes out of that.

Dave76 · 12 Aug 2011

Hope you had a good vacation.

Glad to hear it is becoming a bit more stable.

Can you post the new crash files?
All the information files as outlined here: Blue Screen of Death (BSOD) Posting Instructions
This will give us additional information to work with, and see if anything new has occurred.

Did you change the RAM timings?
DRAM RAS# ACT Time to 22CLK.
The first four RAM timings will be:
8
8
8
22

If memtest86+ finishes all the tests through test#7 (started test#8) you can stop it.
Won't hurt anything to let it run all night.

ColossalMenace · 12 Aug 2011

hey didn't get a chance to end up starting memtest before i had to leave for work so i'll just let it run tonight. The only way i could figure out how to get out of the endless recovery startup loop was to do another clean install of windows. I did that and it still gave me another blue screen, so here are the files. If i did anything wrong lemme know.

Dave76 · 13 Aug 2011

Please confirm questions from post#18.

Same IRQL_NOT_LESS_OR_EQUAL (a) as before, not much help.

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: fffff0800308c608, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002cd6112, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efe0e8
 fffff0800308c608 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerWaitTest+212
fffff800`02cd6112 48894108        mov     qword ptr [rcx+8],rax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880030b03d0 -- (.trap 0xfffff880030b03d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8009de5c00 rbx=0000000000000000 rcx=fffff0800308c600
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cd6112 rsp=fffff880030b0560 rbp=fffffa80077e9c28
 r8=fffff8800308a301  r9=0000000000000002 r10=0000000000000092
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KiTimerWaitTest+0x212:
fffff800`02cd6112 48894108        mov     qword ptr [rcx+8],rax ds:fffff080`0308c608=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cccbe9 to fffff80002ccd640

STACK_TEXT:  
fffff880`030b0288 fffff800`02cccbe9 : 00000000`0000000a fffff080`0308c608 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`030b0290 fffff800`02ccb860 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`077e9c28 : nt!KiBugCheckDispatch+0x69
fffff880`030b03d0 fffff800`02cd6112 : fffff880`02f64180 fffffa80`07bfa060 fffff880`030b0630 fffff880`030b06c0 : nt!KiPageFault+0x260
fffff880`030b0560 fffff800`02cd8ead : fffffa80`077e9c20 fffffa80`07bfa168 fffffa80`07bfa168 00000000`00000102 : nt!KiTimerWaitTest+0x212
fffff880`030b05e0 fffff800`02cd8dee : 00000003`c309932e fffff880`030b0c58 00000000`00019492 fffff880`0308b7c8 : nt!KiProcessExpiredTimerList+0x6d
fffff880`030b0c30 fffff800`02cd8bd7 : 00000001`2e1bd1c1 00000001`00019492 00000001`2e1bd10d 00000000`00000092 : nt!KiTimerExpiration+0x1be
fffff880`030b0cd0 fffff800`02cc536a : fffff880`03088180 fffff880`03093040 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff880`030b0d80 00000000`00000000 : fffff880`030b1000 fffff880`030ab000 fffff880`030b0d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTimerWaitTest+212
fffff800`02cd6112 48894108        mov     qword ptr [rcx+8],rax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiTimerWaitTest+212

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+212

BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+212

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

Same MEMORY_MANAGEMENT (1a) as before, so we are dealing with the same issues.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff68000002090
Arg3: 26400801bace1867
Arg4: fffffa800a05d4b0

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


BUGCHECK_STR:  0x1a_41201

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  Skype.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f3f2de to fffff80002ee2c40

STACK_TEXT:  
fffff880`090f69b8 fffff800`02f3f2de : 00000000`0000001a 00000000`00041201 fffff680`00002090 26400001`bace1867 : nt!KeBugCheckEx
fffff880`090f69c0 fffff800`02eae831 : ffffc0e4`746c6644 fffff880`090f6a60 00000000`00000000 26400001`bace1867 : nt! ?? ::FNODOBFM::`string'+0x14382
fffff880`090f6a00 fffff800`02eae4ca : fffffa80`0a05d4b0 fffffa80`09f77060 fffffa80`09f77060 00000000`00412000 : nt!MiQueryAddressState+0x2b1
fffff880`090f6a50 fffff800`031bd724 : 00000000`00000040 00000000`00413000 fffffa80`0a05d4b0 00000000`00000000 : nt!MiQueryAddressSpan+0xaa
fffff880`090f6ac0 fffff800`02ee1ed3 : ffffffff`ffffffff fffffa80`09f741f0 00000000`0018ebb0 00000000`0008e2a8 : nt!NtQueryVirtualMemory+0x382
fffff880`090f6bb0 00000000`7705154a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e288 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7705154a


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
3 errors : !nt (fffff80002ee21bd-fffff80002ee2a8d)
fffff80002ee21b0  44  0f  29  60  90  44  0f  29  68  a0  44  0f  29 *78  b0  44 D.)`.D.)h.D.)x.D
...
fffff80002ee2230  44  0f  29  60  90  44  0f  29  68  a0  44  0f  29 *78  b0  44 D.)`.D.)h.D.)x.D
...
fffff80002ee2a80  f9  ff  ff  fb  e8  07  95  0b  00  65  0f  ae  14 *2d  80  01 .........e...-..

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

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

Let's see what memtest86+ has to say.