Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About 00sweeney

  • Rank
    Regular Member
  1. It was always an intermittent problem, not something that happened every day or even every week. But it had happened enough and over a long enough period of time that I thought I should ask. I didn't realize that the restarts were coming from blue screens--to me it just looked like it was restarting when I woke it up. I've gotten the bad_pool_header error several times. I didn't realize they might be the same thing.
  2. Log Name: Application Source: Microsoft-Windows-Wininit Date: 1/4/2016 3:49:01 AM Event ID: 1001 Task Category: None Level: Information Keywords: Classic User: N/A Computer: Sweenman Description: Checking file system on C: The type of the file system is NTFS. Volume label is Windows8_OS. A disk check has been scheduled. Windows will now check the disk. Stage 1: Examining basic file system structure ... 666880 file records processed. File verification comp
  3. I don't know what happened the first time but it ran the second time, and has been at 13% for two hours. I know that's not uncommon, but unfortunately I have a meeting tomorrow and need access to the computer tonight, so I may have to stop the scan and try re-running it tonight before I go to bed.
  4. I ran the chkdsk command, but when it restarted it didn't go to the black screen that I've always seen with disk check--almost instantly I got a message that the disk check was done and it was fine. In the past, disk check has taken several minutes. Then I ran event viewer and followed your instructions but there were no results. I'm going to try chkdsk again. I'll try and get a screen shot of the message I get.
  5. I ran scannow (which I'd done not that long ago with no bad results) and this time it said it found and fixed corrupt files. But when I rebooted and ran the command you asked me to, it gave me an empty file, which I'm unable to attach--error message "Upload skipped, no file was selected for upload"--even though the file was selected. I don't think it makes a difference, but I got to the command line through win + X, not win + R, since I needed admin privileges and that was the quickest way. I will do the disk scan now.
  6. It probably doesn't matter, but this is the command I used before I had to restore the system: "verifier.exe /standard /all".
  7. Here you go. I'm sorry about what happened. When I saw that the restarts were the result of a bad pool error BDOD which has happened several times before, I wanted to check again and make sure it wasn't a driver issue and that I wasn't wasting everyone's time. I've used the command line a million times and I've never had it turn on me like that. zoek-results.txt WhoCrashed.txt FRST.txt
  8. As I'd said, I'd gotten this bad pool error before, and I'd read it might have something to do with drivers. I thought I'd updated everything, but I came a cross a command prompt that was supposed to check--I can't find the prompt right now. When I went to reboot, it couldn't start. None of the Windows trouble shooters worked, so I restored. (Wanted to say all this in original reply but had to leave for work.)
  9. Here you go. FYI, I had to restore the machine to a restore point from 12/31. Addition.txt FRST.txt
  10. Here you go. I've gotten a bad_pool_header blue screens in the past. WhoCrashed.txt zoek-results.log
  11. Also--and please forgive me if I'm being one of those "a little knowledge is a dangerous thing" kind of guys--but this shows up in the Event Log--is it connected? "The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000003, 0xffffe00058894d80, 0x0000000000000000, 0xffffe00058894d80). A dump was saved in: C:\WINDOWS\Minidump\010116-31562-01.dmp. Report Id: 010116-31562-01."
  12. Thanks for the swift reply. Here are the logs. I will uninstall the programs you mentioned, but I have a question--the only thing I used Advanced System Care for was the check disk option--which ran a lot faster than Windows chkdsk did, and often seemed to find problems. Is there another 3rd party disk check utility that you'd recommend? Also--I use Bittorrent, but it's not set to run at startup and I will not use it while we're working on the problem. I am 99% sure there's no pirated software on my machine, but if you see something please let me know. The reason I contacted you was that a qui
  13. That's pretty much it. It's also restarted a couple of times when it was on. I'm not a noob, but I'm far from an expert. I look in Event Viewer after it happens, and it seemed like there was definitely something going on, but I don't have the skills to tell what it is. I've run MBAM and BitDefender and found nothing (or found stuff that didn't fix the problem. I've cut and pasted or attached the Farbar Recovery files. Thanks for any help. Scan result of Farbar Recovery Scan Tool (FRST) (x64) Version:31-12-2015 Ran by Matt (administrator) on SWEENMAN (01-01-2016 16:25:26) Running from C:\User
  14. I'm running Windows 10, but it didn't work with Windows 8.1 either. I've selected show context menu entry, but the context menu entry is not showing when I right-click a scannable item. I have attached a screen shot because I know many of you simply will not believe that I have correctly set the context menu settings.
  15. Oh, and THANKS for the reminder about exclusions. I swear I already excluded the whole MBAM folder, but with all the uninstalling and reinstalling, for this and another issue, I forgot to do it again. I don't know if it was directly responsible, but after excluding the files you suggested, I went from 3:15 to under 2 minutes, which is acceptable. As for the other errors you pointed out in another thread--my machine is still under warranty and has phone support. I think I may just give them a call and go through the list,one-by-one and see if they can help. If that doesn't work, I'll investig
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.