PAGE_FAULT_IN_NONPAGED_AREA Help

Page 1 of 2 12 LastLast

  1. Posts : 8
    Windows 7
       #1

    PAGE_FAULT_IN_NONPAGED_AREA Help


    I have been crashing constantly since I have installed a new mobo (ga-890fxa-ud) and a new processor (1090T). My OS is windows 7 64 bit home premium. I tried to read the mini dump files but couldn't because of the wrong symbols. Hopfully I can fix this blue screen of death .
      My Computer


  2. Posts : 140
    Windows 7 Home Premium 64bit
       #2

    Code:
    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    ffffb700`01000000    00000000`00000000    fffff800`0299a9da    00000000`00000007    fltmgr.sys    fltmgr.sys+50a2                    
    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    ffffffff`ffffff94    00000000`00000001    fffff880`041420eb    00000000`00000000    dxgkrnl.sys    dxgkrnl.sys+35274
    It seems your issue might be from disk corruption.

    Do the following and report back with your finding:

    Go to start menu and in search type cmd
    Right click cmd and select "run as administrator"
    Type chkdsk /r
    Let it run and hopefully it will correct your issues.

    Good luck!
      My Computer


  3. Posts : 13,354
    Windows 7 Professional x64
       #3

    If David's advice doesn't work, please enable driver verifier: Using Driver Verifier to identify issues with Drivers

    Also remove your ATI drivers and install a fresh copy: Global Provider of Innovative Graphics, Processors and Media Solutions | AMD

    ...Summary of the Dumps:
    Code:
    
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Debug session time: Tue Jul 20 21:31:13.844 2010 (UTC - 4:00)
    System Uptime: 0 days 0:00:21.124
    BugCheck 50, {ffffffffffffff94, 1, fffff880041420eb, 0}
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : memory_corruption
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  csrss.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Jul 20 19:02:01.619 2010 (UTC - 4:00)
    System Uptime: 0 days 0:04:27.102
    BugCheck 50, {ffffb70001000000, 0, fffff8000299a9da, 7}
    Probably caused by : memory_corruption ( nt!MiInsertVadCharges+10a )
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  dllhost.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
    
      My Computer


  4. Posts : 8
    Windows 7
    Thread Starter
       #4

    Thanks guys for helping me out. After i preformed chkdsk /r i crashed right away and now im performing the verify driver. Hopefully it can find what is wrong with my pc . Hopefully i don't have a broken graphic card, mobo or the processor that i bought
      My Computer


  5. Posts : 8
    Windows 7
    Thread Starter
       #5

    After doing the verifier driver i crashed couple times and then it would not take me to the desktop and continue crashing i had to go back in safe mode and turn it off. Keep saying a hardware/software problem turned of my pc here are the new mini dump files. I feel like I should return my new mother board, processor and graphic card
      My Computer


  6. Posts : 28,845
    Win 8 Release candidate 8400
       #6

    Eaglestrike7 said:
    After doing the verifier driver i crashed couple times and then it would not take me to the desktop and continue crashing i had to go back in safe mode and turn it off. Keep saying a hardware/software problem turned of my pc here are the new mini dump files. I feel like I should return my new mother board, processor and graphic card

    Eaglestrike Hi and welcome

    In an effort to expedite things I analyzed the most recent crash and it like the two that Jonathan_king did also points to memory corruption. Have you been asked to run a memory test yet?

    It is a bug check C1

    Usual causes: Device driver, Memory

    to test your ram

    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

    Be sure to turn the driver verifier off before you ruin the memory test.

    Ken




    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\072110-148824-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (6 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`03062000 PsLoadedModuleList = 0xfffff800`0329fe50
    Debug session time: Wed Jul 21 19:42:28.022 2010 (GMT-4)
    System Uptime: 0 days 0:20:41.973
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ....................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C1, {fffff98039398f10, fffff98039398ffd, f740f0, 24}
    
    Probably caused by : memory_corruption ( nt!MmFreeSpecialPool+383 )
    
    Followup: MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
    Special pool has detected memory corruption.  Typically the current thread's
    stack backtrace will reveal the guilty party.
    Arguments:
    Arg1: fffff98039398f10, address trying to free
    Arg2: fffff98039398ffd, address where bits are corrupted
    Arg3: 0000000000f740f0, (reserved)
    Arg4: 0000000000000024, caller is freeing an address where bytes after the end of the allocation have been overwritten
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xC1_24
    
    SPECIAL_POOL_CORRUPTION_TYPE:  24
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff800031d9783 to fffff800030d2600
    
    STACK_TEXT:  
    fffff880`031fbb18 fffff800`031d9783 : 00000000`000000c1 fffff980`39398f10 fffff980`39398ffd 00000000`00f740f0 : nt!KeBugCheckEx
    fffff880`031fbb20 fffff800`03205356 : 00000000`0000071f 00000000`74707249 00000000`0315bbe0 fffff800`03261480 : nt!MmFreeSpecialPool+0x383
    fffff880`031fbc50 fffff800`035771f6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExFreePool+0x9f3
    fffff880`031fbd00 fffff800`03377a86 : fffff980`00706b60 fffff980`00324b30 00000000`00000000 00000000`00000000 : nt!ViPoolDelayFreeTrimThreadRoutine+0x46
    fffff880`031fbd40 fffff800`030b0b06 : fffff880`02f64180 fffff980`00706b60 fffff880`02f6f040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`031fbd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MmFreeSpecialPool+383
    fffff800`031d9783 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!MmFreeSpecialPool+383
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0xC1_24_VRFK_nt!MmFreeSpecialPool+383
    
    BUCKET_ID:  X64_0xC1_24_VRFK_nt!MmFreeSpecialPool+383
    
    Followup: MachineOwner
    ---------
      My Computer


  7. Posts : 8
    Windows 7
    Thread Starter
       #7

    Were is the errors kept ( if any) after im done with memtest.

    thanks for all the help and patience
      My Computer


  8. Posts : 13,354
    Windows 7 Professional x64
       #8

    Any errors will be displayed on the screen. I believe there is a log somewhere, so I would look in C:\
      My Computer


  9. Posts : 8
    Windows 7
    Thread Starter
       #9

    I just finished my memtest and it didn't show any errors i allowed it to go up to 8 passes. So does it mean my drivers are at fault or my graphic card ati 5830?
      My Computer


  10. Posts : 8
    Windows 7
    Thread Starter
       #10

    After I uninstall my graphic card driver I got the same blue screen of death. Its pretty frustating crashing for 1 week and half I just don't know whats wrong
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About 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 23:48.
Find Us