random BSOD clean win7 64bit install, need your help guys


  1. Posts : 4
    Windows 7 Ultimate x64
       #1

    random BSOD clean win7 64bit install, need your help guys


    Tried a lot of thing. several clean win7 install still my laptop has random crashes. would be very thankful for any suggestions.
      My Computer


  2. Posts : 1,735
    Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
       #2

    Please Enable Driver verifier:

    Driver Verifier - Enable and Disable

    This should cause your computer to crash, when it does please post back with your new crash dumps. I have a feeling that this might be cause by your Video card driver, but I want to be sure first.

    WARNING!: If you can not boot normally into windows after enabling driver verifier Please boot into Safe Mode and then disable Driver Verifier.
      My Computer


  3. Posts : 4
    Windows 7 Ultimate x64
    Thread Starter
       #3

    enabled driver verifier


    nothing so far. playing assassins creed 3 to load video card. all temps look good. no overheating.
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    Hello arislan777. You may disable driver verifier for the time being.

    The version of the display driver you are using is problematic.
    Code:
    start             end                 module name
    fffff880`05866000 fffff880`06304000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Sat Dec 29 12:17:52 2012 (50DE9218)
        CheckSum:         00A7F96C
        ImageSize:        00A9E000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    And it is contributing to the crashes.
    Code:
    fffff880`0865a0b0  fffff880`0591aa8bUnable 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
     nvlddmkm+0xb4a8b
    Roll it back to a known stable version.


    You have a very old version of Rapid Storage installed.
    Code:
    start             end                 module name
    fffff880`01017000 fffff880`0116b000   iaStor     (deferred)             
        Image path: \SystemRoot\system32\DRIVERS\iaStor.sys
        Image name: iaStor.sys
        Timestamp:        Tue Sep 14 06:53:32 2010 (4C8ECE94)
        CheckSum:         00073894
        ImageSize:        00154000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Download and install this version only. (If it says it is not for windows 7, dont worry, and proceed with the installation).

    Dont let MagicDisc to start with windows. It is too much problematic. Use it only when it is needed. Free up the startup.

    1. Click on the Start button
    2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
    3. Select the “Startup” tab.
    4. Deselect all items other than the antivirus.
    5. Apply > OK
    6. Accept the restart.

    Uninstall AVG using AVG Remover. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
    Download, install and update those, and then run full system scans with both of them, one by one.

    Report back with the results.
      My Computer


  5. Posts : 4
    Windows 7 Ultimate x64
    Thread Starter
       #5

    new dump after turning on verifier


    will try rolling video drivers back
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    Verifier found nothing.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff960000ad7c8, fffff8800afbc7e0, 0}
    
    Probably caused by : win32k.sys ( win32k!RGNOBJ::bSwap+3c )
    
    Followup: MachineOwner
    ---------
    
    6: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff960000ad7c8, Address of the instruction which caused the bugcheck
    Arg3: fffff8800afbc7e0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    win32k!RGNOBJ::bSwap+3c
    fffff960`000ad7c8 4c8b00          mov     r8,qword ptr [rax]
    
    CONTEXT:  fffff8800afbc7e0 -- (.cxr 0xfffff8800afbc7e0)
    rax=0000000000000000 rbx=fffff8800afbd230 rcx=fffff8800afbd1e0
    rdx=fffff8800afbd230 rsi=0000000000000000 rdi=fffff900c0104b10
    rip=fffff960000ad7c8 rsp=fffff8800afbd1c0 rbp=0000000000000001
     r8=0000000000000000  r9=fffff900c0104b10 r10=0000000a000001e5
    r11=fffff8800afbd208 r12=fffff900c01e9b04 r13=fffff900c25326d0
    r14=0000000000000004 r15=fffff900c0822870
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    win32k!RGNOBJ::bSwap+0x3c:
    fffff960`000ad7c8 4c8b00          mov     r8,qword ptr [rax] ds:002b:00000000`00000000=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  HWMonitor.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff960000ad7c8
    
    STACK_TEXT:  
    fffff880`0afbd1c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!RGNOBJ::bSwap+0x3c
    
    
    FOLLOWUP_IP: 
    win32k!RGNOBJ::bSwap+3c
    fffff960`000ad7c8 4c8b00          mov     r8,qword ptr [rax]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  win32k!RGNOBJ::bSwap+3c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: win32k
    
    IMAGE_NAME:  win32k.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  50aeecc6
    
    STACK_COMMAND:  .cxr 0xfffff8800afbc7e0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_VRF_win32k!RGNOBJ::bSwap+3c
    
    BUCKET_ID:  X64_0x3B_VRF_win32k!RGNOBJ::bSwap+3c
    
    Followup: MachineOwner
    ---------
    So, I think you should follow the previous post.
      My Computer


  7. Posts : 4
    Windows 7 Ultimate x64
    Thread Starter
       #7

    thanks for everything


    realized that engineering sample processor was causing all the trouble, installed the old one and everything is ok now.
      My Computer


 

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