BSOD on new PC

Page 2 of 2 FirstFirst 12

  1. Posts : 1,598
    Microsoft Window 7 Professional 32 bit
       #11

    The results from the DMP files do not give a definitive answer. While we investigate further here are a few things that you can do.

    1-Run a system file check to verify and repair you system files. You do this by typing cmd in search, then right click and run as admin. SFC/ SCANNOW

    2-Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

    3-Event viewer
    Go into event viewer (type eventvwr in search). Go to the windows log>application tab.

    You want to look for critical errors (they have red in the left column ).

    When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.

    When you find them please note the event ID, and the source codes and tell us what they are.

    4-Device manager
    Please go to start>search>type device manager.
    Are there any "unknown devices" with yellow triangles on them?
    Is you driver there , listed, and working?

    If y our driver is missing, or there is a yellow triangle on it, you will need to update it.

    5-Driver verifier
    please run Verifier with these settings:
    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).

    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"
    NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
    - 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:
    Code:
    Delete these registry keys (works in XP, Vista, Win7):
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
    More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
      My Computer


  2. Posts : 87
    Windows 7 Home Premium x64
    Thread Starter
       #12

    Nothing in device manager, sfc /scannow came back ok. I ran memtest over night...9 passes no errors and still the blue screens. 3 after my last post.

    Anyway, I've just been on the phone to the company that I bought it from and it's been RMA'd and going back today for testing etc

    If it had just started happening after having the PC for a while then I would have stuck with it but the fact that they have been happening from the moment I got the PC on Saturday then something is wrong somewhere and I think it's up to them to sort it out.

    Thanks again for your help, much appreciated.
      My Computer


  3. Posts : 87
    Windows 7 Home Premium x64
    Thread Starter
       #13

    Ok, quick update.

    Sent machine back last week...turned out to be faulty RAM. They replaced it and it's now working perfectly :)

    Thanks again for the help.
      My Computer


  4. Posts : 13,354
    Windows 7 Professional x64
       #14

    Thanks for the report!

    Glad it's working now.
      My Computer


  5. Posts : 87
    Windows 7 Home Premium x64
    Thread Starter
       #15

    Another update....I spoke too soon, blue screens started again so I'm sending it back and getting a refund.

    What is it with "new" computers these days they just don't seem to be as reliable as they used to be.

    I'm now back on a temporary 6 year old celeron that is so slow I keep thinking it's about to stop but it works...has not had one thing go wrong with it since the day it was bought. Hmmm that's tempting fate a bit
      My Computer


  6. Posts : 1,598
    Microsoft Window 7 Professional 32 bit
       #16

    I agree! hard question to answer but yes, new computer these days are not as reliable as before. I have heard somewhere a joke that, in order not to have BSODs, you should not install any 3rd party software, far away from your computer
      My Computer


 
Page 2 of 2 FirstFirst 12

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 23:33.
Find Us