Totally Random BSOD with windows 7 64 and RIVE

Page 1 of 8 123 ... LastLast

  1. Posts : 40
    Windows 7 ultimate 64bits
       #1

    Totally Random BSOD with windows 7 64 and RIVE


    Hi guys,

    I've been plagued with BSODs with my new build and I can't figure out where it comes from. My brand new PSU platimax 1500 died after a couple of days of use so I thought that it might have the cause so I bought an ax1200, still getting random freezes and bsods.

    I tested the RAM individually, in different slots and on my old rig, they are all fine.

    I tried with only one graphic card, tested each of them individually on the new and old rig, they all work perfectly.

    Ran Prime95 on my CPU, no pbs there.

    I'm down to the MB which I really don't know how to test. I wanted to buy a new one but the seller said to make certain that it isn't a drivers conflict before RMA and I think that he might be right. The PC crashes on Idle or while I'm using it, it's totally random. Sometimes it takes 5 hours, other times every 10 minutes.

    I noticed two things though:

    - I couldn't get it to crash on a fresh install of windows, with nothing else installed
    - I can't run memtest86, the memtest screen at boot flashes for a sec and it reboots, flashes again and reboots over and over. I ran memtest86 on my current RAM on my old rig though, couldn't find any problems.

    I'm getting insane guys

    Specs:

    MB: ASUS RIVE
    CPU: i7-3960x
    GPU: 3 x GTX580 (SLI not activated -> BSOD when I try)
    RAM: 4 x 4GB Ripjawz 1866
    HDD: Vertex 3 240GB
    OS: Windows 7 Ultimate 64bits
    The whole lot is water cooled so no temp problem.

    I'm attaching the zip as instructed (jcgriff2 and html file)
      My Computer


  2. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #2

    It is a pity you couldn't get Memtest to run for 5 to 6 passes.

    If you are overclocking anything reset to default before running the test below.
    In other words STOP!!!

    Read the below very carefully...

    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 "Special Pool", "Force Pending I/O Requests" and "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:
    Code:
    Delete these registry keys to stop Driver Verifier from loading (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
    Using Driver Verifier to identify issues with Windows drivers for advanced users
      My Computer


  3. Posts : 40
    Windows 7 ultimate 64bits
    Thread Starter
       #3

    Ok, I'll try and get back to you.

    I ran memtest 5 or 6 times on each ram on my old PC, no pbs found. And I haven't overclocked yet.

    I'm also attaching a new dump file because I had quite a few BSODs since the first post

    Oh and I stressed the cpu in safe mode for 5 hours, no pbs
    Last edited by yannickhk; 28 Jan 2012 at 00:08. Reason: adding an attachment
      My Computer


  4. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #4

    Good luck!
      My Computer


  5. Posts : 40
    Windows 7 ultimate 64bits
    Thread Starter
       #5

    waiting for the BSOD right now, with verifier running (I hope :) )
      My Computer


  6. Posts : 40
    Windows 7 ultimate 64bits
    Thread Starter
       #6

    lol, it ain't crashing
      My Computer


  7. Posts : 28,845
    Win 8 Release candidate 8400
       #7

    yannickhk said:
    waiting for the BSOD right now, with verifier running (I hope :) )

    None of these appear to have been run with verifier enabled. Please type verifier /query and tell us what drivers are being verified.



    Now one constant through most of your crashes there has been one of two Asus drivers as the active thread when the crash occurred.


    They are Related to atkexComSvc.exe from ASUSTeK Computer Inc.

    and Related to AsIO.sys System service from ASUS..



    I would update ALL Asus drivers to the most current version available.

    I am unsure because I am not at my computer but if you are overclocking stop.
      My Computer


  8. Posts : 40
    Windows 7 ultimate 64bits
    Thread Starter
       #8

    Here goes, just had 4 bsods in a row
      My Computer


  9. Posts : 40
    Windows 7 ultimate 64bits
    Thread Starter
       #9

    zigzag3143 said:
    yannickhk said:
    waiting for the BSOD right now, with verifier running (I hope :) )

    None of these appear to have been run with verifier enabled. Please type verifier /query and tell us what drivers are being verified.



    Now one constant through most of your crashes there has been one of two Asus drivers as the active thread when the crash occurred.


    They are Related to atkexComSvc.exe from ASUSTeK Computer Inc.

    and Related to AsIO.sys System service from ASUS..



    I would update ALL Asus drivers to the most current version available.

    I am unsure because I am not at my computer but if you are overclocking stop.
    Thanks for the info, i'm going to download all the drivers from the asus site now.

    Only in the last post have I attached the files with verifier activated

    Edit: I already have the latest drivers
      My Computer


  10. Posts : 28,845
    Win 8 Release candidate 8400
       #10

    yannickhk said:
    Here goes, just had 4 bsods in a row
    Are they driver verified? what drivers did verifiy /query say it was verifying?


    You might want run malwarebytes just in case.

    Please download the free version of Malwarebytes.
    Update it immediately.
    Do a full system scan
    Let us know the results at the end.



    http://www.malwarebytes.org/products
      My Computer


 
Page 1 of 8 123 ... LastLast

  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 03:47.
Find Us