Page Fault and Memory Management after video card installation

[ColossalMenace]

Hey all

A couple of weeks ago I upgraded video cards from a Galaxy GeForce 210 (that I had put in my custom built from a previous Dell) to a EVGA NVIDIA GeForce GTX 460. Everything worked fine at first but shortly after installing it i've started to get page fault in nonpaged area and memory management BSOD's and i'm not sure if that has anything to do with the new graphics card or if that is just a coincidence. I tried switching out the RAM to different slots, and even did a clean install with Windows 7 but i'm still getting blue screened at random points, sometimes i'll be able to get on and play World of Warcraft or whatever else for hours and be completely fine, and other times it will blue screen after just 5 minutes of surfing the web. I've also tried reinstalling the video drivers and motherboard drivers. I'm currently running Memtest on it and hopefully i'll see if it's a problem with the memory or not, but any other advice would be appreciated and if someone could point me in the right direction on how to do so, i can post the dump files if it blue screens again. Thanks!

Hardware

CPU: AMD Phenom II Black Edition
Motherboard: ASUS M4A87TD EVO
Video Card: EVGA NVIDIA GeForce GTX 460
PSU: Thermaltake TR2 600W
RAM: Sector 5 8GB DDR3 (2x4GB) (Manufacturer is Patriot)

 

[yowanvista]

Test this video card with OCCT
http://www.sevenforums.com/tutorials/160729-nvidia-video-card-test-occt.html
Did you update to the latest drivers from Nvidia?
NVIDIA DRIVERS 275.33 WHQL

 

[ColossalMenace]

i'll let memtest finish it's pass with this stick then i'll run the card and check the drivers

 

[ColossalMenace]

So i downloaded that driver update you linked and it seemed to work for a while, but then the next day it started blue screening again, i've tried taking one RAM stick out and then the other and it blue screens with each of them in. I even tried putting my old video card back in the computer and about 5 minutes after loading into my desktop it blue screened again. Any ideas?

 

[Dave76]

Did you run Memtest86+ with both RAM cards installed?
RAM - Test with Memtest86+

D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Have you been checking your temperatures?
Use Core Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

 

[ColossalMenace]

I attached all the snips you asked for, and one of the CPUZ window as well, i'm going to try and figure out how to get into the dump files and next time it crashes I'll post them so you can have a look. Thanks again!

 

[Dave76]

Did you run memtest86+ for testing your RAM?
There is a link in my last post that goes to a tutorial that will explain everything.
Check it here: RAM - Test with Memtest86+

The CPUZ snips help, everything there looks good.
Still need the voltages from BIOS.
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

With more than 4GB RAM you will need a memory controller voltage bump, once you verify the voltages we can make some adjustments to get it stable.

You can D/L your motherboard manual here: ASUS M4A87TD EVO

For the integrated memory controller voltage, called CPU/NB voltage, check page 2-11 and 2-15 in your manual.
Tell us the voltage reading listed in your BIOS.
Should be 1.150v.


To ensure minidumps are enabled:
Go to Start, in the Search Box type: 'sysdm.cpl' then press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

Blue Screen of Death (BSOD) Posting Instructions

 

[ColossalMenace]

Minidumps are now enabled to the specifications you posted and i went and found the voltages, they are;

CPU & NB Voltage Mode [Offset]

CPU Offset Voltages 1.404 [Auto]

CPU/NB Offset Voltage 1.175 [Auto]

P.S. I'm not sure if this has anything to do with anything thats going on, but after i changed everything and went to let it start up it gave me a black screen with "Bootmgr image is corrupt", I just hit the restart button and everything worked fine but just thought I should throw it out there.

 

[ColossalMenace]

Hey found the dump files, attached the last four of them to this post, thanks!

 

[Dave76]

Can your post the rest of the information files as outlined here: Blue Screen of Death (BSOD) Posting Instructions

This will give us additional information to work with.

Have you overclocked anything on your system?

Can you confirm that you tested your RAM with memtest86+?
This is important, your are having RAM faults, running the right test will tell us where the problem is from.

Also need your DRAM voltage, this is important as well, with 8GB ram you will need some adjustments, and I need to know where to start from.
BTW, voltages listed in CPUZ are not actual they are the recommended voltages, go to your BIOS and check under 'AI Tweaker' > DRAM Voltage.
If it only says 'Auto' then select 'Manual' and it should tell you a voltage.

If you don't have your motherboard manual, download it from my post above, you're going to need it.
After you tell me the DRAM voltage we are going to have to re-set some of the timings and adjust the voltages.
You can find this information on pages 2-11, 2-13 and 2-15 in your mobo manual.


Your last crash was STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
This indicates that a severe memory management error occurred.

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa800570a7a0
Arg3: 0000000000000845
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002e7d459 to fffff80002ecdd00

STACK_TEXT:  
fffff880`06a5f498 fffff800`02e7d459 : 00000000`0000001a 00000000`00041790 fffffa80`0570a7a0 00000000`00000845 : nt!KeBugCheckEx
fffff880`06a5f4a0 fffff800`02f0012a : fffffa80`09327060 00000000`00000000 f9900002`14799c66 f9900002`14799867 : nt! ?? ::FNODOBFM::`string'+0x21546
fffff880`06a5f5b0 fffff800`02f015d9 : 00000000`00000000 00000000`0c398fff 00000000`00000000 00000000`002120e6 : nt!MiDeleteVirtualAddresses+0x929
fffff880`06a5f770 fffff800`031e48b1 : fffffa80`099ce010 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`06a5f890 fffff960`001159f2 : ffff0800`00000001 fffffa80`08e81830 00000000`00000001 fffff800`02ed08a4 : nt!MiUnmapViewOfSection+0x1b1
fffff880`06a5f950 fffff960`0024eaab : 00000000`00000000 00000000`00000000 00000000`00004b05 00000000`00000000 : win32k!SURFACE::bDeleteSurface+0x502
fffff880`06a5faa0 fffff960`002cf4a8 : fffff900`c1ba48e0 00000000`00000001 fffff900`c1cb4cc0 00000000`7e12135d : win32k!GreDereferenceObject+0x7b
fffff880`06a5fae0 fffff960`002d04c7 : 00000000`00000000 00000000`7e12135d fffff900`c1ba48e0 00000000`03dfa92c : win32k!SFMLOGICALSURFACE::DeInitialize+0x88
fffff880`06a5fb20 fffff960`0022cb73 : 00000000`00000000 fffff900`c00c0010 fffff900`c1ba48e0 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`06a5fb60 fffff960`0024de0c : 00000000`00000001 00000000`00000001 fffff880`06a5fca0 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`06a5fba0 fffff800`02eccf93 : fffffa80`093987e0 fffffa80`093993e0 ffffffff`fffd67f0 fffffa80`093993e0 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`06a5fc20 000007fe`fe354a3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03bef9f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fe354a3a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!SURFACE::bDeleteSurface+502
fffff960`001159f2 eb05            jmp     win32k!SURFACE::bDeleteSurface+0x509 (fffff960`001159f9)

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  win32k!SURFACE::bDeleteSurface+502

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4df2dbd1

FAILURE_BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+502

BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+502

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

Your next crash blames memory corruption also:

STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver
Followup: memory_corruption

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ffffff8000000320, 2, 0, fffff880049582be}

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : memory_corruption

[B][COLOR="Red"]Followup: memory_corruption[/COLOR][/B]
---------

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffff8000000320, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880049582be, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310c100
 ffffff8000000320 

CURRENT_IRQL:  2

FAULTING_IP: 
dxgmms1!VidSchiProcessCompletedQueuePacketInternal+396
fffff880`049582be 48a12003000080f7ffff mov rax,qword ptr [FFFFF78000000320h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880030b0690 -- (.trap 0xfffff880030b0690)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880030b07f0 rbx=0000000000000000 rcx=fffffa8008fcc7b0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880049582be rsp=fffff880030b0820 rbp=fffffa80071c25f0
 r8=fffff880030b07f0  r9=0000000000000000 r10=fffffa8008fcc7d0
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x396:
fffff880`049582be 48a12003000080f7ffff mov rax,qword ptr [FFFFF78000000320h] ds:c780:fffff780`00000320=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002edc2a9 to fffff80002edcd00

STACK_TEXT:  
fffff880`030b0548 fffff800`02edc2a9 : 00000000`0000000a ffffff80`00000320 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`030b0550 fffff800`02edaf20 : 00000000`000186a0 00000000`00000000 00000000`0001cf1f fffffa80`07193c40 : nt!KiBugCheckDispatch+0x69
fffff880`030b0690 fffff880`049582be : fffffa80`07193c40 fffffa80`071c25f0 fffffa80`09001000 fffffa80`0818c000 : nt!KiPageFault+0x260
fffff880`030b0820 fffff880`049577da : fffffa80`00000000 fffffa80`00000000 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x396
fffff880`030b08e0 fffff880`04956e00 : fffffa80`00000000 fffff880`11258c35 00000000`00000000 00000000`00000001 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x3b6
fffff880`030b0980 fffff880`04956c4c : 00000000`00000001 fffffa80`08fcc010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff880`030b09d0 fffff880`0485d1cf : fffffa80`0816f480 00000000`00000000 00000000`00000022 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`030b0a20 fffff880`1113f138 : fffffa80`0818c000 fffffa80`0818c000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`030b0a50 fffffa80`0818c000 : fffffa80`0818c000 00000000`00000000 00000000`00000000 fffff880`1113f0cb : nvlddmkm+0xce138
fffff880`030b0a58 fffffa80`0818c000 : 00000000`00000000 00000000`00000000 fffff880`1113f0cb fffffa80`0818c000 : 0xfffffa80`0818c000
fffff880`030b0a60 00000000`00000000 : 00000000`00000000 fffff880`1113f0cb fffffa80`0818c000 00000000`00000000 : 0xfffffa80`0818c000


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
7 errors : !nt (fffff80002edc27d-fffff80002edcb4d)
fffff80002edc270  44  0f  29  60  90  44  0f  29  68  a0  44  0f  29 *78  b0  44 D.)`.D.)h.D.)x.D
...
fffff80002edc2f0  44  0f  29  60  90  44  0f  29  68  a0  44  0f  29 *78  b0  44 D.)`.D.)h.D.)x.D
...
fffff80002edc6b0  84  00  00  00  00 *08  66  66  0f  1f  84  00  00  00  00  00 ......ff........
...
fffff80002edca20  0f  6f  50  70  66  44  0f  6f  98  80  00  00  00 *6e  44  0f .oPpfD.o.....nD.
...
fffff80002edcaa0  0f  1f  84  00  00 *08  00  00  66  66  66  66  66  66  66  0f ........fffffff.
fffff80002edcab0  1f  84  00  00  00 *08  00  66  0f  1f  84  00  00  00  00  00 .......f........
...
fffff80002edcb40  f9  ff  ff  fb  e8  97  64  0b  00  65  0f  ae  14 *2d  80  01 ......d..e...-..

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

[B]FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE[/B]

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

[B][COLOR="red"]Followup: memory_corruption[/COLOR][/B]
---------

These are the first two crashes, neither are much help, they have very little information.
Not much info here, STOP 0x1000000A: IRQL_NOT_LESS_OR_EQUAL

*******************************************************************************
*                                                                             *
*                        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: fffff00003026f78, 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: fffff80002e98312, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bc100
 fffff00003026f78 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerExpiration+f2
fffff800`02e98312 48894808        mov     qword ptr [rax+8],rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9caa0 -- (.trap 0xfffff80000b9caa0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff00003026f70 rbx=0000000000000000 rcx=fffff80003002328
rdx=0000000000000005 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e98312 rsp=fffff80000b9cc30 rbp=000000000000f905
 r8=fffffa8004f5dc20  r9=00000000000000c0 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!KiTimerExpiration+0xf2:
fffff800`02e98312 48894808        mov     qword ptr [rax+8],rcx ds:6460:fffff000`03026f78=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e8c2a9 to fffff80002e8cd00

STACK_TEXT:  
fffff800`00b9c958 fffff800`02e8c2a9 : 00000000`0000000a fffff000`03026f78 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9c960 fffff800`02e8af20 : fffff800`02fffe80 fffff780`00000320 00000000`0000f905 00000002`50c48534 : nt!KiBugCheckDispatch+0x69
fffff800`00b9caa0 fffff800`02e98312 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00007429 : nt!KiPageFault+0x260
fffff800`00b9cc30 fffff800`02e981c7 : 00000000`b9f12ac0 00000000`0000f905 00000000`b9f12abb 00000000`00000005 : nt!KiTimerExpiration+0xf2
fffff800`00b9ccd0 fffff800`02e84a2a : fffff800`02fffe80 fffff800`0300dcc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTimerExpiration+f2
fffff800`02e98312 48894808        mov     qword ptr [rax+8],rcx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiTimerExpiration+f2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+f2

BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+f2

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

 

[ColossalMenace]

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

 

[ColossalMenace]

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]

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

 

[Dave76]

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]

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]

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]

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]

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]

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]

Please confirm questions from post#18.


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

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

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