New
#1
BSOD 0x0000000a, 0x000000c2, 0x00000019 and the most common 0x00000024
Hello,
I have these BSODs that occur frequently, at least once a week, usually more.
The computer I use is a bit old, but it has functioned well until these BSODs started to appear. I have changed the HDDs, first added the SSD, and the computer was fine for weeks with it, then replaced all the other existing HDDs with my HDDs (the computer belonged to my boyfriend). About a week after this the BSODs begun to appear.
The most common of them is 0x00000024 NFTS_FILE_SYSTEM caused by Ntfs.sys (+ntoskrnl.exe+75c00), but I've had at least these three too (as far as I can remember):
BAD_POOL_CALLER caused by fltmgr.sys
BAD_POOL_HEADER caused by Ntfs.sys
IRQL_NOT_LESS_OR_EQUAL caused by ntoskrnl.exe
The BSODs can appear at any time; I was watching videos from my hard drive, I was coding with putty on a remote server, I left my computer idle when I got to sleep or left the apartment... So far I haven't been able to find out a pattern with these BSODs.
Notes for the usual tutorial:
- If you are overclocking any hardware, please stop. - I am not overclocking anything
- If you have an SSD, make sure the following are up to date:
SSD firmware - Is up to date.BIOS Version - Is up to date.Chipset Drivers - As far as I have looked, they are up to date.Hard disk controller drivers/SATA drivers - As far as I have looked, they are up to date.
- Run all but the advanced tests with SeaTools for HDDs. - I did, all ok. I also ran HDDscan for all drives, all ok and chkdsk /r & /f for all drives, all ok.
- Use FurMark - I couldn't, too old graphics.
- Run the boot version of Memtest86+ - Ran it up to 30 hours, something 20+ passes without errors.
- Also sfc /scannow did not find any integrity violations.
The things I haven't yet tried:
- Running with only the SSD and the HDD that has the software, taking out the other two
- Reinstalling Windows
I you want to contact me personally, I can be found in IRCnet by nick jaine
jaine@IRCnet