BSOD in Sony Vaio with KERNEL_DATA_INPAGE_ERROR

Page 1 of 3 123 LastLast

  1. Posts : 9
    Windows 7 Home Basic 64-Bit
       #1

    BSOD in Sony Vaio with KERNEL_DATA_INPAGE_ERROR


    PROBLEM: I own a Sony Vaio, Model VPCEH25EN purchased in 2011, warranty expired. From last couple of months, I am having intermittent Blue screen issue, often with a KERNEL_DATA_INPAGE_ERROR. I first tried a Windows Update and Vaio Update to update all drivers, but it did not help. Then I removed all data from my hard drive and did a factory setting from Vaio Care, that did not help either. Rather BSOD is happening more frequently. I also run CHKDSK and Vaio Hardware Diagnostics; they run without errors. Sometimes when I restart after a BSOD, I do see an "Operating System Not Found" or a Disk error but that is uncommon; most often it restarts as normal (except usual warning that the system was not shut down properly). My feeling is Blue Screen occurs when I try multitasking e.g. opening several tabs in browser or opening something when a program is running for long. Also, the laptop has become slower in general.

    I was about to give up until I find this forum. Find attached the DUMP file obtained using Forum instructions. Please excuse me if I have been naive or unclear, I will be happy to provide more details as needed. Thanks!

    - Jha
    Last edited by scientistjha; 03 Jan 2013 at 22:27.
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Welcome

    Try updating your video card drivers and see if that helps.

    METHOD:
    Click on the Start ► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to; NVIDIA and reboot the system and reboot the system. Delete remnants of its drivers/older drivers using Driver Fusion.

    Drivers - Clean Left over Files after Uninstalling

    Link: NVIDIA Driver Downloads - Automatically Detect NVIDIA Products

       Warning
    Do not install BETA drivers:
    BSOD Report
    Code:
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff8800f3c4d85, fffff88008c66f88, fffff88008c667e0}
    
    Probably caused by : nvlddmkm.sys ( nvlddmkm+114d85 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8800f3c4d85, The address that the exception occurred at
    Arg3: fffff88008c66f88, Exception Record Address
    Arg4: fffff88008c667e0, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    nvlddmkm+114d85
    fffff880`0f3c4d85 488b01          mov     rax,qword ptr [rcx]
    
    EXCEPTION_RECORD:  fffff88008c66f88 -- (.exr 0xfffff88008c66f88)
    Cannot read Exception record @ fffff88008c66f88
    
    CONTEXT:  fffff88008c667e0 -- (.cxr 0xfffff88008c667e0)
    rax=0000000000000000 rbx=fffffa800456d000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000040000 rdi=0000000000000000
    rip=fffff8800f3c4d85 rsp=fffff88008c671c0 rbp=fffffa8005555000
     r8=0000000000000004  r9=fffffa8005555000 r10=fffffa800456d000
    r11=0000000000010000 r12=0000000000000000 r13=0000000000000004
    r14=0000000000000000 r15=0000000000100110
    iopl=0         nv up ei pl nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
    nvlddmkm+0x114d85:
    fffff880`0f3c4d85 488b01          mov     rax,qword ptr [rcx] ds:002b:00000000`00000000=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000000
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0b100
    GetUlongFromAddress: unable to read from fffff80002d0b1c0
     0000000000000000 Nonpaged pool
    
    FOLLOWUP_IP: 
    nvlddmkm+114d85
    fffff880`0f3c4d85 488b01          mov     rax,qword ptr [rcx]
    
    BUGCHECK_STR:  0x7E
    
    LAST_CONTROL_TRANSFER:  from fffffa800456d000 to fffff8800f3c4d85
    
    STACK_TEXT:  
    fffff880`08c671c0 fffffa80`0456d000 : 00000980`00000000 0000007f`fffffff8 fffff880`0431e995 fffffa80`05797440 : nvlddmkm+0x114d85
    fffff880`08c671c8 00000980`00000000 : 0000007f`fffffff8 fffff880`0431e995 fffffa80`05797440 00000000`00000002 : 0xfffffa80`0456d000
    fffff880`08c671d0 0000007f`fffffff8 : fffff880`0431e995 fffffa80`05797440 00000000`00000002 fffffa80`05797010 : 0x00000980`00000000
    fffff880`08c671d8 fffff880`0431e995 : fffffa80`05797440 00000000`00000002 fffffa80`05797010 00000000`00000000 : 0x0000007f`fffffff8
    fffff880`08c671e0 00000000`00000004 : 00000000`00000000 00000000`00000000 fffff880`00f00250 fffffa80`043d0950 : dxgmms1!VidSchFlushAdapter+0x2cd
    fffff880`08c67310 00000000`00000000 : 00000000`00000000 fffff880`00f00250 fffffa80`043d0950 fffffa80`043d0950 : 0x4
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nvlddmkm+114d85
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d5eb1fc
    
    STACK_COMMAND:  .cxr 0xfffff88008c667e0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_nvlddmkm+114d85
    
    BUCKET_ID:  X64_0x7E_nvlddmkm+114d85
    
    Followup: MachineOwner
    ---------
    
    2: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0f2b0000 fffff880`0ff21f80   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Fri Feb 18 23:53:00 2011 (4D5EB1FC)
        CheckSum:         00C8109E
        ImageSize:        00C71F80
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Upload a screenshot of your hard disk using CrystalDiskInfo and Summary tab using Speccy:

    Make a hard drive test from the hard drive manufacturers website:

    Run Disk Check on your hard disk for file system errors and bad sectors on it:
      My Computer


  3. Posts : 9
    Windows 7 Home Basic 64-Bit
    Thread Starter
       #3

    Thanks; I am going to do that now. One question: Is it okay to download drivers from vaio website for my laptop model. For some reason, I do not see NVIDIA GEFORCE 410m drivers on nvidia website earlier. Also, I was checking, when I see "operating system not found" error, bios do not see Hard Disk drive (HDD). But as I said, it doesnt happen very often. Is it likely a HDD failure or some loose connection issue?
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #4

    scientistjha said:
    Is it okay to download drivers from vaio website for my laptop model.
    Yup, sure.
    scientistjha said:
    Also, I was checking, when I see "operating system not found" error, bios do not see Hard Disk drive (HDD). But as I said, it doesnt happen very often. Is it likely a HDD failure or some loose connection issue?
    Sounds like a hard drive failure.

    Try reseating the Power and Sata cables.

    Await the snips from Speccy & Crystal Disk.
      My Computer


  5. Posts : 9
    Windows 7 Home Basic 64-Bit
    Thread Starter
       #5

    Find attached the output of Speecy and CrystalDisk. I am going to run the Hard Disk diagnostic now and will update on that later. Thanks again!
    Attachment 248508
    Attachment 248509
      My Computer


  6. Posts : 15,026
    Windows 10 Home 64Bit
       #6

    They look OK.

    Thanks.
      My Computer


  7. Posts : 9
    Windows 7 Home Basic 64-Bit
    Thread Starter
       #7

    Thanks, so does it mean Hard Disk has not failed?

    I am still trying to run the hard drive diagnostics, I have a Hitachi HDD, for some reason the WinDFT is not allowing me to run diagnostics on primary drive. But I had run CHKDSK and Vaio hardware diagnostics and had no errors. I have reinstalled the NVIDIA drivers, no blue screen so far. So far so good, will update when I get blue screen again.
      My Computer


  8. Posts : 15,026
    Windows 10 Home 64Bit
       #8

    Give Seatools a shot.

    Hard drive test both short and long with:
    Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

    The goal is to test all the RAM sticks and all the motherboard slots.


    Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

    If you get errors, stop the test and continue with the next step.

    1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
    *Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
    If this stick passes the test then go to step #3.

    2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
    *If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
    *If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
    3. Test the next stick of RAM (stick #2) in the next motherboard slot.
    *If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
    *If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
    4. If you find a stick that passes the test, test it in all the other motherboard slots.

    If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

    In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
       Information
    Errors are sometimes found after 8 passes.

       Tip
    Do this test overnight, before going to bed.
      My Computer


  9. Posts : 9
    Windows 7 Home Basic 64-Bit
    Thread Starter
       #9

    I did run a Long Generic Test from Seatools and the Hard Drive passed the test. Does that mean that the disk failure is very unlikely? I was doing some more web-search on this and seemingly re-seating hard drive might solve the issue. I need to try that with memtest86+ too ( wanted to avoid opening the laptop cover so far)
      My Computer


  10. Posts : 15,026
    Windows 10 Home 64Bit
       #10

    Yes you could try re-seating the hard drive.
      My Computer


 
Page 1 of 3 123 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 18:09.
Find Us