One BSOD after the next during bootup..

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by ijustdontgiveaf, Nov 12, 2010.

  1. ijustdontgiveaf

    ijustdontgiveaf New Member

    Joined:
    Nov 12, 2010
    Messages:
    10
    Likes Received:
    0
    [​IMG]

    Hello Everybody,

    I have a problem with my 64-bit windows 7 installation on a pretty new system (not even a month old).
    Windows update says i'm at the current state (except for language packs, but that's ok).

    The hardware consists of an Intel i5 760 processor on an Asus P7P55D-E motherboard. I am using 4GB of Ram (OCZ Platinum) and an MSI N460GTX Hawk video card. As a HD for the operating system i am using a crucial red 300 SSD disk that's connected to one of the SATA-600 ports on the mainboard. There is also a WD SATA-600 disk-drive connected to the other SATA-600 port for storage.
    As a network card i use a Linksys WUSB600N usb-stick to connect to my wireless homenetwork. The system is not overclocked (the mainboard has an auto-overclocking feature in the BIOS, but that I turned that off when the first blue-screen appeared)

    The first few days everything worked fine, but the last couple of days blue-screens started to appear whenever i tried to boot the system.
    Now it's even that far, that i can't boot the system regularly without facing at least three or four blue screens and trying again. If i manage to boot I can do pretty much everything except for opening up MS Outlook, as then system generates a blue-screen as well.
    I have checked the drivers site of my motherboard, the video card and the linksys-stick and all the drivers seem to be the newest ones.
    I have as well uninstalled "Teamviewer", as i could see this program causing issues in some of the minidumps that were created, but the issue still exists afterwards.
    Sometimes i also get a bluescreen when trying to load into safe mode, or sometimes also the computer just freezes during bootup.

    I did run a memory test for a couple of hours, but that didn't show anything, however since that was just a few passes I have just started it again and will leave it up for a few hours.

    Here you can find a "few" of the Minidumps that happened this week:

    https://cid-4bba342a4d6ef0cb.skydrive.live.com/redir.aspx?resid=4BBA342A4D6EF0CB!116&authkey=JDzRRkVnt34%24

    any help is greatly appreciated


    edit: attached minidump.zip so you don't need to go to the download link
     

    Attached Files:

    #1 ijustdontgiveaf, Nov 12, 2010
    Last edited: Nov 12, 2010
  2. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    #2 TorrentG, Nov 12, 2010
    Last edited: Nov 12, 2010
  3. ijustdontgiveaf

    ijustdontgiveaf New Member

    Joined:
    Nov 12, 2010
    Messages:
    10
    Likes Received:
    0
    Hi,

    Thanks for the quick response.

    In regards to the RAM i have done a search with my OCZ model and motherboard and found a couple of threads in the OCZ forum, where the vendor asked the users to manually set them to 7-7-7-20, ref cycle to 88 (auto-value was 59), dram voltage to 1.65V (auto was 1.5V) and the frequency fixed to 1333MHz, so i have done that today..
    afterwards it got a bit better, but i still got a few bsod when trying to boot..
    the latest can be found attached

    here are as well the screenshots from cpu-z

    i will now unconfigure ESET in safe mode and will install MSE instead


    edit: i downloaded the installer, then tried uninstalling ESET the regular way using its uninstaller, which gave me another BSOD, so i uninstalled it in safe mode.. bootup showed NO bluescreen :)D) and now MSE has been downloaded, installed and is checking as i write ;)

    thanks so much for your help and i hope that this was all..
     

    Attached Files:

    #3 ijustdontgiveaf, Nov 12, 2010
    Last edited: Nov 12, 2010
  4. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Yes, good move (notice what I've highlighted in red):

    Code:
    file:///I:/SKIDROW/FalloutNVLauncher.exe
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [E:\Temp\Rar$DI02.020\111210-22698-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02e49000 PsLoadedModuleList = 0xfffff800`03086e50
    Debug session time: Fri Nov 12 13:31:57.783 2010 (UTC - 5:00)
    System Uptime: 0 days 0:04:35.876
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C4, {e3, fffffa8003733b51, 4fdf3b4, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt!VerifierBugCheckIfAppropriate+3c )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught.  This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 00000000000000e3, Kernel Zw API called with user-mode address as parameter.
    Arg2: fffffa8003733b51, Address inside the driver making the incorrect API call.
    Arg3: 0000000004fdf3b4, User-mode address used as API parameter.
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc4_e3
    
    FAULTING_IP: 
    +644c2faf0176de70
    fffffa80`03733b51 3d05000080      cmp     eax,80000005h
    
    FOLLOWUP_IP: 
    nt!VerifierBugCheckIfAppropriate+3c
    fffff800`033433dc cc              int     3
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    [COLOR=red]PROCESS_NAME:  ekrn.exe[/COLOR]
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff800033433dc to fffff80002eb9740
    
    STACK_TEXT:  
    fffff880`08124558 fffff800`033433dc : 00000000`000000c4 00000000`000000e3 fffffa80`03733b51 00000000`04fdf3b4 : nt!KeBugCheckEx
    fffff880`08124560 fffff800`03343ec5 : fffffa80`020ebc80 00000000`00000032 00000000`00000080 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
    fffff880`081245a0 fffff800`0334539e : 00000000`00000080 00000000`00000032 00000000`00000000 fffff800`0334539e : nt!ViZwCheckAddress+0x35
    fffff880`081245e0 fffff800`033485c8 : fffffa80`03733b51 00000000`00000000 fffffa80`03733a1b fffff800`02eb4f30 : nt!ViZwCheckUnicodeString+0x2e
    fffff880`08124620 fffffa80`03733b51 : 00000000`04fdf3b4 fffff980`1b0feda0 00000000`04fdf3c4 00000000`00000018 : nt!VfZwQueryDirectoryFile+0x88
    fffff880`081246b0 00000000`04fdf3b4 : fffff980`1b0feda0 00000000`04fdf3c4 00000000`00000018 fffff880`08124778 : 0xfffffa80`03733b51
    fffff880`081246b8 fffff980`1b0feda0 : 00000000`04fdf3c4 00000000`00000018 fffff880`08124778 fffff980`1b0feda0 : 0x4fdf3b4
    fffff880`081246c0 00000000`04fdf3c4 : 00000000`00000018 fffff880`08124778 fffff980`1b0feda0 fffffa80`00000260 : 0xfffff980`1b0feda0
    fffff880`081246c8 00000000`00000018 : fffff880`08124778 fffff980`1b0feda0 fffffa80`00000260 fffff800`00000003 : 0x4fdf3c4
    fffff880`081246d0 fffff880`08124778 : fffff980`1b0feda0 fffffa80`00000260 fffff800`00000003 fffff880`0811f001 : 0x18
    fffff880`081246d8 fffff980`1b0feda0 : fffffa80`00000260 fffff800`00000003 fffff880`0811f001 fffff880`08124728 : 0xfffff880`08124778
    fffff880`081246e0 fffffa80`00000260 : fffff800`00000003 fffff880`0811f001 fffff880`08124728 00000000`00000001 : 0xfffff980`1b0feda0
    fffff880`081246e8 fffff800`00000003 : fffff880`0811f001 fffff880`08124728 00000000`00000001 00000000`000101d0 : 0xfffffa80`00000260
    fffff880`081246f0 fffff880`0811f001 : fffff880`08124728 00000000`00000001 00000000`000101d0 fffff980`1b210fc0 : 0xfffff800`00000003
    fffff880`081246f8 fffff880`08124728 : 00000000`00000001 00000000`000101d0 fffff980`1b210fc0 00000000`00000000 : 0xfffff880`0811f001
    fffff880`08124700 00000000`00000001 : 00000000`000101d0 fffff980`1b210fc0 00000000`00000000 ffffffff`80000af0 : 0xfffff880`08124728
    fffff880`08124708 00000000`000101d0 : fffff980`1b210fc0 00000000`00000000 ffffffff`80000af0 00000000`00100010 : 0x1
    fffff880`08124710 fffff980`1b210fc0 : 00000000`00000000 ffffffff`80000af0 00000000`00100010 00000000`04fdf3b4 : 0x101d0
    fffff880`08124718 00000000`00000000 : ffffffff`80000af0 00000000`00100010 00000000`04fdf3b4 00000000`00000260 : 0xfffff980`1b210fc0
    
    
    STACK_COMMAND:  kb
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!VerifierBugCheckIfAppropriate+3c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    
    FAILURE_BUCKET_ID:  X64_0xc4_e3_VRF_nt!VerifierBugCheckIfAppropriate+3c
    
    BUCKET_ID:  X64_0xc4_e3_VRF_nt!VerifierBugCheckIfAppropriate+3c
    
    Followup: MachineOwner
    ---------
     
  5. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    [langtitle=gl]Re: One BSOD after the next during bootup..[/langtitle]

    Set the tRAS to 16 in the motherboard bios too, instead of 20.

    And be sure to update your video card driver:

    nvlddmkm nvlddmkm.sys Sat Jul 31 09:43:08 2010

    NVIDIA
     
  6. ijustdontgiveaf

    ijustdontgiveaf New Member

    Joined:
    Nov 12, 2010
    Messages:
    10
    Likes Received:
    0
    Re: [langtitle=gl]Re: One BSOD after the next during bootup..[/langtitle]

    i checked the MSI site for the latest drivers and those were the ones on my system (259.22), but i didn't think of checking at NVIDIA directly.. they already have the 260.99 out, so that's currently installing..

    i will also set the tRAS to 16 and test..

    thanks again, your help is greatly appreciated
     
  7. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Re: [langtitle=gl]Re: One BSOD after the next during bootup..[/langtitle]

    Sure thing, you're welcome.

    Please keep us updated on how it's going.

    Once the crashes are completely stopped, be sure to disable the Driver Verifier.
     
  8. ijustdontgiveaf

    ijustdontgiveaf New Member

    Joined:
    Nov 12, 2010
    Messages:
    10
    Likes Received:
    0
    Re: [langtitle=gl]Re: One BSOD after the next during bootup..[/langtitle]

    so, i changed the tRAS and booted up normally..

    while installing 260.99 however i got a bluescreen (no dump), so i then installed the drivers in safe mode..

    while booting i got one bluescreen, but the second attempt it booted up immediately.. 1 BSOD over 7 or 8 is a drastic improvement ;)

    fault seemed to be the nvidia driver?

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\Minidump\111310-15709-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02e65000 PsLoadedModuleList = 0xfffff800`030a2e50
    Debug session time: Sat Nov 13 00:00:19.933 2010 (UTC + 1:00)
    System Uptime: 0 days 0:13:21.400
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............................
    Loading User Symbols
    Loading unloaded module list
    ........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff80002ecc634, fffff880031bc8b8, fffff880031bc120}
    
    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+91f54 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    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.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80002ecc634, The address that the exception occurred at
    Arg3: fffff880031bc8b8, Exception Record Address
    Arg4: fffff880031bc120, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    OVERLAPPED_MODULE: Address regions for 'nvlddmkm' and 'nvlddmkm.sys' overlap
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    nt!memmove+204
    fffff800`02ecc634 488b040a        mov     rax,qword ptr [rdx+rcx]
    
    EXCEPTION_RECORD:  fffff880031bc8b8 -- (.exr 0xfffff880031bc8b8)
    ExceptionAddress: fffff80002ecc634 (nt!memmove+0x0000000000000204)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000105d58018
    Attempt to read from address 0000000105d58018
    
    CONTEXT:  fffff880031bc120 -- (.cxr 0xfffff880031bc120)
    rax=fffff8a00108c590 rbx=0000000000000008 rcx=fffff8a00108c590
    rdx=0000076104ccba88 rsi=fffff8a00108c590 rdi=0000000000000008
    rip=fffff80002ecc634 rsp=fffff880031bcaf8 rbp=fffff880031bcec0
     r8=0000000000000008  r9=0000000000000001 r10=fffff88002f65660
    r11=fffff8a00108c590 r12=000000000000000a r13=fffff880031bcc38
    r14=0000000105d58018 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
    nt!memmove+0x204:
    fffff800`02ecc634 488b040a        mov     rax,qword ptr [rdx+rcx] ds:002b:00000001`05d58018=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000105d58018
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310d0e0
     0000000105d58018 
    
    FOLLOWUP_IP: 
    nvlddmkm+91f54
    fffff880`056a2f54 ??              ???
    
    BUGCHECK_STR:  0x7E
    
    LAST_CONTROL_TRANSFER:  from fffff800031ce552 to fffff80002ecc634
    
    STACK_TEXT:  
    fffff880`031bcaf8 fffff800`031ce552 : fffffa80`00000000 00000000`00000008 00000000`00000000 00000000`000007ff : nt!memmove+0x204
    fffff880`031bcb00 fffff800`031ce40b : fffffa80`047b0280 fffff880`031bcf70 00000000`00000001 fffff880`031bcf00 : nt!ObpCaptureObjectName+0x102
    fffff880`031bcb80 fffff800`031d1555 : fffffa80`03684bc0 fffffa80`03739200 00000000`0000006c 00000000`00000000 : nt!ObpCaptureObjectCreateInformation+0x279
    fffff880`031bcc00 fffff800`0316c262 : fffffa80`03713680 fffff880`031bcd80 fffff880`031bcf00 00000000`00000000 : nt!ObCreateObject+0x75
    fffff880`031bcc70 fffff800`02ed4993 : fffffa80`03713680 fffffa80`04bb34a0 00000000`00000000 00000000`00000001 : nt!NtCreateSymbolicLinkObject+0xbe
    fffff880`031bcd00 fffff800`02ed0f30 : fffff800`03248df6 00000000`000090de fffffa80`04bb34a0 fffff980`0140efa0 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`031bce98 fffff800`03248df6 : 00000000`000090de fffffa80`04bb34a0 fffff980`0140efa0 fffffa80`036fb000 : nt!KiServiceLinkage
    fffff880`031bcea0 fffff880`056a2f54 : 00000000`00000000 fffffa80`036fb000 fffffa80`04bb34a0 00000000`00000018 : nt!IoCreateSymbolicLink+0x46
    fffff880`031bcf00 00000000`00000000 : fffffa80`036fb000 fffffa80`04bb34a0 00000000`00000018 00000000`00000100 : nvlddmkm+0x91f54
    
    
    SYMBOL_STACK_INDEX:  8
    
    SYMBOL_NAME:  nvlddmkm+91f54
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4cb9dd0e
    
    STACK_COMMAND:  .cxr 0xfffff880031bc120 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_VRF_nvlddmkm+91f54
    
    BUCKET_ID:  X64_0x7E_VRF_nvlddmkm+91f54
    
    Followup: MachineOwner
    ---------
    
    


    i have driver verifier still enabled?? :confused:
    i thought i deleted the existing settings a few days ago, but i'll try using verifier /reset
     
  9. TorrentG

    TorrentG Banned

    Joined:
    May 31, 2010
    Messages:
    7,814
    Likes Received:
    372
    Re: [langtitle=gl]Re: One BSOD after the next during bootup..[/langtitle]

    What you'll want to do is boot to safe mode + networking.

    Download and run Driver Sweeper from guru3d.com to remove all the NVIDIA video content within the program. Boot to normal mode and then install the driver again from my link.

    Post the actual crash dump files if still needed after. There are commands I run on it to see much more than the normal !analyze -v output.
     

Share This Page

Loading...