BSOD related with ntoskrnl.exe

[petezahut]

I just installed windows 7 64-bit on my new computer and everytime I'd do something like install avast anti-virus or add gadgets too quickly, i'd get these blue screens.

I used BlueScreenView to see what the problem was, and the most common problem driver is this ntoskrnl.exe

I'm pretty sure there was no problems during the install, and I'm sure all my drivers are updated (I used this Uniblue Drive Scanner, which said nothing was out of date).

Just in case this information is needed: I'm running 7 Professional, with an AMD Phenom II x4 965 Processor (3.40 ghz). I've got 4 gigs of DDR3 Ram (and I went into my BIOS and upped the voltage from 1.5 to 1.9 cause I read somewhere that someone used that as a quick fix for the BSODs). And I'm using a M4A79XTD Evo mobo and a ATI Radeon HD 4800 video card (DirectX 11)

I've attached the dmp files from my minidump folder. Thanks in advance to anyone who can help me out.

 

[zigzag3143]

I just installed windows 7 64-bit on my new computer and everytime I'd do something like install avast anti-virus or add gadgets too quickly, i'd get these blue screens.

I used BlueScreenView to see what the problem was, and the most common problem driver is this ntoskrnl.exe

I'm pretty sure there was no problems during the install, and I'm sure all my drivers are updated (I used this Uniblue Drive Scanner, which said nothing was out of date).

Just in case this information is needed: I'm running 7 Professional, with an AMD Phenom II x4 965 Processor (3.40 ghz). I've got 4 gigs of DDR3 Ram (and I went into my BIOS and upped the voltage from 1.5 to 1.9 cause I read somewhere that someone used that as a quick fix for the BSODs). And I'm using a M4A79XTD Evo mobo and a ATI Radeon HD 4800 video card (DirectX 11)

I've attached the dmp files from my minidump folder. Thanks in advance to anyone who can help me out.

hi and welcome

pretty straight what the problem is but not what caused it. These were likely caused by memory corruption.. the faulty driver cannot be determined

I would
download memtestx86 and run it for 5 passes

run a system file check to verify and repair your system files
type cmd in search>right click and run as admin>sfc /scannow
if you are overlocking stop


Ken J+

123109-27690-01.dmp    12/31/2009 3:14:39 AM    MEMORY_MANAGEMENT    0x0000001a    00000000`00041790    fffffa80`02210040    00000000`0000ffff    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    
123109-16879-01.dmp    12/31/2009 1:43:09 AM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    fffff6dc`50036488    00000000`00000000    fffff800`028a2ae2    00000000`00000005    ntoskrnl.exe    ntoskrnl.exe+71f00                    
123109-19422-01.dmp    12/31/2009 1:33:54 AM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    fffff6f3`400000f0    00000000`00000000    fffff800`0289eae2    00000000`00000005    ntoskrnl.exe    ntoskrnl.exe+71f00                    
123109-25537-01.dmp    12/31/2009 2:05:28 AM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    fffffa98`0169504b    00000000`00000000    fffff800`028d4d3b    00000000`00000005    ntoskrnl.exe    ntoskrnl.exe+71f00                    
123109-26941-01.dmp    12/31/2009 3:13:20 AM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    fffffe80`06200118    00000000`00000000    fffff800`02d6864c    00000000`00000007    ntoskrnl.exe    ntoskrnl.exe+71f00                    
123109-26192-01.dmp    12/31/2009 2:07:11 AM    PFN_LIST_CORRUPT    0x0000004e    00000000`00000099    00000000`0001680e    00000000`00000000    00000000`0001690e    ntoskrnl.exe    ntoskrnl.exe+71f00

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\123109-16879-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
[B]Built by: 7600.16385.amd64fre.win7_rtm.090713-1255[/B]
Machine Name:
Kernel base = 0xfffff800`0281d000 PsLoadedModuleList = 0xfffff800`02a5ae50
Debug session time: Thu Dec 31 04:42:04.693 2009 (GMT-5)
System Uptime: 0 days 0:03:08.410
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff6dc50036488, 0, fffff800028a2ae2, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1c2 )

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

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

P[B]AGE_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.[/B]
Arguments:
Arg1: fffff6dc50036488, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800028a2ae2, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ac50e0
 fffff6dc50036488 

FAULTING_IP: 
nt!MiAgeWorkingSet+1c2
fffff800`028a2ae2 488b19          mov     rbx,qword ptr [rcx]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880031167a0 -- (.trap 0xfffff880031167a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff6dc50036488
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800028a2ae2 rsp=fffff88003116930 rbp=007fffdc50036488
 r8=0000000000000001  r9=fffff80002a19b40 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!MiAgeWorkingSet+0x1c2:
fffff800`028a2ae2 488b19          mov     rbx,qword ptr [rcx] ds:fffff6dc`50036488=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000290cb91 to fffff8000288ef00

STACK_TEXT:  
fffff880`03116638 fffff800`0290cb91 : 00000000`00000050 fffff6dc`50036488 00000000`00000000 fffff880`031167a0 : nt!KeBugCheckEx
fffff880`03116640 fffff800`0288cfee : 00000000`00000000 00000980`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40f5b
fffff880`031167a0 fffff800`028a2ae2 : 00000003`00000000 9bf00000`b28d9963 00000000`00000000 00000000`000081bf : nt!KiPageFault+0x16e
fffff880`03116930 fffff800`0290fa0e : fffff800`02a19b40 fffff880`00000001 00000000`00000001 fffff880`03116bb0 : nt!MiAgeWorkingSet+0x1c2
fffff880`03116ae0 fffff800`028a36e2 : 00000000`000000bd 00000000`00000000 fffffa80`00000000 00000000`00000006 : nt! ?? ::FNODOBFM::`string'+0x49926
fffff880`03116b80 fffff800`028a396f : 00000000`00000008 fffff880`03116c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03116bd0 fffff800`02b32166 : fffffa80`039f9040 00000000`00000080 fffffa80`0396e890 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03116d40 fffff800`0286d486 : fffff880`02d63180 fffffa80`039f9040 fffff880`02d6dfc0 63832450`1b2c508b : nt!PspSystemThreadStartup+0x5a
fffff880`03116d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiAgeWorkingSet+1c2
fffff800`028a2ae2 488b19          mov     rbx,qword ptr [rcx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiAgeWorkingSet+1c2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+1c2

BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+1c2

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

 

[petezahut]

Alright thanks for the info.

I went into my BIOS and (since I recently changed the voltage to 1.9) reset it back to AUTO. The memtest ran for about 200% (I'll do a longer one tonight) and found no problems.

However I did the sfc /scannow thing, and it says "Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log......etc."

Do you think I shouldn't worry about it? And to just wait and see if it'll still blue screen?