Jump to content

cxb1

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About cxb1

  • Rank
    New Member

Recent Profile Visitors

514 profile views
  1. Well, your decisions are your own: that's fine. I have no expertise in Intel or Microsoft. My expertise, however, runs in previous generations of mainframes, from the lowest level of hardware (imagine diagnosing a "once-a-month" user program failure, down to a 20ns spike on a single bit of a single arithmetic register within a mainframe the size of a built-in wardrobe, or flying to Melbourne Australia, to diagnose a random failure down to an intermittent crack in the copper track buried inside a motherboard) or "dump-cracking" - determining the failure point from the hexadecimal dump of
  2. Regarding USASMA's comment, I can't let this self-congratulatory message go unchallenged (either). This forum is full of BSOD-type failures, starting well into mid 2015. I myself reported a BAD POOL Header failure in March (over 6 months ago), and only got another "What antivirus are you using? " - I clearly stated MBAM and Avast - "and if it's BitDefender then etc etc..." - none of it in the slightest bit relevant to the problem. Lots of "please create a minidump" and "check your drivers are uptodate" and constant reference to BitDefender - none of it relevant to me. All these BSOD probl
  3. Thank you pakhoi. That is useful. I'll wait and see what happens.
  4. Here are the dumps from FRST64 and mbam-check Addition.txt CheckResults.txt FRST.txt
  5. I get the same problem, in the same circumstances it seems. Same version of Windows 10 Pro (latest), same BSOD reported in same module. With BitLocker drives. It's bedtime (!) so I'll look into this tomorrow. Regards
  6. Thanks for the analysis tools, but I don't think I'll get the problem anymore; but if I do, I'll certainly use your suggestion. When I have my system 'stable' at last, I'm not very inclined to go back and re-create all the issues I had with Fast Start messing up the file structure integrity. I think the biggest issue I have, is that over the past 9 months, I'm not sure that MalwareBytes have acknowledged that THEY have a problem. I know correlation isn't causation, but the correlation of Bad Pool Headers with MalwareBytes being installed, simply drives people away from a very good pr
  7. Sorry, was that question aimed at me? No, I stopped using Bit Defender some time ago. I use Avast Pro + Malwarebytes. The Bad Pool Header problems were only ever associated with MalwareBytes, and over 6 months, I kept hoping they would be fixed, but everytime I reloaded MalwareBytes and updated the software, it still had these same issues. Until I switched off Malicious Website, and now Fast Restart and Sleep (hyperfil.sys?)
  8. I've been having random Bad_Pool_Header failures when surfing the web, too. But only on one of the two systems I have. I think I've "fixed" the problem. No BPHs Random BPHs System 1 System 2 Notebook PC UEFI/GPT Classic/MBR Win10Pro Win10Pro Dual Boot/Linux AHCI RAID First discovery: it's only related to MWAC, the Malicious Website Protection service. Switch that off, and it goes away. Second discovery: It started in Windows 10. (after I upg
  9. Yes, I get the same thing (I think). Bad_Pool_Header failures on my PC, but not on my laptop. The PC is older, Intel G45, running Win 10, ATI graphics, BitLocker, a BIOS RAID on the Intel chip ICH6R, a mix of SSDs and Disks, Avast and MBAM Premium The laptop is newer, Intel Core i5-4200U, running Win 10, Intel chip graphics, BitLocker, no raid, Avast and MBAM Premium. The Bad_Pool_header failure is intermittent, but predictably 2-4 times a day, usually while on the Internet (Firefox, NoScript + AdBlock Plus). Removing MBAM Premium on the PC has resulted in no failures in the past 5 days.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.