Frequent BSoD on New Desktop

Page 1 of 2 12 LastLast

  1. Posts : 26
    Windows 7 Home Premium 64bit
       #1

    Frequent BSoD on New Desktop


    Hello,

    I am having frequent BSoD on my desktop which I built this past Christmas. The hardware is only about 7 months old. I am running a full new version of Windows 7 Home Premium 64 bit which was installed when the computer was assembled 7 months ago.

    The BSoD were originally most common during games, but now they are frequent (every 1-2 days) during random times. The computer frequently shuts down while watching videos or browsing the internet or during a game.

    There are only a few BSoD crash reports because cleaning programs I have used in the past cleaned the dump file folder without me realizing it was important. Attached are just a few of the most recent crashes although there have been dozens.

    Any help would be appreciated. Thank you.
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    The Nvidia driver is the cause,
    Uninstall it and use Driver Sweeper to remove leftover nvidia display driver files
    Then reinstall the Nvidia driver

    If BSODs still occur test your RAM and Graphic card
    RAM - Test with Memtest86+
    https://www.sevenforums.com/tutorials...test-occt.html
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {0, 0, 0, 0}
    
    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+816e0 )
    
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: 0000000000000000, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
    
    FAULTING_IP: 
    +0
    00000000`00000000 ??              ???
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000000
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x1E
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    EXCEPTION_RECORD:  fffff8800305b738 -- (.exr 0xfffff8800305b738)
    ExceptionAddress: fffff80003094c16 (nt!KeSetEvent+0x0000000000000016)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    TRAP_FRAME:  fffff8800305b7e0 -- (.trap 0xfffff8800305b7e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80003094c16 rsp=fffff8800305b970 rbp=0000000000000410
     r8=0000000000000000  r9=000000000000001f r10=00000000000002d4
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    nt!KeSetEvent+0x16:
    fffff800`03094c16 f6037f          test    byte ptr [rbx],7Fh ds:1000:00000000`00000000=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800030886be to fffff80003090cd0
    
    STACK_TEXT:  
    fffff880`0305a818 fffff800`030886be : fffffa80`09e93660 fffffa80`0a219080 fffff880`0305af90 fffff800`030bc890 : nt!KeBugCheck
    fffff880`0305a820 fffff800`030bc55d : fffff800`03297968 fffff800`031d4cbc fffff800`03011000 fffff880`0305b738 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff880`0305a850 fffff800`030bb335 : fffff800`031d80fc fffff880`0305a8c8 fffff880`0305b738 fffff800`03011000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`0305a880 fffff800`030cc3b1 : fffff880`0305b738 fffff880`0305af90 fffff880`00000000 00000000`00000004 : nt!RtlDispatchException+0x415
    fffff880`0305af60 fffff800`03090382 : fffff880`0305b738 ffff5880`071d65d0 fffff880`0305b7e0 00000000`000009b4 : nt!KiDispatchException+0x135
    fffff880`0305b600 fffff800`0308ec8a : 00000000`00000000 fffff880`0305b9e0 fffff880`0305b820 00000000`00000000 : nt!KiExceptionDispatch+0xc2
    fffff880`0305b7e0 fffff800`03094c16 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`13212c35 : nt!KiGeneralProtectionFault+0x10a
    fffff880`0305b970 fffff880`130ac6e0 : 00000000`00000002 fffffa80`00000000 00000000`00000900 00000000`00000000 : nt!KeSetEvent+0x16
    fffff880`0305b9e0 00000000`00000002 : fffffa80`00000000 00000000`00000900 00000000`00000000 00000000`00000000 : nvlddmkm+0x816e0
    fffff880`0305b9e8 fffffa80`00000000 : 00000000`00000900 00000000`00000000 00000000`00000000 fffffa80`0f13c5e0 : 0x2
    fffff880`0305b9f0 00000000`00000900 : 00000000`00000000 00000000`00000000 fffffa80`0f13c5e0 00000000`00000002 : 0xfffffa80`00000000
    fffff880`0305b9f8 00000000`00000000 : 00000000`00000000 fffffa80`0f13c5e0 00000000`00000002 fffff880`13174eaa : 0x900
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+816e0
    fffff880`130ac6e0 ??              ???
    
    SYMBOL_STACK_INDEX:  8
    
    SYMBOL_NAME:  nvlddmkm+816e0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4dd73a68
    
    FAILURE_BUCKET_ID:  X64_0x1E_nvlddmkm+816e0
    
    BUCKET_ID:  X64_0x1E_nvlddmkm+816e0
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 26
    Windows 7 Home Premium 64bit
    Thread Starter
       #3

    Thank you for the quick reply. I have recently tried to reinstall that driver a couple times but I will give that a shot with Driver Sweeper and post back if I am still having problems.
      My Computer


  4. Posts : 26
    Windows 7 Home Premium 64bit
    Thread Starter
       #4

    Reinstalled the Nvidia drivers as well as I knew how and got another bsod. Will have to check RAM and the Nvidia card using the links you provided. If it is helpful, here is the latest BSoD error:

    Dump File : 071211-33399-01.dmp
    Crash Time : 7/12/2011 8:51:03 PM
    Bug Check String : NTFS_FILE_SYSTEM
    Bug Check Code : 0x00000024
    Parameter 1 : 00000000`001904fb
    Parameter 2 : fffff880`0b71db88
    Parameter 3 : fffff880`0b71d3e0
    Parameter 4 : fffff880`012b4550
    Caused By Driver : Ntfs.sys
    Caused By Address : Ntfs.sys+a9550
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+7fd00
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\071211-33399-01.dmp
    Processors Count : 6
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 292,776

    Let me know if this is helpful in giving any additional information. I believe I unistalled the driver fully using the cleaner before reinstalling.
      My Computer


  5. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #5

    GiveMeTaffy said:
    Reinstalled the Nvidia drivers as well as I knew how and got another bsod. Will have to check RAM and the Nvidia card using the links you provided. If it is helpful, here is the latest BSoD error:

    Dump File : 071211-33399-01.dmp
    Crash Time : 7/12/2011 8:51:03 PM
    Bug Check String : NTFS_FILE_SYSTEM
    Bug Check Code : 0x00000024
    Parameter 1 : 00000000`001904fb
    Parameter 2 : fffff880`0b71db88
    Parameter 3 : fffff880`0b71d3e0
    Parameter 4 : fffff880`012b4550
    Caused By Driver : Ntfs.sys
    Caused By Address : Ntfs.sys+a9550
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+7fd00
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\071211-33399-01.dmp
    Processors Count : 6
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 292,776

    Let me know if this is helpful in giving any additional information. I believe I unistalled the driver fully using the cleaner before reinstalling.
    Post back the the test results :)
      My Computer


  6. Posts : 26
    Windows 7 Home Premium 64bit
    Thread Starter
       #6

    Just ran the video card test with OCCT with no errors on either the MemTest (7 passes) or the OCCT stress test (ran for 1 hr, windowed, 1280x1024).

    Will run the RAM test tonight since it takes several hours supposedly.

    Here is the most recent BSoD error as well. I hope the RAM test shows some results because I am getting frustrated with these frequent blue screens (this last one happened last night when I left my computer on playing music on iTunes and I woke up to the blue screen this morning).

    Thanks for the quick replies along the way. Will reply back with RAM test tomorrow morning.

    Dump File : 071511-31621-01.dmp
    Crash Time : 7/15/2011 10:21:56 AM
    Bug Check String : BAD_POOL_HEADER
    Bug Check Code : 0x00000019
    Parameter 1 : 00000000`00000003
    Parameter 2 : fffff880`029c87e0
    Parameter 3 : fffff880`029c87e0
    Parameter 4 : ffffd880`029c87e0
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+7fd00
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.17592 (win7sp1_gdr.110408-1631)
    Processor : x64
    Crash Address : ntoskrnl.exe+7fd00
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\071511-31621-01.dmp
    Processors Count : 6
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 292,784
      My Computer


  7. Posts : 26
    Windows 7 Home Premium 64bit
    Thread Starter
       #7

    OK I am now having trouble running the Memtest using the USB method. I have installed the program on the USB drive with reformatting and the other default settings. I have then restarted my computer several times normally, and also by going to the boot menu (F12 while starting) and selecting USB FDD and USB HDD as the first drive to boot. Any clarification on how to get this test to begin would be appreciated.
      My Computer


  8. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #8

    GiveMeTaffy said:
    OK I am now having trouble running the Memtest using the USB method. I have installed the program on the USB drive with reformatting and the other default settings. I have then restarted my computer several times normally, and also by going to the boot menu (F12 while starting) and selecting USB FDD and USB HDD as the first drive to boot. Any clarification on how to get this test to begin would be appreciated.
    You can try with a rewritable CD
      My Computer


  9. Posts : 26
    Windows 7 Home Premium 64bit
    Thread Starter
       #9

    OK I got it going and on pass 6 it got >1000 errors. When I woke up it was on pass 10 supposedly so I went ahead and stopped it. I can't find any data saved from the test so I am assuming the error report ITSELF is not needed, just the fact that there were errors.

    According to that guide, I will now need to run the tests for the RAM sticks individually to see which of my two is bad, so I will work on that.

    This could be causing my frequent BSoD then? I thought it appeared to be a video card driver problem originally?
      My Computer


  10. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #10

    GiveMeTaffy said:
    OK I got it going and on pass 6 it got >1000 errors. When I woke up it was on pass 10 supposedly so I went ahead and stopped it. I can't find any data saved from the test so I am assuming the error report ITSELF is not needed, just the fact that there were errors.

    According to that guide, I will now need to run the tests for the RAM sticks individually to see which of my two is bad, so I will work on that.

    This could be causing my frequent BSoD then? I thought it appeared to be a video card driver problem originally?
    Yes it is the RAM the culprit, the TDR video BSOD was triggered by a fault in memory. :)
      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 04:55.
Find Us