Help please? Posted According to BSOD Posting Instructions.

Page 1 of 2 12 LastLast

  1. Posts : 21
    Windows 7 x64
       #1

    Help please? Posted According to BSOD Posting Instructions.


    Ok, here goes. A formal request for help according to the BSOD posting instructions.

    Is Windows 7 . . .
    - x64 ?
    - the original installed OS on the system? :No it is a new install.
    - an OEM or full retail version?: OEM full retail

    - What is the age of system (hardware)? ~ 1 year old
    - What is the age of OS installation (have you re-installed the OS?): ~5 days

    I tried to clear up the problem before the reinstall with no luck.

    I have run Memtest ~7 hours total with 0 errors.

    I have updated all drivers manually as well as Windows Updates.

    I have run Verifier although the system only crashes sporadically. Sometimes 4 times within 2 hours, but mostly once or twice a day.

    If it helps, my internet drops out on my router a few times a day but the system does not crash when this happens.

    Windows 7 x64

    CPU i7 860-no overclock
    Motherboard P55 FTW
    Memory: Supertalent DDR3-2000
    Graphics card: 2X GTX 260
    Sound Card On board Realtek
    Monitors 20" Samsung Syncmaster 2053 BW and 42" LG
    1.4TB and 500 GB hard drives
    PSU 850W Corsair
    Cooling VenomX with 6000 RPM Sanyo Denki
    Keyboard Microsoft Natural
    Mouse: Logitech trackman wireless
    Internet speed 30 Down



    Any help would be greatly appreciated.
      My Computer


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

    We have seen problems with the UltraMon program in the past - but haven't had any recent problems. Don't do anything with it right now - but keep it in mind for later on (if needed).

    Well, it looks like your copy of UltraMon is from 2008 - so please uninstall it. If that stops the BSOD's then we won't have to move on with hardware troubleshooting (which is what I suspect from the BSOD output). Please let us know if this fixes things. If not, we'll post some hardware troubleshooting tests.

    Please update these drivers:
    OLDER DRIVERS PRESENT IN THE DUMP FILES
    - Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
    - Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
    - DO NOT use Windows Update or the Update Drivers function of Device Manager.
    - Please feel free to post back about any drivers that you are having difficulty locating.
    - Windows Update exceptions may be noted below for Windows drivers:
    Code:
    
    amdxata.sys         Fri Mar 19 12:18:18 2010 (4BA3A3CA) - Windows Update will handle this one
    serscan.sys         Mon Jul 13 20:35:32 2009 (4A5BD2D4)
    RTKVHD64.sys        Fri Sep 03 04:02:27 2010 (4C80AB93)
    UltraMonUtility.sys Thu Nov 13 20:10:30 2008 (491CD006)
    nx6000.sys          Wed Jan 27 18:36:09 2010 (4B60CDE9)
    yk62x64.sys         Fri Dec 11 10:58:19 2009 (4B226C1B)
    dc3d.sys            Fri Apr 08 18:58:20 2011 (4D9F930C)
    
    http://www.carrona.org/dvrref.html#amdxata.sys
    http://www.carrona.org/dvrref.html#serscan.sys
    http://www.carrona.org/dvrref.html#RTKVHD64.sys
    http://www.carrona.org/dvrref.html#UltraMonUtility.sys
    http://www.carrona.org/dvrref.html#nx6000.sys
    http://www.carrona.org/dvrref.html#yk62x64.sys
    http://www.carrona.org/dvrref.html#dc3d.sys
    BSOD BUGCHECK SUMMARY
    Code:
    
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072411-16234-01.dmp]
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Sun Jul 24 12:39:59.343 2011 (UTC - 4:00)
    System Uptime: 0 days 2:10:21.250
    BugCheck D1, {57, 2, 0, fffff88000dc11b3}
    Probably caused by : ataport.SYS ( ataport!IdeSeverCompletedList+7f )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xD1_VRF_ataport!IdeSeverCompletedList+7f
    Bugcheck code 000000D1
    Arguments 00000000`00000057 00000000`00000002 00000000`00000000 fffff880`00dc11b3
    BiosVersion = 080016 
    BiosReleaseDate = 05/03/2011
    CPUID:        "Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2801
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072411-17734-01.dmp]
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Sun Jul 24 06:00:20.041 2011 (UTC - 4:00)
    System Uptime: 0 days 0:59:59.962
    Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID:  X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff800`02c7ac25 fffff880`0972afc0 00000000`00000000
    BiosVersion = 080016 
    BiosReleaseDate = 05/03/2011
    CPUID:        "Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2801
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072411-18218-01.dmp]
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Sun Jul 24 04:59:11.517 2011 (UTC - 4:00)
    System Uptime: 0 days 2:07:15.439
    BugCheck D1, {80, 2, 0, fffff8800441b74f}
    *** WARNING: Unable to verify timestamp for RTKVHD64.sys
    *** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
    Probably caused by : HDAudBus.sys ( HDAudBus!HdaController::ProcessCodecTransferList+6f )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0xD1_HDAudBus!HdaController::ProcessCodecTransferList+6f
    Bugcheck code 000000D1
    Arguments 00000000`00000080 00000000`00000002 00000000`00000000 fffff880`0441b74f
    BiosVersion = 080016 
    BiosReleaseDate = 05/03/2011
    CPUID:        "Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2801
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072411-16859-01.dmp]
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Debug session time: Sun Jul 24 02:50:45.958 2011 (UTC - 4:00)
    System Uptime: 0 days 6:31:56.989
    Probably caused by : fltmgr.sys ( fltmgr! ?? ::FNODOBFM::`string'+2b02 )
    BUGCHECK_STR:  0xc2_7
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  uTorrent.exe
    FAILURE_BUCKET_ID:  X64_0xc2_7_fltmgr!_??_::FNODOBFM::_string_+2b02
    Bugcheck code 000000C2
    Arguments 00000000`00000007 00000000`0000109b 00000000`35324d43 fffffa80`0700da20
    BiosVersion = 080016 
    BiosReleaseDate = 05/03/2011
    CPUID:        "Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz"
    MaxSpeed:     2800
    CurrentSpeed: 2801
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
      
      
      My Computer


  3. Posts : 21
    Windows 7 x64
    Thread Starter
       #3

    Ok, As instructed I have Updated windows again (this updates amdxata.sys and serscan.sys)

    I have updated RTKVHD64.sys (Realtek driver)

    I have removed UltraMonUtility.sys

    I have updated nx6000.sys (Lifecam driver)

    I have updated yk62x64.sys (from EVGA website) it is the Marvell network driver. (this one is questionable)

    I have run the update for dc3d.sys (Intellipoint software for MWK-5000 and mouse) although it says I was already up to date.

    I am following your instructions to the letter.

    I also ran Memtest overnight last night. There were no errors, but the screen was covered with wierd ascii symbols and the computer had restarted itself. Again, there were no errors present. This leads me to believe that the problem is hardware related.
      My Computer


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

    Yes, display errors in MemTest are likely to be hardware.
    How many passes did MemTest complete?

    I suspect it's heat related - open the side of the case and point a house fan at the mobo.
    Then run MemTest overnight.
    Does it still give the distorted graphics?

    If not, then try with only 1 video card and no house fan
    Then try the other video card (alone) and no house fan
      My Computer


  5. Posts : 21
    Windows 7 x64
    Thread Starter
       #5

    I ran Memtest for at least 10 passes w/o fail.

    As far as heat related, the computer can crash randomly w/o regard to heat. Also I monitor the temp and it never goes over 32ฐC. I also have 7 120mm CPU fans that all work. The CPU fan is a Sanyo Denki 6000 RPM fan (running at 2000) on a Venom X.

    There is a 240mm Fan in the door of my Cooler Master HAF 932, so although I won't rule out cooling I would say a house fan probably wouldn't net me any benefit. I will do as suggested though. I will also try my individual cards to see if it crashes.

    First however I will wait on the next crash. Verifier is not crashing me at the moment.

    Thank you.
      My Computer


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

    Fan on the video card?
    Video card temps? Have you run a video stress test such as FurMark?
    Have you checked the video card power, cooler and fan?
    FYI - I don't have much experience with multi-GPU setups, so please bear with me.

    Long story, but too many fans may be just as bad as too few fans - depending on the airflow pattern through the case. The house fan will force air to the entire mobo - thereby ruling out any fan balancing issues. As you say, it's probably not a concern - but if everything was OK, you wouldn't be posting here.

    What settings are you using on Driver Verifier? I recommend the following (it stresses 3rd party drivers and leaves Windows drivers alone):
    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" and "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
    Here's my canned speech for hardware diagnostics. Furmark is in the second section:
    I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
    H/W Diagnostics:
    Please start by running these bootable hardware diagnostics:
    Memory Diagnostics (read the details at the link)
    HD Diagnostic (read the details at the link)

    Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Resources (read the details at the link)
    Then, if the above tests pass, I'd try these free stress tests:
    FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
    FurMark Setup:
    - If you have more than one GPU, select Multi-GPU during setup
    - In the Run mode box, select "Stability Test" and "Log GPU Temperature"
    Click "Go" to start the test
    - Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
    NOTE: Set the alarm to go off at 90บC. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
    - Click "Quit" to exit
    Prime95 download site: http://www.mersenne.org/freesoft/
    Prime95 Setup:
    - extract the contents of the zip file to a location of your choice
    - double click on the executable file
    - select "Just stress testing"
    - select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
    - "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
    The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
    Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
    This won't necessarily crash the system - but check the output in the test window for errors.
    The Test selection box and the stress.txt file describes what components that the program stresses.
    More details on the use of this test: Torture test your CPU with Prime95
    More Video Stress Tests:
    1. Thanks to VirGnarus for finding this test: https://simtk.org/home/memtest
    2. Two other video stress tests (may be more stressful than FurMark):
    Video Memory stress Test - ะœะ˜ะ NVIDIA / ะฃั‚ะธะปะธั‚ั‹ / VMT
    Artifact Locator - ะœะ˜ะ NVIDIA / ะฃั‚ะธะปะธั‚ั‹ / Artifact Locator
    Sorry, but I don't read the language that this website is made in.
    3. Another interesting test that came to my attention: Download - OCCT Website english
    USE AT YOUR OWN RISK - the program doesn't have a whole bunch of safety features to protect you from yourself!
      My Computer


  7. Posts : 21
    Windows 7 x64
    Thread Starter
       #7

    Left Verifier running and nvlddmkm.sys crashed and would not reboot until I deleted verifier settings in bios.

    a) Since this problem happens both in and out of Windows (Dos Mode) - Video Card is suspected.
    b) Since the screen appeared corrupted during Memtest with no memory errors - Video Card is suspected.
    c) Since no other obvious driver failures (just random) except for nvlddmkm.sys appear - Video card is suspected.


    Per your suggestion I am going to run Furmark and do some extensive video card tests, then swap out each to see if this resolves the problem.
      My Computer


  8. Posts : 21
    Windows 7 x64
    Thread Starter
       #8

    OK, I am at my wits end. Continued ntoskrnl.exe faults. Random BSODs

    Swapped PSU and Motherboard. (Still BSODs)

    In the new motherboard I ran one video card (BSOD)

    Then the other video card (BSOD)

    I then ran one ram stick, checked and passed memtest (BSOD)

    I ran the other stick, checked and passed memtest (BSOD)

    I re-installed windows on another HDD (BSOD)

    I used a different Keyboard (BSOD)

    I am at my wits end, can anyone help me? Did I miss something? Could my CPU be causing these errors?
      My Computer


  9. Posts : 21
    Windows 7 x64
    Thread Starter
       #9

    I just noticed running prime95 causes computer to freeze or crash. It doesn't matter if its small ffts or blend. I suspect failure of the CPU, going to reseat my HSF to cover bases, but I can duplicate the problem now.
      My Computer

  10.   My Computer


 
Page 1 of 2 12 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 10:15.
Find Us