Typical BSOD situation, minidump check?

Page 2 of 2 FirstFirst 12

  1. Posts : 5,705
    Win7 x64 + x86
       #11

    Thanks for the translation (I have no language skills - neither spoken nor programming) :)

    The BSOD only offers clues as to what's happening. So, if it points to your hard drive, that's the most likely explanation. My troubleshooting revolves around this - so the first thing that I ask is that you perform hard drive tests (to support/refute the supposition that it's a hard drive issue). Once that's done, we can then move on to other tests if necessary.

    Also, I suggest the memory test in my "canned" H/W Diagnostics speech because it's easier to run these tests up front. At work we run a hard drive diagnostic, a memory diagnostic, a motherboard diagnostic (about $400 US), and a virusscan before we start working on a system. It saves us many hours of troubleshooting if we run these tests first.


    In your case, chkdsk shows errors in your file system (but not that they were corrected). Are you sure that this is the result from running CHKDSK /F /R - or maybe it's from another test where you just ran CHKDSK?

    But, regardless of what it is, the presence of errors in CHKDSK means that there are issues with the file system on your hard drive. BUT, we don't know what caused the errors - so running the hard drive diagnostic is definitely needed at this point.

    Unfortunately the event log error doesn't have any significant information in it. Have you checked in C:\Windows\Minidump to see if there was a memory dump created at that time?
      My Computer


  2. Posts : 72
    Windows 7 64-bit
    Thread Starter
       #12

    usasma said:
    Thanks for the translation (I have no language skills - neither spoken nor programming) :)

    The BSOD only offers clues as to what's happening. So, if it points to your hard drive, that's the most likely explanation. My troubleshooting revolves around this - so the first thing that I ask is that you perform hard drive tests (to support/refute the supposition that it's a hard drive issue). Once that's done, we can then move on to other tests if necessary.

    Also, I suggest the memory test in my "canned" H/W Diagnostics speech because it's easier to run these tests up front. At work we run a hard drive diagnostic, a memory diagnostic, a motherboard diagnostic (about $400 US), and a virusscan before we start working on a system. It saves us many hours of troubleshooting if we run these tests first.


    In your case, chkdsk shows errors in your file system (but not that they were corrected). Are you sure that this is the result from running CHKDSK /F /R - or maybe it's from another test where you just ran CHKDSK?

    But, regardless of what it is, the presence of errors in CHKDSK means that there are issues with the file system on your hard drive. BUT, we don't know what caused the errors - so running the hard drive diagnostic is definitely needed at this point.

    Unfortunately the event log error doesn't have any significant information in it. Have you checked in C:\Windows\Minidump to see if there was a memory dump created at that time?
    Okay thank you man! I ran the /f /r but I can run It now too again, It takes like 20-30 min to complete so not a big problem.

    I checked the minidump and there was no dump file named that. But those messages are gone (bluescreen gone for 2 cold boots and 6 reboots, when I raised up lil bit HT and NB voltage )

    But I will run the chkdsk now for to be sure, and post the result here translated. This doesn't take so long, maybe up to 30minutes. And I will run overnight the seatools again. Seatools results I will post tomorrow morning.

    Very much thanks for the help, really appreciate your work! :)
      My Computer


  3. Posts : 72
    Windows 7 64-bit
    Thread Starter
       #13

    Log Name: Application
    Source: Microsoft-Windows-wininit
    Date: 16.2.2010 23:42:30
    Event ID: 1001
    Task Category: None
    Level: About
    Keywords: Traditional
    User: --
    Computer: Wili
    Description:


    Checked drive C: File System
    Filesystem type is NTFS.

    Disk check has been scheduled.
    Windows checks the disk now.

    CHKDSK scan files (stage 1 / 5) ...
    102,144 file record processed.

    File Amendment carried out.
    75 large file record processed.

    0 defective file record processed.

    0 EA records processed.

    65 uudelleenjäsennystietuetta processed.

    CHKDSK check the indexes (stage 2 / 5) ...
    137,976 index entry processed.

    Index Amendment carried out.
    0 indeksoimatonta files reviewed.

    0 indeksoimatonta files restored.

    CHKDSK check suojauskuvaimia (step 3 / 5) ...
    102,144 file-SD / security symbol processed.

    47 is deleted unused index configuration file 0x9 index $ SII.
    47 is deleted unused index configuration file 0x9 index $ SDH.
    47 is deleted unused suojauskuvainta.
    Suojauskuvainten review has been completed.
    17,917 data files processed.

    CHKDSK check USN Journal-file ...
    35944456 USN bytes-processed.

    USN Journal-file review is completed.
    CHKDSK will check the file data (stage 4 / 5) ...
    102,128 files processed.

    File data review conducted.
    CHKDSK to check the free space (stage 5 / 5) ...
    34455985 free clusters processed.

    Of free disk space check performed.
    Windows has checked the file system. No errors were detected.

    209612799 kilobytes total disk space.
    71525468 KB in 80,284 files.
    53,044 KB Index 17,918.
    0 KB in a damaged sector.
    210,347 KB in the system in use.
    65,536 KB in the log file to use.
    137823940 KB available disk.

    4096 bytes / cluster.
    52403199 reserve unit disc.
    34455985 units available for booking at the album.

    Internal data:
    00 8f 01 00 a6 7f 01 00 17 e3 02 00 00 00 00 00 ................
    94 0e 00 00 41 00 00 00 00 00 00 00 00 00 00 00 .... A. ..........
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

    Windows has checked the disc.
    Wait. The computer is restarted.

    That is the just runned CHKDSK /F /R (took 42minutes) :)

    The translator failed on that " Errors were detected " -thing. In my language there reads " No errors were detected ", so the NO word was missing somehow I fixed It on my own. Weird that the google translator failed like that.. But all good? :)

    Maybe you did see some errors on my first check because I didn't notice that translating failure My bad!
      My Computer


  4. Posts : 72
    Windows 7 64-bit
    Thread Starter
       #14

    Today I went to home and cold booted my pc and bsod came.. Now restarted and avast! doesn't work anymore.. I can't get It on. Here is the dump file:
    Typical BSOD situation, minidump check? Attached Files
      My Computer


  5. Posts : 5,705
    Win7 x64 + x86
       #15

    This is where I got the "errors" from:
    CHKDSK to check the free space (stage 5 / 5) ...
    34371864 free clusters processed. Of free disk space check performed.
    Windows has checked the file system. Errors were detected.
    If that was a translation glitch, then everything's OK.

    This BSOD blames the kernel of the OS (we don't believe that - so we have to look elsewhere).
    First, I'd uninstall Avast and reinstall it (or another antivirus).
    Then, since this is a pool error - it's a good place to run Driver Verifier according to these directions:
    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
    If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

    More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
      My Computer


  6. Posts : 72
    Windows 7 64-bit
    Thread Starter
       #16



    everytime I boot those things give me errors ?!?
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:57.
Find Us