omidontop

updated

14 years ago

O

omidontop

7 Posts

0

46258

April 9th, 2013 15:00

Frequent Blue Screens in Windows 8 after installing a SSD disk in the mSATA slot of the Dell XPS One 2710

Hello!

I own a XPS One 2710 which I bought the summer of 2012. It came with a 1TB HDD and no SSD disks whatsoever. I have recently bought an Intel 525 Series mSATA 180GB SSD disk and did a clean installation of Windows 8 on it. Everything went well and I can successfully boot my Windows and use it. I have all the drivers installed including the Chipset drivers. The problem is, every once in a while ( about a few times a day ) I suddenly get the Blue Screen of Death and my computer restarts. Right after it restarts it seems like the SSD is lost for a short while as my computers goes to booting from the Hard Disk instead and cannot find the SSD before I restart a couple of times or Power cycle the computer. The only clue I have is the KERNEL_DATA_INPAGE_ERROR words underneath the Blue Screen. Any ideas what might be causing this?

Thanks in advance!

  • 1525

    1

    Posted April 19th, 2013 19:00

    There's huge amount of memory that is corrupted that would cause inconsistencies and eventually may crash the system. It is recommended to do a clean re-installation to avoid further issue. Specially with important files and documents. And If you have any further questions or concerns, feel free to send me a DM and I would be happy to help.

    Thanks and Regards,

    DELL_Andrew F

    Dell Social Media and Community Professional

    For easy access to drivers, manuals and product updates, please visit our Support Site.

  • omidontop

    7 Posts

    1525

    0

    Posted April 9th, 2013 17:00

    Dear Andrew,

    Thank you very much for your response. I confirm that I have all the latest drivers, the A10 version of the BIOS flashed and the latest firmware on the SSD. Am I missing anything?

    Here's the dump file analysis results :


    Executable search path is: c:\windows\i386
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    Machine Name:
    Kernel base = 0xfffff803`6c60f000 PsLoadedModuleList = 0xfffff803`6c8d9a60
    Debug session time: Tue Apr 9 01:12:23.655 2013 (UTC + 2:00)
    System Uptime: 0 days 0:35:18.317
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................................................
    Loading User Symbols
    Loading unloaded module list
    ................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7A, {fffff6fc40009008, ffffffffc00000c0, 1b9a0860, fffff88001201000}

    ^QGetPointerFromAddress: unable to read from fffff8036c965170
    !uit*** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    !exitProbably caused by : memory_corruption

    Followup: memory_corruption
    ---------

    !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    KERNEL_DATA_INPAGE_ERROR (7a)
    The requested page of kernel data could not be read in. Typically caused by
    a bad block in the paging file or disk controller error. Also see
    KERNEL_STACK_INPAGE_ERROR.
    If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
    it means the disk subsystem has experienced a failure.
    If the error status is 0xC000009A, then it means the request failed because
    a filesystem failed to make forward progress.
    Arguments:
    Arg1: fffff6fc40009008, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc00000c0, error status (normally i/o status code)
    Arg3: 000000001b9a0860, current process (virtual address for lock type 3, or PTE
    )
    Arg4: fffff88001201000, virtual address that could not be in-paged (or PTE conte
    nts if arg1 is a PTE address)

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


    ERROR_CODE: (NTSTATUS) 0xc00000c0 - This device does not exist.

    BUGCHECK_STR: 0x7a_c00000c0

    DEFAULT_BUCKET_ID: CODE_CORRUPTION

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff8036c75f9fd to fffff8036c68a040

    STACK_TEXT:
    fffff880`1a18e3c8 fffff803`6c75f9fd : 00000000`0000007a fffff6fc`40009008 ffffff
    ff`c00000c0 00000000`1b9a0860 : nt!KeBugCheckEx
    fffff880`1a18e3d0 fffff803`6c67b2c3 : 00000000`00000002 fffff880`1a18e530 fffff8
    03`6c95ea80 fffff880`1a18e520 : nt! ?? ::FNODOBFM::`string'+0x2409e
    fffff880`1a18e4b0 fffff803`6c6c4e1c : fffffa80`0b35eb00 fffff803`6c95ea80 000000
    00`c0033333 00000000`00000000 : nt!MiIssueHardFault+0x183
    fffff880`1a18e580 fffff803`6c671a82 : 00000000`00000000 fffffa80`0b35eb00 000000
    00`00000000 00000000`00000000 : nt!MmAccessFault+0x7fc
    fffff880`1a18e6c0 fffff803`6ca42549 : 00000000`00000000 fffffa80`0b35eb00 fffff8
    80`012001e8 00000000`00000801 : nt!MiLockCode+0x256
    fffff880`1a18e7d0 fffff880`013c4993 : fffff880`1a18e938 00000000`00000000 fffffa
    80`05114d40 fffffa80`046d4ae0 : nt!MmResetDriverPaging+0xdd
    fffff880`1a18e800 fffff880`013d101a : 00000000`00000003 00000000`00000000 fffff8
    80`00ed1180 fffff803`000e0082 : volmgr!VmpRestoreExtensionDriver+0x23
    fffff880`1a18e830 fffff880`013d0c3b : 00000000`0000000f fffffa80`046ce5a0 000000
    00`00000000 00000000`00000000 : volmgr!VmpPartitionRemovedImmediate+0x46
    fffff880`1a18e8f0 fffff880`013c58a8 : 00000000`00000000 00000000`00000000 fffffa
    80`046d4990 fffff803`6c6e93f3 : volmgr!VmpPartitionRemoved+0x4f
    fffff880`1a18e930 fffff803`6c614c52 : fffffa80`046ca2f0 00000000`00000000 000000
    00`00000000 00000000`00000000 : volmgr! ?? ::FNODOBFM::`string'+0x144
    fffff880`1a18e960 fffff803`6c996f17 : 00000000`00000000 fffffa80`049ebb90 000000
    00`00000010 fffff803`6c693700 : nt!IoSynchronousCallDriver+0x52
    fffff880`1a18e9c0 fffff880`0137281a : fffffa80`051ffc60 fffff880`01360550 fffff8
    80`1a18eaa9 fffff880`01360550 : nt!IoForwardIrpSynchronously+0x47
    fffff880`1a18e9f0 fffff880`013655f9 : fffffa80`051ffc60 fffff880`1a18eaa9 fffffa
    80`051ffc60 fffff880`01360500 : partmgr!PmTakePartition+0xbe
    fffff880`1a18ea40 fffff803`6c67545b : fffffa80`049ebb90 fffff880`01360550 fffffa
    80`051ffb10 fffffa80`085913a0 : partmgr! ?? ::FNODOBFM::`string'+0xc1c
    fffff880`1a18eb10 fffff803`6c6c2391 : fffff803`6c893080 fffffa80`0b35eb00 fffff8
    03`6c6753fc fffff803`6c893000 : nt!IopProcessWorkItem+0x5f
    fffff880`1a18eb80 fffff803`6c631521 : fffffa80`00ca00ca 00000000`00000080 fffff8
    03`6c6c2250 fffffa80`0b35eb00 : nt!ExpWorkerThread+0x142
    fffff880`1a18ec10 fffff803`6c66fdd6 : fffff880`00ed1180 fffffa80`0b35eb00 fffffa
    80`039da040 fffffa80`039dc940 : nt!PspSystemThreadStartup+0x59
    fffff880`1a18ec60 00000000`00000000 : 00000000`00000000 00000000`00000000 000000
    00`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


    STACK_COMMAND: kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !volmgrx
    fffff88001201000-fffff8800120100a 11 bytes - volmgrx!GsDriverEntry+2c
    [ cc cc cc cc cc cc 66 66:00 00 00 00 00 00 00 00 ]
    fffff88001201010-fffff88001201013 4 bytes - volmgrx!_security_check_cookie
    (+0x10)
    [ 48 3b 0d e9:00 00 00 00 ]
    fffff88001201015 - volmgrx!_security_check_cookie+5 (+0x05)
    [ 02:00 ]
    fffff88001201017-fffff88001201024 14 bytes - volmgrx!_security_check_cookie
    +7 (+0x02)
    [ 75 12 48 c1 c1 10 66 f7:00 00 00 00 00 00 00 00 ]
    fffff88001201027-fffff8800120102d 7 bytes - volmgrx!_security_check_cookie+
    17 (+0x10)
    [ 48 c1 c9 10 e9 b8 15:00 00 00 00 00 00 00 ]
    fffff88001201030-fffff88001201069 58 bytes - volmgrx!_security_check_cookie
    +20 (+0x09)
    [ 90 90 90 90 90 90 90 90:00 00 00 00 00 00 00 00 ]
    fffff8800120106b-fffff8800120106f 5 bytes - volmgrx!VMX_IO_DISK_EXTENT::Bro
    adcastIrp+2b (+0x3b)
    [ 0f 85 58 82 01:00 00 00 00 00 ]
    fffff88001201071-fffff88001201088 24 bytes - volmgrx!VMX_IO_DISK_EXTENT::Br
    oadcastIrp+31 (+0x06)
    [ 48 8b 41 30 48 89 74 24:00 00 00 00 00 00 00 00 ]
    fffff8800120108a-fffff88001201094 11 bytes - volmgrx!VMX_IO_DISK_EXTENT::Br
    oadcastIrp+4a (+0x19)
    [ 48 8b d8 48 85 c0 0f 84:00 00 00 00 00 00 00 00 ]
    fffff88001201096-fffff88001201097 2 bytes - volmgrx!VMX_IO_DISK_EXTENT::Bro
    adcastIrp+56 (+0x0c)
    [ ba 28:00 00 ]
    fffff8800120109b - volmgrx!VMX_IO_DISK_EXTENT::BroadcastIrp+5b (+0x05)
    [ b9:00 ]
    fffff8800120109d - volmgrx!VMX_IO_DISK_EXTENT::BroadcastIrp+5d (+0x02)
    [ 02:00 ]
    fffff880012010a0-fffff880012010aa 11 bytes - volmgrx!VMX_IO_DISK_EXTENT::Br
    oadcastIrp+60 (+0x03)
    [ 41 b8 56 6d 43 72 ff 15:00 00 00 00 00 00 00 00 ]
    fffff880012010ac-fffff880012010b6 11 bytes - volmgrx!VMX_IO_DISK_EXTENT::Br
    oadcastIrp+6c (+0x0c)
    [ 4c 8b d8 48 85 c0 0f 84:00 00 00 00 00 00 00 00 ]
    fffff880012010b8-fffff880012010c9 18 bytes - volmgrx!VMX_IO_DISK_EXTENT::Br
    oadcastIrp+78 (+0x0c)
    [ 48 89 38 4c 89 78 18 4c:00 00 00 00 00 00 00 00 ]
    fffff880012010cd-fffff880012010d0 4 bytes - volmgrx!VMX_IO_DISK_EXTENT::Bro
    adcastIrp+8d (+0x15)
    [ 48 8d 0d 9c:00 00 00 00 ]
    fffff880012010d4-fffff880012010da 7 bytes - volmgrx!VMX_IO_DISK_EXTENT::Bro
    adcastIrp+94 (+0x07)
    [ 89 43 30 4c 8b 85 b8:00 00 00 00 00 00 00 ]
    fffff880012010de-fffff880012010df 2 bytes - volmgrx!VMX_IO_DISK_EXTENT::Bro
    adcastIrp+9e (+0x0a)
    [ 49 8b:00 00 ]
    fffff880012010e1-fffff88001201128 72 bytes - volmgrx!VMX_IO_DISK_EXTENT::Br
    oadcastIrp+a1 (+0x03)
    [ 48 89 42 b8 49 8b 40 08:00 00 00 00 00 00 00 00 ]
    fffff8800120112c-fffff88001201142 23 bytes - volmgrx!VMX_IO_DISK_EXTENT::Br
    oadcastIrp+ec (+0x4b)
    [ 48 8b d3 48 89 48 f0 48:00 00 00 00 00 00 00 00 ]
    fffff88001201144-fffff8800120117b 56 bytes - volmgrx!VMX_IO_DISK_EXTENT::Br
    oadcastIrp+104 (+0x18)
    [ 48 8b 74 24 40 48 8b 5c:00 00 00 00 00 00 00 00 ]
    fffff8800120117d-fffff8800120119d 33 bytes - volmgrx!VmxpDiskExtentBroadcas
    tIrpCompletionRoutine+d (+0x39)
    [ 48 8b da 49 8b f8 48 8b:00 00 00 00 00 00 00 00 ]
    fffff8800120119f-fffff880012011a8 10 bytes - volmgrx!VmxpDiskExtentBroadcas
    tIrpCompletionRoutine+2f (+0x22)
    [ 33 d2 48 8b cf ff 15 8e:00 00 00 00 00 00 00 00 ]
    fffff880012011aa-fffff880012011b0 7 bytes - volmgrx!VmxpDiskExtentBroadcast
    IrpCompletionRoutine+3a (+0x0b)
    [ 48 8b 5c 24 30 b8 16:00 00 00 00 00 00 00 ]
    fffff880012011b3-fffff880012011d4 34 bytes - volmgrx!VmxpDiskExtentBroadcas
    tIrpCompletionRoutine+43 (+0x09)
    [ c0 48 83 c4 20 5f c3 90:00 00 00 00 00 00 00 00 ]
    fffff880012011d6-fffff880012011da 5 bytes - volmgrx!VMX_IO_DISK_EXTENT::Que
    ryRepresentativeDiskExtent+16 (+0x23)
    [ 0f 85 5c 81 01:00 00 00 00 00 ]
    fffff880012011dc-fffff88001201215 58 bytes - volmgrx!VMX_IO_DISK_EXTENT::Qu
    eryRepresentativeDiskExtent+1c (+0x06)
    [ 48 8b c1 48 83 c4 20 5b:00 00 00 00 00 00 00 00 ]
    fffff88001201219-fffff8800120122e 22 bytes - volmgrx!VmxReadWrite+19 (+0x3d
    )
    [ 4c 8b 39 48 8b f2 4c 8b:00 00 00 00 00 00 00 00 ]
    fffff88001201230-fffff88001201231 2 bytes - volmgrx!VmxReadWrite+30 (+0x17)

    [ 7e 01:00 00 ]
    fffff88001201233-fffff8800120123f 13 bytes - volmgrx!VmxReadWrite+33 (+0x03
    )
    [ 4b 8d 04 26 49 3b 47 10:00 00 00 00 00 00 00 00 ]
    fffff88001201241-fffff88001201250 16 bytes - volmgrx!VmxReadWrite+41 (+0x0e
    )
    [ 48 89 5c 24 70 48 89 7c:00 00 00 00 00 00 00 00 ]
    fffff88001201252-fffff88001201259 8 bytes - volmgrx!VmxReadWrite+52 (+0x11)

    [ 48 85 ff 0f 84 05 7d 01:00 00 00 00 00 00 00 00 ]
    fffff8800120125b-fffff88001201265 11 bytes - volmgrx!VmxReadWrite+5b (+0x09
    )
    [ ff 47 14 48 8b cf ff 15:00 00 00 00 00 00 00 00 ]
    fffff88001201267-fffff8800120126f 9 bytes - volmgrx!VmxReadWrite+67 (+0x0c)

    [ 48 8b d8 48 85 c0 0f 84:00 00 00 00 00 00 00 00 ]
    fffff88001201273-fffff88001201287 21 bytes - volmgrx!VmxReadWrite+73 (+0x0c
    )
    [ 33 c0 c6 43 50 01 48 89:00 00 00 00 00 00 00 00 ]
    fffff8800120128b-fffff88001201290 6 bytes - volmgrx!VmxReadWrite+8b (+0x18)

    [ 48 8d 05 ce 92 01:00 00 00 00 00 00 ]
    fffff88001201292-fffff880012012b0 31 bytes - volmgrx!VmxReadWrite+92 (+0x07
    )
    [ 48 89 03 48 8b 46 08 4c:00 00 00 00 00 00 00 00 ]
    fffff880012012b4-fffff880012012be 11 bytes - volmgrx!VmxReadWrite+b4 (+0x22
    )
    [ 48 8b d3 48 89 43 28 48:00 00 00 00 00 00 00 00 ]
    fffff880012012c2-fffff880012012cf 14 bytes - volmgrx!VmxReadWrite+c2 (+0x0e
    )
    [ 48 89 43 38 8b 46 10 89:00 00 00 00 00 00 00 00 ]
    fffff880012012d3-fffff880012012df 13 bytes - volmgrx!VmxReadWrite+d3 (+0x11
    )
    [ 48 89 43 48 0f b6 45 02:00 00 00 00 00 00 00 00 ]
    fffff880012012e1-fffff880012012e5 5 bytes - volmgrx!VmxReadWrite+e1 (+0x0e)

    [ 03 4c 89 ab b0:00 00 00 00 00 ]
    fffff880012012e9-fffff880012012ef 7 bytes - volmgrx!VmxReadWrite+e9 (+0x08)

    [ 0f 94 c0 48 89 b3 b8:00 00 00 00 00 00 00 ]
    fffff880012012f3-fffff880012012f9 7 bytes - volmgrx!VmxReadWrite+f3 (+0x0a)

    [ 88 43 52 48 8b 86 b8:00 00 00 00 00 00 00 ]
    fffff880012012fd-fffff88001201317 27 bytes - volmgrx!VmxReadWrite+fd (+0x0a
    )
    [ 80 48 03 01 48 8b 4b 30:00 00 00 00 00 00 00 00 ]
    fffff8800120131a-fffff8800120131e 5 bytes - volmgrx!VmxReadWrite+11a (+0x1d
    )
    [ 48 8b ac 24 80:00 00 00 00 00 ]
    fffff88001201322-fffff8800120134f 46 bytes - volmgrx!VmxReadWrite+122 (+0x0
    8)
    [ 48 83 c4 40 41 5f 41 5e:00 00 00 00 00 00 00 00 ]
    fffff88001201351-fffff88001201385 53 bytes - volmgrx!VmxReadWrite+151 (+0x2
    f)
    [ cc 90 90 90 90 90 90 90:00 00 00 00 00 00 00 00 ]
    fffff88001201389-fffff8800120138c 4 bytes - volmgrx!VmxpReadWriteCompletion
    Routine+29 (+0x38)
    [ 48 8b b1 b8:00 00 00 00 ]
    fffff88001201390-fffff880012013a7 24 bytes - volmgrx!VmxpReadWriteCompletio
    nRoutine+30 (+0x07)
    [ 48 89 46 30 48 8b 41 68:00 00 00 00 00 00 00 00 ]
    fffff880012013a9-fffff880012013ad 5 bytes - volmgrx!VmxpReadWriteCompletion
    Routine+49 (+0x19)
    [ 48 8b 01 4c 8b:00 00 00 00 00 ]
    WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [
    num_lines]' to view entire output.
    3719 errors : !volmgrx (fffff88001201000-fffff88001201fff)

    MODULE_NAME: memory_corruption

    IMAGE_NAME: memory_corruption

    FOLLOWUP_NAME: memory_corruption

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MEMORY_CORRUPTOR: LARGE_4096

    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE_4096

    BUCKET_ID: MEMORY_CORRUPTION_LARGE_4096

    Followup: memory_corruption
    ---------
  • 1525

    0

    Posted April 9th, 2013 17:00

    Hi omindontop,

    Welcome to the Community!

    You Can check on this link:

    lt.dell.com/.../lt.aspx

    Issue may have been caused by incorrect driver. Please update your firmware and device drivers from our support site.

    lt.dell.com/.../lt.aspx

    To get the root cause of the blue screen, we need to analyze the dump file.

    How to read the small memory dump files that Windows creates for debugging

    lt.dell.com/.../lt.aspx

    Thanks and Regards,

    DELL_Andrew F

    Dell Social Media and Community Professional

    For easy access to drivers, manuals and product updates, please visit our Support Site.

  • omidontop

    7 Posts

    1525

    0

    Posted April 11th, 2013 14:00

    Anything??

  • omidontop

    7 Posts

    1525

    0

    Posted April 20th, 2013 06:00

    Dear Andrew, 

    Thank you very much for the reply. You are right. I returned the module and asked for a new one and the new one works fine so fat. I guess it was defective when I received it or it might've been damaged as I wasn't so careful with the ESD precautions. 

  • 1525

    0

    Posted April 22nd, 2013 17:00

    Hi omindontop,

    You are always welcome. Good to know that all is well now on your end. If you have any further questions or concerns, feel free to reach out to us anytime and we're glad to be of help.

    Again, thanks for choosing dell.

    Thanks and Regards,

    DELL_Andrew F

    Dell Social Media and Community Professional

    For easy access to drivers, manuals and product updates, please visit our Support Site.