Member Avatar for Serunson

heres my problem
when i allow folder sharing on msn
and a partiular person shares folders with me the blue screen of death appears.
it says about a BAD_POOL_HEADER error occuring
any help would be apreciated thanks

  • 2 Contributors
  • 2 Replies
  • 125 Views
  • 6 Hours Discussion Span
  • Latest Post Latest Post by Serunson

Dani AI

Generated

BAD_POOL_HEADER (STOP 0x00000019) means a kernel memory pool header was corrupted. That usually points to a buggy kernel-mode component (device driver, network/file-filter driver from a security suite, or bad RAM) rather than a simple Messenger setting. Because this happens when a folder share is accepted, the bug is likely triggered by a network/file-filter driver installed by third-party security or by a faulty network/driver interaction.

noted Norton and suggested turning off firewalls. Disabling a firewall UI often does not unload the kernel drivers that can cause this crash; a full uninstall (or the vendor removal tool) is the proper way to test the suite as the culprit. Booting into Safe Mode is another quick isolator: if the BSOD stops in Safe Mode, a third-party driver is implicated.

Practical troubleshooting steps that have proven useful:

  1. Try to reproduce the crash and note the exact STOP code.
  2. Reboot into Safe Mode and attempt the same action.
  3. Fully remove the antivirus/security suite (use the vendor removal utility when available) and test again; if the crash stops, reinstall or update the suite.
  4. Update or roll back the network adapter and chipset drivers.
  5. Enable small memory dumps and analyze the minidump with BlueScreenView or WinDbg to see which driver name appears next to the crash.
  6. Run chkdsk /f, sfc /scannow, and a full RAM test (memtest86) to rule out disk or memory faults.
  7. Check Event Viewer around the crash time for driver or disk errors.

If removing the security suite does not help, collect the minidump and the driver name shown in the dump — that information is usually decisive. Leaving the system unprotected during testing is not recommended; enable Windows Firewall or disconnect the machine from the network when performing risky tests.

Recommended Answers

All 2 Replies

Member Avatar for sennetor

turn off all firewalls and try again.

Troubleshooting is the only answer I'm afraid.

Member Avatar for Serunson

i have norton on, is that why?
windows firewall is off

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.