Quantcast
Page 1 of 2 12 LastLast
Results 1 to 10 of 19
Like Tree2Likes

BSOD Might be Hardware, but I can't tell

  1. #1
    Jared Witt is offline Junior Member
    Enjoys Windows 7 Forums
     
    Join Date
    Jun 2011
    Posts
    11

    BSOD Might be Hardware, but I can't tell

    Hello all, I hate for this to be my first post, but oh well. I've seen threads similar to this one but of course not the same. I've been getting BSODs lately. First it started with a couple while I was sleeping, then they started to happen while I was using the computer, and eventually got so bad that I couldn't even boot to the BIOS with out multiple tries. I believe it is hardware related, but I don't know what hardware is causing the problem.

    Things I've done:
    Reinstalled the entire OS
    Took out all but 2 gigs of RAM (based on some other thread's suggestions)
    Reseated Video Card and Ram, as well as reset the BIOS by removing the battery.
    After Reinstalling OS, removed the nVidia HD Audio Drivers, they may reinstall during reboot though...

    Dumps.zip
    Any help or insight is appreciated. I'm still well with-in warranty of my video card, and I want to get more RAM anyways, so I wouldn't mind finding out they are broken, I just need to know if they are.

    Some System Specs:

    Windows 7 Ultimate 64-bit
    AMD Athlon 64 x2 6000+ (Windsor 90nm Tech...)
    2.0 GB Dual-Channel DDR2 @ 334 MHz (5-5-5-15) *3 before removing some. Going to upgrade to 8)
    ECS Nettle2 MOBO
    nVidia GeForce GTS 450 (I think it's the audio drivers on this one that causes it)
    488 gb Western Digital WDC WD50

    That might be more than you need, but once again THANKS!

    Reply With Quote Reply With Quote

  2. #2
    Captain Jack's Avatar
    Captain Jack is offline Tier 2 Moderator
    Microsoft MVP - Windows Expert
    (IT Pro)
     
    Join Date
    Mar 2010
    Posts
    959
    Blog Entries
    1

    Re: BSOD Might be Hardware, but I can't tell

    Hi there,

    Seems like the causes of crashes are random so more likely it could be some Hardware that's causing the system to crash. Go follow this link Hardware Diagnostic | Captain Debugger and run a complete Hardware Diagnostic

    If your Overclocking please reset to default settings.

    Update the following Drivers:

    Code:
    SoftK56 Modem Driver:
    VSTCNXT6.SYS Thu Oct 16 06:22:22 2008
    VSTDPV6.SYS  Thu Oct 16 06:27:45 2008
    VSTBS26.SYS  Thu Oct 16 06:24:06 2008 
    
    RTCore64.sys Wed May 25 12:09:12 2005 - Afterburner  (Very important should update to remove it)

    Code:
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000000403, The subtype of the bugcheck.
    Arg2: fffff68000020fd8
    Arg3: feb000004c8de867
    Arg4: ffffc68000020fd8
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x1a_403
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80002f407d8 to fffff80002ece700
    
    STACK_TEXT:  
    fffff880`04f3b7b8 fffff800`02f407d8 : 00000000`0000001a 00000000`00000403 fffff680`00020fd8 feb00000`4c8de867 : nt!KeBugCheckEx
    fffff880`04f3b7c0 fffff800`02eff401 : 00000000`00000000 fffff680`00020ff8 fffffa80`01948630 00000000`00048093 : nt! ?? ::FNODOBFM::`string'+0x31eb2
    fffff880`04f3b970 fffff800`02f1016a : 00000000`00000000 00000000`04f95fff fffffa80`00000000 fffffa80`00000000 : nt!MiDeleteVirtualAddresses+0x408
    fffff880`04f3bb30 fffff800`02ecd953 : ffffffff`ffffffff 00000000`0145ebf8 00000000`0145ebf0 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
    fffff880`04f3bc20 00000000`7782f89a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0145ebb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7782f89a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+31eb2
    fffff800`02f407d8 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+31eb2
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd34
    
    FAILURE_BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+31eb2
    
    BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+31eb2
    
    Followup: MachineOwner
    ---------
    Shyam Sasindran
    Microsoft MVP





    Reply With Quote Reply With Quote

  3. #3
    Jared Witt is offline Junior Member Thread Starter Thread Starter
    Enjoys Windows 7 Forums
     
    Join Date
    Jun 2011
    Posts
    11

    Re: BSOD Might be Hardware, but I can't tell

    Hello,

    Thanks for the reply. I believe I've done everything you asked.

    I ran MemTest86+ with no errors reported.
    Ran chkdsk without problems.
    Reset the OC to factory (btw, it's factory OC'd, here's a link to the card: Newegg.com - GIGABYTE GV-N450OC-1GI GeForce GTS 450 (Fermi) 1GB 128-bit GDDR5 PCI Express 2.0 x16 HDCP Ready SLI Support Video Card, )Attachment 13931 and then uninstalled Afterburner
    Reinstalled all the nVidia drivers, and stress tested with furmark. Never have gotten over 80 degrees, so it's not a heat problem.
    Update the drivers you asked. I updated my modem driver through the device manager, 'successfully.' They now show a 2009 date.

    Also, I noticed that when it crashes when I use it the audio hangs and repeats itself (like a loop of a eighth of a second). I don't use the HDMI cable, so the audio drivers are useless to me, but disabling them didn't see to work as I have had a few more BSOD while I was away. I'll attach them, thanks!

    new dumps.zip

    Reply With Quote Reply With Quote

  4. #4
    Captain Jack's Avatar
    Captain Jack is offline Tier 2 Moderator
    Microsoft MVP - Windows Expert
    (IT Pro)
     
    Join Date
    Mar 2010
    Posts
    959
    Blog Entries
    1

    Re: BSOD Might be Hardware, but I can't tell

    Hi there,

    Do you use any third party Antivirus / Firewall? If so uninstall it completely and use the removal tool and cleanup the left over files. Enable Driver Verifier Using Driver Verifier to identify issues with Drivers - Windows 7 Forums for 36 hours.

    Run SFC /SCANNOW SFC /SCANNOW to Repair Windows 7 Files | Captain Debugger

    Report us back with results
    Shyam Sasindran
    Microsoft MVP





    Reply With Quote Reply With Quote

  5. #5
    Saltgrass is online now Microsoft Community Contributor This member is a certified Microsoft Community Contributor at Windows 7 Forums. Click here for more information from Microsoft.
    Just trying to help
     
    Join Date
    Oct 2009
    Posts
    6,483

    Re: BSOD Might be Hardware, but I can't tell

    I believe the RTcore64 file is associated with the EVGA Precision software. The 2005 file has been replaced recently with a 2011 version if you download the new version of that utility. So if you are using that utility, or have used it, you might want to check.

    If you are no longer using it, you might want to check msconfig.exe to see if it is still listed during startup.

    FYI, the 32 bit version is still dated 2005.

    Reply With Quote Reply With Quote

  6. #6
    Jared Witt is offline Junior Member Thread Starter Thread Starter
    Enjoys Windows 7 Forums
     
    Join Date
    Jun 2011
    Posts
    11

    Re: BSOD Might be Hardware, but I can't tell

    Captain: Thanks for the reply, I do NOT have a 3rd party firewall installed as of now. I have yet to install ESET nod32, but will once everything is working. I will have to wait until tomorrow to enable driver verification and to run SFC because I have to finish a graduation video. (Party is tomorrow). I'll report back with results then.

    Saltgrass: RTCore is not listed in my start-up nor services tab under msconfig. I do not have a EVGA card, and cannot find the EVGA Precision software anywhere on my add/remove programs. If you suggest it I will install the EVGA Percision if you think it will help.


    The good news is: I haven't had any BSOD's logged in the minidump folder since my last post. I even had mIRC running all night so I know it didn't even shut down. Maybe we are getting somewhere!

    Thanks again guys

    Reply With Quote Reply With Quote

  7. #7
    Jared Witt is offline Junior Member Thread Starter Thread Starter
    Enjoys Windows 7 Forums
     
    Join Date
    Jun 2011
    Posts
    11

    Re: BSOD Might be Hardware, but I can't tell

    After around 20 failed attempts at booting and a rediculous about of blue screening the past day, I was going through the bios and I disabled a setting in the BIOS under the advanced tab. It was the PS/2 setting, which I disable because it said it would "Free up IRQ12". I remember on a lot of the BSODs it mentioned IRQ something something, so I disabled it and it booted fullyon the first try. Restarted, and it booted again perfectly. Third time worked as well. After browsing on firefox I got this BSOD (newest folder) which appears to be different then the other ones, any suggestions?

    Moar BSOD.zip



    I can do the Driver Verifier too if that will help, yes/no?

    Thanks!

    Reply With Quote Reply With Quote

  8. #8
    Captain Jack's Avatar
    Captain Jack is offline Tier 2 Moderator
    Microsoft MVP - Windows Expert
    (IT Pro)
     
    Join Date
    Mar 2010
    Posts
    959
    Blog Entries
    1

    Re: BSOD Might be Hardware, but I can't tell

    Hi there,

    Seems like VKbms.sys i.e. Virtual HID Minidrive could be causing it . I would recommend to remove it. Also Yes I would recommend to Enable Driver Verifier.

    Code:
    Unable to load image \SystemRoot\system32\DRIVERS\VKbms.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for VKbms.sys
    Shyam Sasindran
    Microsoft MVP





    Reply With Quote Reply With Quote

  9. #9
    Jared Witt is offline Junior Member Thread Starter Thread Starter
    Enjoys Windows 7 Forums
     
    Join Date
    Jun 2011
    Posts
    11

    Re: BSOD Might be Hardware, but I can't tell

    I enabled driver verifier and these where the Bluescreens that may or may not have resulted from it:

    Post DV.zip





    I also ran SFC as directed and when it was finished it said this:
    Verification 100% complete.
    Windows Resource Protection did not find any integrity violations.
    Note: The first SFC I ran was interrupted at around 50% by a "Memory Management" bluescreen. I was on Firefox

    If it helps, these are the files that are now in the Windows>Logs>CBS folder, exactly how I found them.

    CBS.zip


    Thanks again Captain!

    Reply With Quote Reply With Quote

  10. #10
    Jared Witt is offline Junior Member Thread Starter Thread Starter
    Enjoys Windows 7 Forums
     
    Join Date
    Jun 2011
    Posts
    11

    Re: BSOD Might be Hardware, but I can't tell

    I got another blue screen this morning that said "DRIVER_CORRUPTED_MMPOOL" and using BlueScreenView it says it was caused by ntoskrnl.exe. Reading around I found:
    In my experience if this is a hardware fault it's invariably memory ?
    Time for some new RAM?

    Here's the dmp file.

    060711-15178-01.zip
    Last edited by Jared Witt; 06-07-2011 at 01:11 PM.

    Reply With Quote Reply With Quote

Page 1 of 2 12 LastLast

Similar Threads

  1. BSOD and hardware issue
    By Temzen in forum Blue Screen of Death (BSOD)
    Replies: 14
    Last Post: 10-19-2011, 05:42 PM
  2. [CRASH] BSOD. 0x00000124 hardware problem.
    By hasanagas in forum Blue Screen of Death (BSOD)
    Replies: 1
    Last Post: 05-04-2011, 09:23 AM
  3. Replies: 1
    Last Post: 03-20-2011, 08:01 AM
  4. Replies: 11
    Last Post: 12-14-2010, 02:16 PM
  5. Daily BSOD - Hardware or Software?
    By sraisz in forum Blue Screen of Death (BSOD)
    Replies: 2
    Last Post: 01-11-2010, 03:15 PM

Visitors found this page by searching for:

Search engine data is still being processed!

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •