none
Tricky problem: PAGE FAULT IN NON PAGED AREA, disk.sys is involved.

    Question

  • First of all, my OS is Windows 7 Pro SP1 x64. My computer's specs include a nvidia RAID 0 (2x500GB WD drives) which I partitioned in 3 partitions, and of course W7 created the 4th (the System Reserved one). I've installed the OS about 2 months ago, and ran it without problems. A few days ago, I've taken a spare HDD (a WD 250GB) and connected as SATA drive on one of the free ports, Windows detected it fine. Today I ran some backup jobs with Acronis and saved the backup archives on the spare HDD.

    Everything was fine until I decided to take the spare drive out and mount it in a newly bought HDD rack. Turned off the computer, disconnected the drive (i repeat, it's not part of the RAID matrix, is just plain SATA) and then switched on the computer ... Surprise ... some error occurred on boot, causing a BSOD with the message PAGE FAULT IN NON PAGED AREA, and after reboot the startup repair popped up, trying for almost 10 minutes to fix the boot, then saying that it couldn't be fixed.

    Ok, boot problems are common, so I did the usual stuff, started cmd from recovery, ran the bootrec.exe /fixmbr, /fixboot, bootsect /nt60 ... everything completing successfuly... until I restarted my rig in normal mode, then the BSOD appeared again.

    Other symptoms are:

    1. bootrec's os search cannot find any OS, but I can see my files through cmd.

    2. cannot access Safe Mode, it's stuck at disk.sys and then BSODs.

    3. connecting the spare drive again makes windows to boot properly.

     

    What I can't understand is why Windows is so "in love" with that drive since that HDD wasn't there when OS was installed. And ... the other thing ... I really need that drive mounted in the rack a.s.a.p. since I'm traveling a lot.

     

    Thank you !

     


    • Edited by EduardBrn Tuesday, December 27, 2011 10:01 PM corrections
    Tuesday, December 27, 2011 9:57 PM

Answers

  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    PAGE_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.
    Arguments:
    Arg1: fffff88003526001, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff880017f748d, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000000, (reserved)
    Debugging Details:
    ------------------
    Unable to load image \SystemRoot\system32\DRIVERS\nvsmu.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvsmu.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvsmu.sys
    Could not read faulting driver name
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002509100
     fffff88003526001 
    FAULTING_IP: 
    nvsmu+248d
    fffff880`017f748d 428a940002100000 mov     dl,byte ptr [rax+r8+1002h]
    MM_INTERNAL_CODE:  0
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    TRAP_FRAME:  fffff880025de4e0 -- (.trap 0xfffff880025de4e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000000007efff rbx=0000000000000000 rcx=000000000006f0ff
    rdx=fffff880034a60ff rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880017f748d rsp=fffff880025de678 rbp=fffffa80037d5240
     r8=fffff880034a6000  r9=fffffa800378e4b0 r10=0000000000000000
    r11=0000000000000753 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    nvsmu+0x248d:
    fffff880`017f748d 428a940002100000 mov     dl,byte ptr [rax+r8+1002h] ds:0020:fffff880`03526001=??
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff800022829fc to fffff800022d6c40
    STACK_TEXT:  
    fffff880`025de378 fffff800`022829fc : 00000000`00000050 fffff880`03526001 00000000`00000000 fffff880`025de4e0 : nt!KeBugCheckEx
    fffff880`025de380 fffff800`022d4d6e : 00000000`00000000 fffff880`03526001 fffffa80`0378e300 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4611f
    fffff880`025de4e0 fffff880`017f748d : fffff880`017f72a5 fffffa80`037dff00 00000000`00000000 fffffa80`0378e360 : nt!KiPageFault+0x16e
    fffff880`025de678 fffff880`017f72a5 : fffffa80`037dff00 00000000`00000000 fffffa80`0378e360 fffffa80`0378e4b0 : nvsmu+0x248d
    fffff880`025de680 fffffa80`037dff00 : 00000000`00000000 fffffa80`0378e360 fffffa80`0378e4b0 00000000`00000000 : nvsmu+0x22a5
    fffff880`025de688 00000000`00000000 : fffffa80`0378e360 fffffa80`0378e4b0 00000000`00000000 fffff880`025de6d0 : 0xfffffa80`037dff00
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nvsmu+248d
    fffff880`017f748d 428a940002100000 mov     dl,byte ptr [rax+r8+1002h]
    SYMBOL_STACK_INDEX:  3
    SYMBOL_NAME:  nvsmu+248d
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nvsmu
    IMAGE_NAME:  nvsmu.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ba8196f
    FAILURE_BUCKET_ID:  X64_0x50_nvsmu+248d
    BUCKET_ID:  X64_0x50_nvsmu+248d
    Followup: MachineOwner
    ---------
    1: kd> lmvm nvsmu
    start             end                 module name
    fffff880`017f5000 fffff880`01800000   nvsmu    T (no symbols)           
        Loaded symbol image file: nvsmu.sys
        Image path: \SystemRoot\system32\DRIVERS\nvsmu.sys
        Image name: nvsmu.sys
        Timestamp:        Tue Mar 23 02:29:19 2010 (4BA8196F)
        CheckSum:         0000A94D
        ImageSize:        0000B000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    ---------------------------------------------------------------------------------------
    As I see, your BSOD was caused by nvsmu.sys driver. More about it: http://www.runscanner.net/lib/nvsmu.sys.html
    I see also that the driver dates from 2010. Start by updating the driver. If you are unable to find new ones, I would recommend contacting NVIDIA or your manufacturer Technical Support for to get it.
    Once updated, check results.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. 

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    Saturday, December 31, 2011 3:29 PM

All replies

  • Hi,

     

    I would like to verify if you have replaced with the new HDD rack. Please update the BIOS, chipset and hard drive driver from manufacture.

     

    Meanwhile, please upload your %SystemRoot%\Minidump file to SkyDrive for further research.

     

    Best Regards,

    Niki


    Niki Han

    TechNet Community Support

    Thursday, December 29, 2011 9:05 AM
    Moderator
  • No, disconnecting the drive from sata cable then putting it into a rack and reconnecting via USB didn't helped. Bios is the latest version, drivers are the latest stable ones from nVidia. So ... nothing beta, nothing outdated.

    I have only one minidump, it's uploaded here.


    • Edited by EduardBrn Thursday, December 29, 2011 9:30 AM
    Thursday, December 29, 2011 9:29 AM
  • Hi,

     

    From the dump file, I notice the issue is probably caused by nvsmu.sys

     

    Nvsmu.sys with description NVIDIA nForce(TM) SMU Microcontroller Driver is a driver file from company NVIDIA Corporation belonging to product NVIDIA nForce(TM) PCA Driver.

     

    Please uninstall your current Nvidia driver from Device Manager and load the driver from computer manufacture's website such as HP, DELL first. If the driver doesn't work, then go to Nvidia website and use the NVIDIA Smart Scan tool to detect the motherboard.

     

    http://www.nvidia.com/Download/ScannForce.aspx?lang=en-us

    Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

     

    Best Regards,

    Niki


    Niki Han

    TechNet Community Support

    Thursday, December 29, 2011 10:12 AM
    Moderator
  • The drivers from the manufacturer site are old and with poor compatibility with Windows 7. I have the latest driver from nvidia. And I did an uninstall and reinstall of all nvidia drivers, even for the video card, before asking here.
    Thursday, December 29, 2011 10:25 AM
  • PAGE_FAULT_IN_NONPAGED_AREA isn't particularly forthcoming as to its cause,
     
     
    Have you tried analyzing the dumps after enabling driver verifier?
     
     

    -- Mike Burr
    Technology
    Friday, December 30, 2011 3:26 PM
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    PAGE_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.
    Arguments:
    Arg1: fffff88003526001, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff880017f748d, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000000, (reserved)
    Debugging Details:
    ------------------
    Unable to load image \SystemRoot\system32\DRIVERS\nvsmu.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvsmu.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvsmu.sys
    Could not read faulting driver name
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002509100
     fffff88003526001 
    FAULTING_IP: 
    nvsmu+248d
    fffff880`017f748d 428a940002100000 mov     dl,byte ptr [rax+r8+1002h]
    MM_INTERNAL_CODE:  0
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    TRAP_FRAME:  fffff880025de4e0 -- (.trap 0xfffff880025de4e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000000007efff rbx=0000000000000000 rcx=000000000006f0ff
    rdx=fffff880034a60ff rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880017f748d rsp=fffff880025de678 rbp=fffffa80037d5240
     r8=fffff880034a6000  r9=fffffa800378e4b0 r10=0000000000000000
    r11=0000000000000753 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    nvsmu+0x248d:
    fffff880`017f748d 428a940002100000 mov     dl,byte ptr [rax+r8+1002h] ds:0020:fffff880`03526001=??
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff800022829fc to fffff800022d6c40
    STACK_TEXT:  
    fffff880`025de378 fffff800`022829fc : 00000000`00000050 fffff880`03526001 00000000`00000000 fffff880`025de4e0 : nt!KeBugCheckEx
    fffff880`025de380 fffff800`022d4d6e : 00000000`00000000 fffff880`03526001 fffffa80`0378e300 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4611f
    fffff880`025de4e0 fffff880`017f748d : fffff880`017f72a5 fffffa80`037dff00 00000000`00000000 fffffa80`0378e360 : nt!KiPageFault+0x16e
    fffff880`025de678 fffff880`017f72a5 : fffffa80`037dff00 00000000`00000000 fffffa80`0378e360 fffffa80`0378e4b0 : nvsmu+0x248d
    fffff880`025de680 fffffa80`037dff00 : 00000000`00000000 fffffa80`0378e360 fffffa80`0378e4b0 00000000`00000000 : nvsmu+0x22a5
    fffff880`025de688 00000000`00000000 : fffffa80`0378e360 fffffa80`0378e4b0 00000000`00000000 fffff880`025de6d0 : 0xfffffa80`037dff00
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nvsmu+248d
    fffff880`017f748d 428a940002100000 mov     dl,byte ptr [rax+r8+1002h]
    SYMBOL_STACK_INDEX:  3
    SYMBOL_NAME:  nvsmu+248d
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nvsmu
    IMAGE_NAME:  nvsmu.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ba8196f
    FAILURE_BUCKET_ID:  X64_0x50_nvsmu+248d
    BUCKET_ID:  X64_0x50_nvsmu+248d
    Followup: MachineOwner
    ---------
    1: kd> lmvm nvsmu
    start             end                 module name
    fffff880`017f5000 fffff880`01800000   nvsmu    T (no symbols)           
        Loaded symbol image file: nvsmu.sys
        Image path: \SystemRoot\system32\DRIVERS\nvsmu.sys
        Image name: nvsmu.sys
        Timestamp:        Tue Mar 23 02:29:19 2010 (4BA8196F)
        CheckSum:         0000A94D
        ImageSize:        0000B000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    ---------------------------------------------------------------------------------------
    As I see, your BSOD was caused by nvsmu.sys driver. More about it: http://www.runscanner.net/lib/nvsmu.sys.html
    I see also that the driver dates from 2010. Start by updating the driver. If you are unable to find new ones, I would recommend contacting NVIDIA or your manufacturer Technical Support for to get it.
    Once updated, check results.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. 

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    Saturday, December 31, 2011 3:29 PM