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

Windows 10 Home: BAD POOL HEADER


  • Please log in to reply
5 replies to this topic

#1 thedudejude

thedudejude

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:05:22 AM

Posted 13 February 2016 - 12:54 AM

Windows 10 Home: BAD POOL HEADER error. 

 

My wife's compute has this issue. Bad Pool Header error. It will randomly occur, and the pc will restart itself. 
 
Ran memtest86 for 5 passes, no errors. 
 
I have run sfc /scannow no errors. I have run chkdsk no errors. 
 
I have included a link to my onedrive with DMP files, including a screenshot of the sfc/ scannow, chkdsk, and speccy.txt contains the link to specs of pc. and a minitoolbox .txt output of:
 
List last 10 Event Viewer log
List Installed Programs
List Users, Partitions and Memory size.
Windows 10 Home 64 bit. 
 
The only thing I have noticed is under critical errors in event viewer logs is that it does say:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
[ Name]  Microsoft-Windows-Kernel-Power 
   [ Guid]  {331C3B3A-2005-44C2-AC5E-77220C37D6B4} 
 
   EventID 41 
 
   Version 3 
 
   Level 1 
 
   Task 63 
 
   Opcode 0 
 
   Keywords 0x8000400000000002 
 
Could this possibly mean a bad or failing PSU?
 
Here is the link to the OneDrive folder with the DMP files, etc:
 


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:09:22 AM

Posted 13 February 2016 - 09:02 AM

Please run this report collecting tool so that we can provide a complete analysis:  http://omgdebugging.com/bsod-inspector/
When done a Notepad document will open with the name of the file and it's location. (By default it'll be a .zip file located on your Desktop)
Simply upload the .zip file with your next post and we'll move on from there.

Your UEFI/BIOS (version V1.3) dates from 2008.  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.

You have an unknown number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.

The memory dumps appear to focus on MalwareBytes, but I'm uncertain if it's MalwareBytes or your Norton that's causing the problems here.

Please stop MalwareBytes from loading with Windows in order to see if it's a conflict between the 2.

 

Analysis:
The following is for informational purposes only.
**************************Fri Feb 12 23:05:33.410 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\021216-12093-01.dmp]
Windows 10 Kernel Version 10586 MP (2 procs) Free x64
Built by: 10586.103.amd64fre.th2_release.160126-1819
System Uptime: 0 days 0:03:02.121
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+1dd )
BugCheck 19, {20, ffffe001b57eda40, ffffe001b57eda60, 402000c}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffe001b57eda40, The pool entry we were looking for within the page.
Arg3: ffffe001b57eda60, The next pool entry.
Arg4: 000000000402000c, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  mbamservice.ex
FAILURE_BUCKET_ID:  0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
CPUID:        "Intel® Core™2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 3007
  BIOS Version                  V1.3
  BIOS Release Date             07/02/2008
  Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
  Product Name                  MS-7514
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Feb 12 23:01:47.324 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\021216-11125-01.dmp]
Windows 10 Kernel Version 10586 MP (2 procs) Free x64
Built by: 10586.103.amd64fre.th2_release.160126-1819
System Uptime: 0 days 18:43:37.229
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+1dd )
BugCheck 19, {20, ffffe001700c4080, ffffe001700c40a0, 4020008}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffe001700c4080, The pool entry we were looking for within the page.
Arg3: ffffe001700c40a0, The next pool entry.
Arg4: 0000000004020008, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  mbamservice.ex
FAILURE_BUCKET_ID:  0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
CPUID:        "Intel® Core™2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 3007
  BIOS Version                  V1.3
  BIOS Release Date             07/02/2008
  Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
  Product Name                  MS-7514
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Feb 11 03:16:18.931 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\021116-11515-01.dmp]
Windows 10 Kernel Version 10586 MP (2 procs) Free x64
Built by: 10586.103.amd64fre.th2_release.160126-1819
System Uptime: 0 days 0:01:52.648
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+1dd )
BugCheck 19, {20, ffffe0012fd2f080, ffffe0012fd2f0a0, 4020008}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffe0012fd2f080, The pool entry we were looking for within the page.
Arg3: ffffe0012fd2f0a0, The next pool entry.
Arg4: 0000000004020008, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  mbamservice.ex
FAILURE_BUCKET_ID:  0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
CPUID:        "Intel® Core™2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 3007
  BIOS Version                  V1.3
  BIOS Release Date             07/02/2008
  Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
  Product Name                  MS-7514
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Feb 11 03:13:45.466 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\021116-11078-01.dmp]
Windows 10 Kernel Version 10586 MP (2 procs) Free x64
Built by: 10586.103.amd64fre.th2_release.160126-1819
System Uptime: 0 days 0:29:00.178
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+1dd )
BugCheck 19, {20, ffffe0016c0e1460, ffffe0016c0e1480, 4020046}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffe0016c0e1460, The pool entry we were looking for within the page.
Arg3: ffffe0016c0e1480, The next pool entry.
Arg4: 0000000004020046, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  mbamservice.ex
FAILURE_BUCKET_ID:  0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
CPUID:        "Intel® Core™2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 3007
  BIOS Version                  V1.3
  BIOS Release Date             07/02/2008
  Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
  Product Name                  MS-7514
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Feb 11 02:44:04.143 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\021016-9265-01.dmp]
Windows 10 Kernel Version 10586 MP (2 procs) Free x64
Built by: 10586.103.amd64fre.th2_release.160126-1819
System Uptime: 0 days 4:01:27.857
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+1dd )
BugCheck 19, {20, ffffe000c52ab6f0, ffffe000c52ab710, 4020011}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffe000c52ab6f0, The pool entry we were looking for within the page.
Arg3: ffffe000c52ab710, The next pool entry.
Arg4: 0000000004020011, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  mbamservice.ex
FAILURE_BUCKET_ID:  0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
CPUID:        "Intel® Core™2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 3007
  BIOS Version                  V1.3
  BIOS Release Date             07/02/2008
  Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
  Product Name                  MS-7514
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Feb 10 22:41:54.833 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\021016-11234-01.dmp]
Windows 10 Kernel Version 10586 MP (2 procs) Free x64
Built by: 10586.103.amd64fre.th2_release.160126-1819
System Uptime: 0 days 4:54:59.545
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+1dd )
BugCheck 19, {20, ffffe00156345c60, ffffe00156345c80, 402000a}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffe00156345c60, The pool entry we were looking for within the page.
Arg3: ffffe00156345c80, The next pool entry.
Arg4: 000000000402000a, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  mbamservice.ex
FAILURE_BUCKET_ID:  0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
CPUID:        "Intel® Core™2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 3007
  BIOS Version                  V1.3
  BIOS Release Date             07/02/2008
  Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
  Product Name                  MS-7514
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Feb 10 17:46:14.832 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\021016-11640-01.dmp]
Windows 10 Kernel Version 10586 MP (2 procs) Free x64
Built by: 10586.103.amd64fre.th2_release.160126-1819
System Uptime: 0 days 0:01:47.544
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+1dd )
BugCheck 19, {20, ffffe000f5ecae30, ffffe000f5ecae50, 402000e}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffe000f5ecae30, The pool entry we were looking for within the page.
Arg3: ffffe000f5ecae50, The next pool entry.
Arg4: 000000000402000e, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  mbamservice.ex
FAILURE_BUCKET_ID:  0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
CPUID:        "Intel® Core™2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 3007
  BIOS Version                  V1.3
  BIOS Release Date             07/02/2008
  Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
  Product Name                  MS-7514
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Feb 10 17:43:45.443 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\021016-11078-01.dmp]
Windows 10 Kernel Version 10586 MP (2 procs) Free x64
Built by: 10586.103.amd64fre.th2_release.160126-1819
System Uptime: 0 days 1:32:02.156
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+1dd )
BugCheck 19, {20, ffffe000f1e66170, ffffe000f1e66190, 4020017}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffe000f1e66170, The pool entry we were looking for within the page.
Arg3: ffffe000f1e66190, The next pool entry.
Arg4: 0000000004020017, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  mbamservice.ex
FAILURE_BUCKET_ID:  0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
CPUID:        "Intel® Core™2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 3007
  BIOS Version                  V1.3
  BIOS Release Date             07/02/2008
  Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
  Product Name                  MS-7514
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Feb 10 16:11:04.055 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\021016-10937-01.dmp]
Windows 10 Kernel Version 10586 MP (2 procs) Free x64
Built by: 10586.103.amd64fre.th2_release.160126-1819
System Uptime: 0 days 8:24:38.767
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+1dd )
BugCheck 19, {20, ffffe0012ee13ea0, ffffe0012ee13ec0, 4020015}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffe0012ee13ea0, The pool entry we were looking for within the page.
Arg3: ffffe0012ee13ec0, The next pool entry.
Arg4: 0000000004020015, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  mbamservice.ex
FAILURE_BUCKET_ID:  0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
CPUID:        "Intel® Core™2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 3007
  BIOS Version                  V1.3
  BIOS Release Date             07/02/2008
  Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
  Product Name                  MS-7514
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Feb 10 03:24:09.892 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\021016-12375-01.dmp]
Windows 10 Kernel Version 10586 MP (2 procs) Free x64
Built by: 10586.63.amd64fre.th2_release.160104-1513
System Uptime: 2 days 22:18:02.606
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+1dd )
BugCheck 19, {20, ffffe0005dedec10, ffffe0005dedec30, 4020008}
BugCheck Info: BAD_POOL_HEADER (19)
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: ffffe0005dedec10, The pool entry we were looking for within the page.
Arg3: ffffe0005dedec30, The next pool entry.
Arg4: 0000000004020008, (reserved)
BUGCHECK_STR:  0x19_20
PROCESS_NAME:  mbamservice.ex
FAILURE_BUCKET_ID:  0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
CPUID:        "Intel® Core™2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 3007
  BIOS Version                  V1.3
  BIOS Release Date             07/02/2008
  Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
  Product Name                  MS-7514
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only.
Any drivers in RED should be updated or removed from your system. And should have been discussed in the body of my post.
**************************Fri Feb 12 23:05:33.410 2016 (UTC - 5:00)**************************
PxHlpa64.sys                Tue Apr 24 13:26:29 2012 (4F96E245)
ssudbus.sys                 Thu Jan  2 04:51:22 2014 (52C5369A)
ssudmdm.sys                 Thu Jan  2 04:51:26 2014 (52C5369E)
mwac.sys                    Tue Jun 17 22:07:00 2014 (53A0F444)
ccSetx64.sys                Mon Aug 18 15:33:11 2014 (53F254F7)
SRTSPX64.SYS                Tue Aug 26 02:36:42 2014 (53FC2AFA)
SYMEVENT64x86.SYS           Mon Jan 19 17:43:56 2015 (54BD88AC)
AE6000w864.sys              Mon Feb 16 01:09:49 2015 (54E189AD)
Ironx64.SYS                 Mon May  4 19:51:42 2015 (5548060E)
RTKVHD64.sys                Tue Jun 16 06:55:05 2015 (55800089)
MBAMSwissArmy.sys           Wed Jul 29 00:26:01 2015 (55B855D9)
mbam.sys                    Tue Aug 11 13:35:19 2015 (55CA3257)
SYMNETS.SYS                 Mon Aug 24 16:15:17 2015 (55DB7B55)
BHDrvx64.sys                Fri Sep 25 21:17:16 2015 (5605F21C)
rt640x64.sys                Wed Oct  7 11:03:55 2015 (5615345B)
nvlddmkm.sys                Tue Oct 13 11:43:56 2015 (561D26BC)
SYMEFASI64.SYS              Mon Oct 19 19:48:01 2015 (56258131)
intelppm.sys                Thu Oct 29 22:09:51 2015 (5632D16F)
eeCtrl64.sys                Fri Nov  6 21:29:47 2015 (563D621B)
EraserUtilRebootDrv.sys     Fri Nov  6 21:29:47 2015 (563D621B)
IDSvia64.sys                Tue Dec  1 18:46:40 2015 (565E3160)
nvvad64v.sys                Thu Dec 17 07:47:18 2015 (5672AED6)
NvStreamKms.sys             Tue Dec 22 15:53:26 2015 (5679B846)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Feb 12 23:01:47.324 2016 (UTC - 5:00)**************************
SRTSP64.SYS                 Fri Oct  9 20:11:42 2015 (561857BE)
EX64.SYS                    Tue Oct 13 22:01:49 2015 (561DB78D)
ENG64.SYS                   Tue Oct 13 22:06:35 2015 (561DB8AB)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Feb 11 03:16:18.931 2016 (UTC - 5:00)**************************
IDSvia64.sys                Mon Oct 12 22:00:26 2015 (561C65BA)
http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys
http://www.carrona.org/drivers/driver.php?id=ssudbus.sys
http://www.carrona.org/drivers/driver.php?id=ssudmdm.sys
http://www.carrona.org/drivers/driver.php?id=mwac.sys
http://www.carrona.org/drivers/driver.php?id=ccSetx64.sys
http://www.carrona.org/drivers/driver.php?id=SRTSPX64.SYS
http://www.carrona.org/drivers/driver.php?id=SYMEVENT64x86.SYS
AE6000w864.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=Ironx64.SYS
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=MBAMSwissArmy.sys
http://www.carrona.org/drivers/driver.php?id=mbam.sys
http://www.carrona.org/drivers/driver.php?id=SYMNETS.SYS
http://www.carrona.org/drivers/driver.php?id=BHDrvx64.sys
http://www.carrona.org/drivers/driver.php?id=rt640x64.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=SYMEFASI64.SYS
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=eeCtrl64.sys
http://www.carrona.org/drivers/driver.php?id=EraserUtilRebootDrv.sys
http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=SRTSP64.SYS
http://www.carrona.org/drivers/driver.php?id=EX64.SYS
http://www.carrona.org/drivers/driver.php?id=ENG64.SYS
http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys
 


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.

#3 thedudejude

thedudejude
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:05:22 AM

Posted 13 February 2016 - 06:24 PM

Hi,

 

I did exactly as you instructed. The zip file of report collecting tool was ran and zipped first. It should be attached to this post. 

 

Checked the motherboard manufacturer for any UEFI/BIOS updates. There are none, I have included a screenshot of that. 

 

Windows updates appears to be updated. At least that is what it says, when I try to update it. I even went into advanced and checked the "check for updates for all Microsoft products" as well. Screenshot provided. 

 

Went into Malwarebytes configuration and unchecked the box "start with windows" and exited the program. 

 

Not exactly sure what AE6000w864.sys is, but when I checked it says it is a wireless device driver. This computer is using a linksys wireless USB adapter. It is working, and if I go to device manager, it says the device is working. 

 

Anything else I missed, please let me know. 

 

Thanks!

Attached Files



#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:09:22 AM

Posted 14 February 2016 - 06:14 AM

I'm late for work right now.  I'll try to get to this this afternoon or tomorrow AM at the latest.

Meanwhile, we wait to see if what you've done so far has stopped the BSOD's........

Good luck!


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.

#5 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:09:22 AM

Posted 15 February 2016 - 06:11 AM

AE6000w864.sys is a driver for a wireless USB wifi device:

I do not recommend using wireless USB network devices.
These wireless USB devices have many issues with Win7 and later systems - using older drivers with them is almost certain to cause a BSOD.
Should you want to keep using these devices, be sure to have the latest W7/8/8.1/10 drivers - DO NOT use older drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.


Your UEFI/BIOS (version V1.3) dates from 2008.  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.

Only 8 Windows Update hotfixes installed.  Most build 10586 (TH2/1511) systems have more than this.  Please visit Windows Update and get ALL available Windows Updates.

If these steps don't help stop the BSOD's, please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

 

I'm very concerned with the age of your BIOS.  If unable to find updates that will help with this, you may have to consider that the system may not be compatible w/W10.

We'll continue to help here, but it's your decision on the compatibliity issue.  The solution for a compatibility issue is to revert to the previous OS and see if the problems remain there.

Good luck!


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.

#6 Jimbo4u

Jimbo4u

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:NJ
  • Local time:08:22 AM

Posted 06 May 2016 - 09:53 AM

I had this message too. I looked at Task Manager and Processes and saw the Hard Drive was 100%, then a shutdown / restart occurred. I ran Glary 5 and chkdsk /F and now the Hard Drive is around 0-5%.


looking foward into the past or backward into the future i walk along the highest hills and i laugh about it all the way - e e cummings




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users