Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Please help BSOD critical structure corruption windows 10


  • Please log in to reply
1 reply to this topic

#1 wusgnb

wusgnb

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:09:38 AM

Posted 07 February 2017 - 08:54 PM

I ald using window 10 more than half year, but recently day day keep restart BSOD critical structure corruption

Please help me

Attached Files



BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:09:38 PM

Posted 10 February 2017 - 08:10 AM

Your UEFI/BIOS (version F.04) dates from 2012.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it.  WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Only 6 Windows Update hotfixes installed.  Most build 14393 (1607) systems have more than this.  Please visit Windows Update and get ALL available Windows Updates.
The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

D: drive only has about 10% free space.  Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance.  Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty).  Low free space can cause BSOD's - but the actual amount depends on the files being used by the system.

I would suggest running Driver Verifier in order to see if we can coax the name of the driver that's to blame out of the memory dumps.

Please let the system crash at least 3 times in order to ensure we get sufficient information.

Please follow these instructions for using Driver Verifier:  http://www.carrona.org/verifier.html

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Tue Feb  7 20:23:14.643 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\020817-5937-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 0:40:42.377
Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 109, {a39fe5d8feb7b906, b3b6f25f51399b78, 2, 18}
BugCheck Info: CRITICAL_STRUCTURE_CORRUPTION (109)
Arguments:
Arg1: a39fe5d8feb7b906, Reserved
Arg2: b3b6f25f51399b78, Reserved
Arg3: 0000000000000002, Failure type dependent information
Arg4: 0000000000000018, Type of corrupted region, can be
    0   : A generic data region
    1   : Modification of a function or .pdata
    2   : A processor IDT
    3   : A processor GDT
    4   : Type 1 process list corruption
    5   : Type 2 process list corruption
    6   : Debug routine modification
    7   : Critical MSR modification
    8   : Object type
    9   : A processor IVT
    a   : Modification of a system service function
    b   : A generic session data region
    c   : Modification of a session function or .pdata
    d   : Modification of an import table
    e   : Modification of a session import table
    f   : Ps Win32 callout modification
    10  : Debug switch routine modification
    11  : IRP allocator modification
    12  : Driver call dispatcher modification
    13  : IRP completion dispatcher modification
    14  : IRP deallocator modification
    15  : A processor control register
    16  : Critical floating point control register modification
    17  : Local APIC modification
    18  : Kernel notification callout modification
    19  : Loaded module list modification
    1a  : Type 3 process list corruption
    1b  : Type 4 process list corruption
    1c  : Driver object corruption
    1d  : Executive callback object modification
    1e  : Modification of module padding
    1f  : Modification of a protected process
    20  : A generic data region
    21  : A page hash mismatch
    22  : A session page hash mismatch
    23  : Load config directory modification
    24  : Inverted function table modification
    25  : Session configuration modification
    26  : An extended processor control register
    27  : Type 1 pool corruption
    28  : Type 2 pool corruption
    29  : Type 3 pool corruption
    101 : General pool corruption
    102 : Modification of win32k.sys
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  BAD_STACK_0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID: BAD_STACK_0x109
CPUID:        "Intel® Core™ i5-3320M CPU @ 2.60GHz"
MaxSpeed:     2600
CurrentSpeed: 2594
  BIOS Version                  68ICE Ver. F.04
  BIOS Release Date             06/12/2012
  Manufacturer                  Hewlett-Packard
  Product Name                  HP ProBook 6470b
  Baseboard Product             179C
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Feb  7 12:26:21.419 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\020817-6921-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.693.amd64fre.rs1_release.161220-1747
System Uptime:0 days 1:53:59.154
Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 109, {a3a0215a04b765c5, b3b72de05738635f, 2, 18}
BugCheck Info: CRITICAL_STRUCTURE_CORRUPTION (109)
Arguments:
Arg1: a3a0215a04b765c5, Reserved
Arg2: b3b72de05738635f, Reserved
Arg3: 0000000000000002, Failure type dependent information
Arg4: 0000000000000018, Type of corrupted region, can be
    0   : A generic data region
    1   : Modification of a function or .pdata
    2   : A processor IDT
    3   : A processor GDT
    4   : Type 1 process list corruption
    5   : Type 2 process list corruption
    6   : Debug routine modification
    7   : Critical MSR modification
    8   : Object type
    9   : A processor IVT
    a   : Modification of a system service function
    b   : A generic session data region
    c   : Modification of a session function or .pdata
    d   : Modification of an import table
    e   : Modification of a session import table
    f   : Ps Win32 callout modification
    10  : Debug switch routine modification
    11  : IRP allocator modification
    12  : Driver call dispatcher modification
    13  : IRP completion dispatcher modification
    14  : IRP deallocator modification
    15  : A processor control register
    16  : Critical floating point control register modification
    17  : Local APIC modification
    18  : Kernel notification callout modification
    19  : Loaded module list modification
    1a  : Type 3 process list corruption
    1b  : Type 4 process list corruption
    1c  : Driver object corruption
    1d  : Executive callback object modification
    1e  : Modification of module padding
    1f  : Modification of a protected process
    20  : A generic data region
    21  : A page hash mismatch
    22  : A session page hash mismatch
    23  : Load config directory modification
    24  : Inverted function table modification
    25  : Session configuration modification
    26  : An extended processor control register
    27  : Type 1 pool corruption
    28  : Type 2 pool corruption
    29  : Type 3 pool corruption
    101 : General pool corruption
    102 : Modification of win32k.sys
BUGCHECK_STR:  0x109
DEFAULT_BUCKET_ID:  BAD_STACK_0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID: BAD_STACK_0x109
CPUID:        "Intel® Core™ i5-3320M CPU @ 2.60GHz"
MaxSpeed:     2600
CurrentSpeed: 2594
  BIOS Version                  68ICE Ver. F.04
  BIOS Release Date             06/12/2012
  Manufacturer                  Hewlett-Packard
  Product Name                  HP ProBook 6470b
  Baseboard Product             179C
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.

Spoiler



3rd Party Drivers:
The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Tue Feb  7 20:23:14.643 2017 (UTC - 5:00)**************************
iaStor.sys                  Wed Feb  1 19:15:24 2012 (4F29D59C)
iusb3hcs.sys                Tue Mar 27 04:11:21 2012 (4F717629)
Accelerometer.sys           Thu Apr 26 12:26:29 2012 (4F997735)
HECIx64.sys                 Mon Jul  2 18:14:58 2012 (4FF21D62)
stwrt64.sys                 Fri Oct 25 00:08:57 2013 (5269EED9)
NETwew00.sys                Tue Feb 25 08:04:56 2014 (530C94F8)
e1c64x64.sys                Fri May  2 15:35:23 2014 (5363F37B)
IntcDAud.sys                Tue Sep  9 08:13:01 2014 (540EEECD)
bcbtums.sys                 Mon Mar 23 17:31:26 2015 (5510862E)
hcmon.sys                   Tue May  5 03:09:44 2015 (55486CB8)
igdkmd64.sys                Tue May 26 23:53:18 2015 (55653FAE)
SPUVCbv_x64.sys             Tue Jun  9 06:53:29 2015 (5576C5A9)
SynTP.sys                   Mon Jul  6 07:12:43 2015 (559A62AB)
iwdbus.sys                  Thu Nov 19 18:37:42 2015 (564E5D46)
kesvc.sys                   Fri Jan  8 22:06:46 2016 (56907946)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
aswRvrt.sys                 Thu Aug 18 10:12:01 2016 (57B5C231)
aswKbd.sys                  Thu Aug 18 10:12:06 2016 (57B5C236)
aswRdr2.sys                 Thu Aug 18 10:12:58 2016 (57B5C26A)
aswMonFlt.sys               Thu Aug 18 10:30:14 2016 (57B5C676)
aswStm.sys                  Thu Aug 18 10:36:29 2016 (57B5C7ED)
aswSnx.sys                  Mon Sep 12 08:37:08 2016 (57D6A174)
aswSP.sys                   Mon Sep 12 08:59:01 2016 (57D6A695)
aswVmm.sys                  Thu Oct  6 05:26:20 2016 (57F618BC)
MBAMChameleon.sys           Sat Nov 19 14:13:08 2016 (5830A444)
prsdmp.sys                  Fri Jan 13 00:17:45 2017 (587862F9)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Feb  7 12:26:21.419 2017 (UTC - 5:00)**************************
jmcr.sys                    Wed Feb 15 01:08:41 2012 (4F3B4BE9)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Feb  7 04:03:03.331 2017 (UTC - 5:00)**************************
cnnctfy4.sys                Tue Sep  1 17:19:12 2015 (55E61650)
cfywlan2.sys                Thu Oct 22 12:07:44 2015 (562909D0)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan 30 21:16:02.509 2017 (UTC - 5:00)**************************
xlwfp.sys                   Tue Jan 12 04:10:31 2016 (5694C307)
XLGuard.sys                 Thu Feb 18 03:06:08 2016 (56C57B70)
MBAMSwissArmy.sys           Wed Jan  4 03:34:33 2017 (586CB399)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan 30 20:27:37.912 2017 (UTC - 5:00)**************************
XLGuard.sys                 Tue Oct 20 03:43:53 2015 (5625F0B9)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan 30 09:00:48.166 2017 (UTC - 5:00)**************************
stwrt64.sys                 Mon Mar  5 21:11:10 2012 (4F55723E)
hpdskflt.sys                Thu Apr 26 12:26:29 2012 (4F997735)
SynTP.sys                   Thu Jun 11 23:05:12 2015 (557A4C68)
igdkmd64.sys                Mon Dec 21 14:46:50 2015 (5678572A)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jan 30 05:37:29.143 2017 (UTC - 5:00)**************************
LeapdroidVMDrv.sys          Thu Aug  4 22:53:44 2016 (57A3FFB8)


http://www.carrona.org/drivers/driver.php?id=iaStor.sys
http://www.carrona.org/drivers/driver.php?id=iusb3hcs.sys
http://www.carrona.org/drivers/driver.php?id=Accelerometer.sys
http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
http://www.carrona.org/drivers/driver.php?id=stwrt64.sys
http://www.carrona.org/drivers/driver.php?id=NETwew00.sys
http://www.carrona.org/drivers/driver.php?id=e1c64x64.sys
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
http://www.carrona.org/drivers/driver.php?id=bcbtums.sys
http://www.carrona.org/drivers/driver.php?id=hcmon.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=SPUVCbv_x64.sys
http://www.carrona.org/drivers/driver.php?id=SynTP.sys
http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
kesvc.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=aswRvrt.sys
http://www.carrona.org/drivers/driver.php?id=aswKbd.sys
http://www.carrona.org/drivers/driver.php?id=aswRdr2.sys
http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys
http://www.carrona.org/drivers/driver.php?id=aswStm.sys
http://www.carrona.org/drivers/driver.php?id=aswSnx.sys
http://www.carrona.org/drivers/driver.php?id=aswSP.sys
http://www.carrona.org/drivers/driver.php?id=aswVmm.sys
http://www.carrona.org/drivers/driver.php?id=MBAMChameleon.sys
prsdmp.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=jmcr.sys
cnnctfy4.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
cfywlan2.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=xlwfp.sys
XLGuard.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=MBAMSwissArmy.sys
XLGuard.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=stwrt64.sys
http://www.carrona.org/drivers/driver.php?id=hpdskflt.sys
http://www.carrona.org/drivers/driver.php?id=SynTP.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
LeapdroidVMDrv.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
 
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users