none
Windows 7 BSOD on Fresh install RRS feed

  • Question

  • I can't read the minidump files.  If someone can decipher the minidump for me to pinpoint what's causing the problem.

    http://cid-32695fc97207f956.skydrive.live.com/browse.aspx/BSOD%206%5E_2%5E_10

    Thursday, June 3, 2010 12:30 AM

Answers

All replies

  • The crash dump appears to be corrupt and is not readable.

     

    Can you upload the crash dumps from c:\windows\minidump to SkyDrive and provide a link?

    FWIW, general guidance for dealing with bluescreens:

    Consider running chkdsk on all partitions.  Let chkdsk complete on each partition and see if that helps.

    Also consider running SFC /SCANNOW.

    It can be helpful to use Driver Verifier.  To enable Driver Verifier... start->verifier.exe->OK->Create standard settings->Next->select driver names from a list->Next->sort by Provider->select all non-Microsoft drivers->Finish, and OK your way out of the dialog.

    Then, reboot and use the system as you normally would, and wait for a problem.  In the event that the system does not boot completely after enabling driver verifier, boot into Safe Mode and run driver verifier, and tell it to delete the changes.

    Wait for a bugcheck to occur after enabling verifier as described, and then upload the dump to your SkyDrive, and provide a link.

    If you boot into safe mode, do you still experience bugchecks? What about if you do a clean boot, or device clean boot?

    Consider testing memory with Windows Memory Diagnostic or memtest86. Note that memory that passes tests is not necessarily good memory - it just hasn't failed a test.  Consider systematically eliminating RAM from the system - run with a couple of modules for a while, and see how things go. Then try the other modules.

    Other common suggestions include ensuring drivers are up to date, as well as ensuring that you're using the latest BIOS. 

    Thursday, June 3, 2010 12:36 AM
  • I left the computer on and it BSOD today.  Here is the location of the latest minidump, hopefully it's not corrupt.

    http://cid-32695fc97207f956.skydrive.live.com/self.aspx/BSOD%206%5E_3%5E_10/060310-13634-01.dmp

    In addition here are the event log properties in XML view.

    <script type="text/javascript"></script>

    - < Event xmlns =" http://schemas.microsoft.com/win/2004/08/events/event " >
    - < System >
      < Provider Name =" Microsoft-Windows-Kernel-Power " Guid =" {331C3B3A-2005-44C2-AC5E-77220C37D6B4} " />
      < EventID > 41 </ EventID >
      < Version > 2 </ Version >
      < Level > 1 </ Level >
      < Task > 63 </ Task >
      < Opcode > 0 </ Opcode >
      < Keywords > 0x8000000000000002 </ Keywords >
      < TimeCreated SystemTime =" 2010-06-03T16:51:48.300013700Z " />
      < EventRecordID > 2642 </ EventRecordID >
      < Correlation />
      < Execution ProcessID =" 4 " ThreadID =" 8 " />
      < Channel > System </ Channel >
      < Computer > Nhan-PC </ Computer >
      < Security UserID =" S-1-5-18 " />
      </ System >
    - < EventData >
      < Data Name =" BugcheckCode " > 24 </ Data >
      < Data Name =" BugcheckParameter1 " > 0x0 </ Data >
      < Data Name =" BugcheckParameter2 " > 0x4547fa8005fe6e60 </ Data >
      < Data Name =" BugcheckParameter3 " > 0x2 </ Data >
      < Data Name =" BugcheckParameter4 " > 0xffff00000000001c </ Data >
      < Data Name =" SleepInProgress " > false </ Data >
      < Data Name =" PowerButtonTimestamp " > 0 </ Data >
      </ EventData >
      </ Event >

    Also, at the same time there was a bug check event which took place 6 seconds after. 

    - < Event xmlns =" http://schemas.microsoft.com/win/2004/08/events/event " >
    - < System >
      < Provider Name =" Microsoft-Windows-WER-SystemErrorReporting " Guid =" {ABCE23E7-DE45-4366-8631-84FA6C525952} " EventSourceName =" BugCheck " />
      < EventID Qualifiers =" 16384 " > 1001 </ EventID >
      < Version > 0 </ Version >
      < Level > 2 </ Level >
      < Task > 0 </ Task >
      < Opcode > 0 </ Opcode >
      < Keywords > 0x80000000000000 </ Keywords >
      < TimeCreated SystemTime =" 2010-06-03T16:51:54.000000000Z " />
      < EventRecordID > 2657 </ EventRecordID >
      < Correlation />
      < Execution ProcessID =" 0 " ThreadID =" 0 " />
      < Channel > System </ Channel >
      < Computer > Nhan-PC </ Computer >
      < Security />
      </ System >
    - < EventData >
      < Data Name =" param1 " > 0x00000018 (0x0000000000000000, 0x4547fa8005fe6e60, 0x0000000000000002, 0xffff00000000001c) </ Data >
      < Data Name =" param2 " > C:\Windows\Minidump\060310-13634-01.dmp </ Data >
      < Data Name =" param3 " > 060310-13634-01 </ Data >
      </ EventData >
      </ Event >


    Please let me know if there are any other information I can provide.  I am really frustrated because of this.  I am currently trying to uninstall/disable software that I think may cause this.

     

    Thursday, June 3, 2010 10:42 PM
  • The dump is again corrupt, it seems.

    The bugcheck details in the event log suggest that you got bugcheck 0x24 (NTFS_FILE_SYSTEM) and bugcheck 0x18 (REFERENCE_BY_POINTER).

    Lately when I've seen the 0x24 bugcheck, it's been due to or related to memory or some other form of corruption.  Can you run chkdsk and see what that may turn up?  Similarly, corruption could be responsible for the 0x18 bugcheck, as well as the reason that the dumps are corrupt.  First run chkdsk and see what happens.

    Also - can you download, extract, and run Process Explorer?  Choose File->Show Details for all Processes, and then select the SYSTEM process (PID 4). Press CTRL+D and right-click the column header in the lower pane.  Choose Select Columns, and in the property sheet that appears with the DLL page selected, check all boxes and click OK.  Then choose File->Save, and save the report.  Upload the report to your SkyDrive and provide a link.

    Friday, June 4, 2010 11:11 AM
  • Thanks for the help.  However, I noticed that I didn't get any BSOD prior to installing AVG Free so I uninstalled it.  I have been running for 24 hours now without any BSODs.
    Friday, June 4, 2010 11:05 PM