• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Question BSOD Bad Pool Header

Lost_in_the_HTTP

Lost_in_the_HTTP

Lifer
Win 7 (Yes, still using it, flog me.)

Browsing along normally, music running. BSOD, Bad Pool Header, restarted normally. here I am. But where am I? And why?
 
Try a bootable RAM test, and/or re-seat your RAM.

Otherwise, it could be a bad/flakey driver. Maybe even bad/flakey hardware, if it's scribbling on RAM that it's not supposed to. Don't go swapping hardware before you do a RAM test though.
 
MemTest, basic two pass completed, no error. Showed no error on the test screen, but did not display result on startup and I can't find a log. No error -- no log?

sfc /scannow, no error.


-------------

On soft restarts like this memtest did, or after a BSOD, the E: drive does not populate. Files cannot be found.

On hard restarts (shutdown, power button to start), it populates fine. Works normally.
 
Shmee said:
I would run memtest86, I wouldn't really trust the built in Windows one.
Click to expand...

+1. Considering that if the system is old enough to run Win7 during Win7's 'era', so if there's a memory fault it's probably isn't going to be a glaring one and might take 4 or more passes for memtest86 (7.4 or 4.3.7, the 7.4 ISO contains both so it's compatible with UEFI and legacy systems) to find it.
 
Lost_in_the_HTTP said:
On soft restarts like this memtest did, or after a BSOD, the E: drive does not populate. Files cannot be found.
Click to expand...
Flaky SATA controller?

Where is that drive located? On the single storage device (HDD or SSD) or a separate device?

You could try replacing the SATA cable and maybe also try a different SATA power connector from the PSU to the physical drive.

Check PSU voltages in BIOS if that's available. Any voltage running more than 5% higher (3.3V / 5V and 12V) could cause stability issues. How old is the PSU? You could try a spare one? If it's an OEM PC which won't accept a normal PSU, that's a bummer then.
 
Last edited:
@Lost_in_the_HTTP Does E drive show up in explorer immediately just with no files, or does it take its time, or not at all no matter how much time you give it?

I just wonder if the crash is causing the extra drive to go through some cursory NTFS checks and comes online in its own time. The event log would likely give some useful pointers here.
 
E: does not appear at all on a soft boot. Always appears right away on a hard/power boot.

I see stuff in the Event Viewer, but nothing that tells me anything I can understand.
 
What is the E: drive? SSD? HDD? What model? How old? You may want to check the SMART data to make sure the drive is healthy.
 
Old laptop makes me want to ask if it is overheating. I install Coretemp on everything, especially laptops.

It's probably a driver problem, these become more frequent with old stuff since backwards compatibility only goes so far.
 
Speccy shows normally in the 100-130F range, sometimes spiking to 150 or less when running something intensive, but that's only for short periods.
 
Lost_in_the_HTTP said:
E: does not appear at all on a soft boot. Always appears right away on a hard/power boot.

I see stuff in the Event Viewer, but nothing that tells me anything I can understand.
Click to expand...

disk / ntfs / *ahci* warnings and errors are of interest in the 'System' log. If they tally up with disk numbers in Disk Management or the correct drive letter, then they're definitely relevant.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top