new surface pro3: continous crashing BSOD

Discussion in 'Microsoft Surface Pro 3' started by ayman, Jun 17, 2015.

  1. ayman

    ayman New Member

    Joined:
    Jun 17, 2015
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    My Device:
    SPro3
    hay i bought a surface pro 3 couple days ago and aim having extremely bad experience with it
    the screen start to whizzle and after a few minute i get BSOD this is constant and i dont know if its a hardware or software issues i cant keep on for a while before it crashes
    i posted pictures on some of the thing that happens to me and there's a rare case of black wallpaper and some stuff on driver i didn't understand i put a pic of it
    i want to know is this hardware or software issue and is it fixable ?


    hers a WhoCrashed program report

    Crash Dump Analysis
    Crash dump directory: C:\WINDOWS\Minidump

    Crash dumps are enabled on your computer.
    On Wed 17/06/15 11:24:04 ص GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\061715-10031-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
    Bugcheck code: 0x4E (0x7, 0x108D96, 0x40000000000, 0x0)
    Error: PFN_LIST_CORRUPT
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that the page frame number (PFN) list is corrupted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    On Wed 17/06/15 11:24:04 ص GMT your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x28DC6)
    Bugcheck code: 0x4E (0x7, 0x108D96, 0x40000000000, 0x0)
    Error: PFN_LIST_CORRUPT
    file path: C:\WINDOWS\system32\drivers\ntfs.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT File System Driver
    Bug check description: This indicates that the page frame number (PFN) list is corrupted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

    On Mon 15/06/15 12:26:09 م GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\061515-10625-01.dmp
    This was probably caused by the following module: hidi2c.sys (0xFFFFF8011B75E0A8)
    Bugcheck code: 0x50 (0xFFFFF8011F763B28, 0x0, 0xFFFFF8011B75E0A8, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\WINDOWS\system32\drivers\hidi2c.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: I2C HID Miniport Driver
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

    On Sun 14/06/15 08:05:50 م GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\061415-6156-01.dmp
    This was probably caused by the following module: mrvlpcie8897.sys (0xFFFFF8001B828E53)
    Bugcheck code: 0xD1 (0x98A, 0x2, 0x0, 0xFFFFF8001B828E53)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\WINDOWS\system32\drivers\mrvlpcie8897.sys
    product: Marvell LE Driver
    company: Marvell Semiconductors Inc.
    description: Marvell LE Driver for the WiFiCLass Stack
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mrvlpcie8897.sys (Marvell LE Driver for the WiFiCLass Stack, Marvell Semiconductors Inc.).
    Google query: Marvell Semiconductors Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

    On Sun 14/06/15 07:41:32 م GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\061415-6734-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
    Bugcheck code: 0x50 (0xFFFFF6FB41000000, 0x0, 0xFFFFF80294CA00E8, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    On Sun 14/06/15 05:49:04 م GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\061415-6125-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
    Bugcheck code: 0xA (0xFFFFD000C0C94F6C, 0xF, 0x1, 0xFFFFF80394876CD6)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    On Sun 14/06/15 05:43:45 م GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\061415-7406-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0xA9E9)
    Bugcheck code: 0x24 (0xB500190637, 0xFFFFD000850D3478, 0xFFFFD000850D2C80, 0xFFFFF8001CEA1D53)
    Error: NTFS_FILE_SYSTEM
    file path: C:\WINDOWS\system32\drivers\ntfs.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT File System Driver
    Bug check description: This indicates a problem occurred in the NTFS file system.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

    On Sun 14/06/15 05:41:18 م GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\061415-7328-01.dmp
    This was probably caused by the following module: mrvlpcie8897.sys (mrvlpcie8897+0x1F1E4)
    Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF801944A21E4, 0xFFFFE00111DDA040, 0x1FFEEC9CED18)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\WINDOWS\system32\drivers\mrvlpcie8897.sys
    product: Marvell LE Driver
    company: Marvell Semiconductors Inc.
    description: Marvell LE Driver for the WiFiCLass Stack
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mrvlpcie8897.sys (Marvell LE Driver for the WiFiCLass Stack, Marvell Semiconductors Inc.).
    Google query: Marvell Semiconductors Inc. KMODE_EXCEPTION_NOT_HANDLED

    On Sun 14/06/15 05:38:41 م GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\061415-6984-01.dmp
    This was probably caused by the following module: intelpep.sys (intelpep+0x1DFC)
    Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF801CE5DE324, 0xFFFFF801CE7D1A00, 0xFFFFF801DE3E5DFC)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\WINDOWS\system32\drivers\intelpep.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Intel Power Engine Plugin
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


    Conclusion
    9 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

    mrvlpcie8897.sys (Marvell LE Driver for the WiFiCLass Stack, Marvell Semiconductors Inc.)

    20150615_151252.jpg 20150615_151244.jpg
     

    Attached Files:

  2. hughlle

    hughlle Super Moderator Staff Member

    Joined:
    Jul 7, 2014
    Messages:
    2,698
    Likes Received:
    422
    Trophy Points:
    83
    First step is to do a refresh of your system, or better yet remove everything and reinstall (find it under update and recovery). Fingers crossed your machine can stay on long enough to perform this.
     
  3. ayman

    ayman New Member

    Joined:
    Jun 17, 2015
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    My Device:
    SPro3
    i did a refresh and it still the same problem

    the screen tends to go giggly alot you can see it in the attachment
     
  4. Telstar1948

    Telstar1948 Active Member

    Joined:
    Jul 12, 2013
    Messages:
    435
    Likes Received:
    78
    Trophy Points:
    28
    Location:
    Columbia, Missouri
    My Device:
    Surface Book
    Try a reset then; that will wipe everything and install Windows...then the updates start! If it's still giving you problems after resetting it, sounds like hardware issues...exchange/replace the SP3
     
  5. ayman

    ayman New Member

    Joined:
    Jun 17, 2015
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    My Device:
    SPro3
    by reset do you mean reinstall win8 ?
     
  6. samurai

    samurai Member

    Joined:
    Jan 21, 2014
    Messages:
    55
    Likes Received:
    8
    Trophy Points:
    8
    Location:
    Germany
    My Device:
    SPro3
    Screenshot (3).png Yes, It's the second option.
     

Share This Page

Search tags for this page

surface pro 3 bugcheck

,
surface pro 3 firmware causes bsod
,
surface pro3 bsod