none
BSOD on fresh W7 install RRS feed

  • Question

  • https://skydrive.live.com/redir?resid=3E78E857E67EB0B1!107

    Any idears?

    Win 7 64 Bit

    Asus P8Z77-V PRO

    Intel 3570k

    GSkill Sniper DDR3-1866

    Mushkin Chronos Deluxe 240 6GB/s


    Saturday, December 1, 2012 7:19 PM

Answers

  • Your crashes were caused by memory corruption (possibly caused by Chrome]. 

    Please run these two tests to verify your memory and find which driver is causing the problem.  

    *Don't forget to upload any further DMP files (especially those when verifier is running)

    *If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!  

    If you don't know what this means you probably arent


    1-Memtest.

    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org  
    *Boot from the CD, and leave it running for at least 5 or 6 passes.
    *Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
    *Test the sticks individually, and if you find a good one, test it in all slots.
    Any errors are indicative of a memory problem.
    If a known good stick fails in a motherboard slot it is probably the slot.

    2-Driver verifier

    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.

    *I'd suggest that you first backup your data 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).

    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.

    *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.

    *Further Reading
    "http://support.microsoft.com/kb/244617"

    Using Driver Verifier to identify issues with Windows drivers for advanced users

    Sunday, December 2, 2012 6:00 AM

All replies

  • Miles

    This single DMP file was inconclusive, we need more dmps to spot trends etc. Of note you need SP-1 and may as well do it now (it may well fix the issue)

    Please run the System Update Readiness Tool (SURT)  and then update to SP-1

    32 Bit
    http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=3132

    64 Bit
    http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=20858


    Now update to SP-1

    http://windows.microsoft.com/installwindows7sp1

    Learn how to install Windows 7 Service Pack 1 (SP1) http://windows.microsoft.com/en-US/windows7/learn-how-to-install-windows-7-service-pack-1-sp1

     Additional Resources:

    http://windows.microsoft.com/en-US/windows7/uninstall-sp1
    http://windows.microsoft.com/troubleshootwindows7sp1


    MS-MVP 2010, 2011, 2012 Team ZigZag

    Sunday, December 2, 2012 2:47 AM
    Moderator
  • Thanks for the quick reply!

    I decided to do a fresh install of Windows 8 64 bit.  Ran fine for a while, 3 crashes so far though.

    https://skydrive.live.com/redir?resid=3E78E857E67EB0B1!107

    I'm 100% up to date with Windows updates so far as I can tell.  I uninstalled my Gamecom 780 drivers and will leave them disabled until they release a W8 driver, seems as though others have pin pointed them as their BSOD culprit. 

    I'm just worried that one of my components is bad.  Any SSD test or memtest I run test 100%.

    • Edited by Kilomph Sunday, December 2, 2012 3:16 AM
    Sunday, December 2, 2012 3:14 AM
  • Your crashes were caused by memory corruption (possibly caused by Chrome]. 

    Please run these two tests to verify your memory and find which driver is causing the problem.  

    *Don't forget to upload any further DMP files (especially those when verifier is running)

    *If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!  

    If you don't know what this means you probably arent


    1-Memtest.

    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org  
    *Boot from the CD, and leave it running for at least 5 or 6 passes.
    *Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
    *Test the sticks individually, and if you find a good one, test it in all slots.
    Any errors are indicative of a memory problem.
    If a known good stick fails in a motherboard slot it is probably the slot.

    2-Driver verifier

    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.

    *I'd suggest that you first backup your data 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).

    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.

    *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.

    *Further Reading
    "http://support.microsoft.com/kb/244617"

    Using Driver Verifier to identify issues with Windows drivers for advanced users

    Sunday, December 2, 2012 6:00 AM
  • Patrick

    JMH3143 is correct (as usual).  Since you have had these issues with 2 OS'es I would think hardware first.  I am unsure if you have run memtest from boot for 6-8passes but I would do that just to be sure.

    As JMH suggests driver verifer will usually crash (a good thing) and identify the culprit driver.  Those DMPS will be more specific.


    MS-MVP 2010, 2011, 2012 Team ZigZag

    Sunday, December 2, 2012 6:01 AM
    Moderator
  • Sounds like a plan!  I'll bring my work laptop home with me tomorrow and give it a go.

    Thanks!
    Sunday, December 2, 2012 6:22 AM
  • So I started running Memtest last night and after about 45 minutes had 300k errors.  Went to bed and just started messing around again.  Seems as though one stick of my 8GB pair (GSkill Sniper) is bad.  I've tested the other stick in two slots so far and 0 errors as of now.  

    Hopefully that's my issue, if not I'll keep you updated.  Thanks for the help!!!
    Monday, December 3, 2012 1:37 AM
  • Well lets hope that solves the issue.  Let us know if you need help


    MS-MVP 2010, 2011, 2012 Team ZigZag

    Monday, December 3, 2012 3:44 AM
    Moderator