BSOD tried everything...PLEASE HELP

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Olysian, Aug 31, 2012.

  1. Olysian

    Olysian New Member

    Joined:
    Aug 31, 2012
    Messages:
    10
    Likes Received:
    0
    Hello, Window 7forums

    I have recently receive many different random BSODs and HARD FREEZES.:( I have upgraded all my drivers, check for any malware and viruses, and did Memtestx86 for about 8 passes no errors were detected. I have contacted my manufacturer to see whether or not this could be a hardware issue. After many tests and scans no issues could be found.

    I would regularly get blue screens at first boot. So my initial thought was to reboot after the first boot. This actually worked... for only about a week. Before entering into windows, I would get a BSOD. I installed WinDbg to find out what is the cause of these random BSOD. Most of my BSOD are caused by ntkrnlmp.exe. I'm not sure what that means.

    I have attach my minidump files, for further analysis.
     

    Attached Files:

  2. Olysian

    Olysian New Member

    Joined:
    Aug 31, 2012
    Messages:
    10
    Likes Received:
    0
    Microsoft (R) Windows Debugger Version 6.2.9200.16384 X86
    Copyright (c) Microsoft Corporation. All rights reserved.




    Loading Dump File [C:\Windows\Minidump\082912-34320-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available


    Symbol search path is: http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Machine Name:
    Kernel base = 0xfffff800`02e5e000 PsLoadedModuleList = 0xfffff800`030a2670
    Debug session time: Wed Aug 29 20:32:44.825 2012 (UTC - 5:00)
    System Uptime: 0 days 4:47:30.776
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************


    Use !analyze -v to get detailed debugging information.


    BugCheck 3B, {c0000005, fffff80002f50964, fffff88007c1ff90, 0}


    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3f962 )


    Followup: MachineOwner
    ---------


    0: 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: fffff80002f50964, Address of the instruction which caused the bugcheck
    Arg3: fffff88007c1ff90, 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:
    nt! ?? ::FNODOBFM::`string'+3f962
    fffff800`02f50964 488b00 mov rax,qword ptr [rax]


    CONTEXT: fffff88007c1ff90 -- (.cxr 0xfffff88007c1ff90)
    rax=f7fffa8009044970 rbx=fffffa80087ced90 rcx=0000000000000001
    rdx=f7fffa8009044970 rsi=0000000000000000 rdi=fffffa80090448d0
    rip=fffff80002f50964 rsp=fffff88007c20970 rbp=fffffa80090448d0
    r8=0000000000000002 r9=fffff88007c20ac0 r10=fffff80002e5e000
    r11=fffff88007c209c8 r12=fffffa8009044968 r13=fffffa8008928e40
    r14=fffffa8009044970 r15=fffff8000304fe80
    iopl=0 nv up ei ng nz na po cy
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287
    nt! ?? ::FNODOBFM::`string'+0x3f962:
    fffff800`02f50964 488b00 mov rax,qword ptr [rax] ds:002b:f7fffa80`09044970=????????????????
    Resetting default scope


    CUSTOMER_CRASH_COUNT: 1


    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT


    BUGCHECK_STR: 0x3B


    PROCESS_NAME: chrome.exe


    CURRENT_IRQL: 2


    LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002f50964


    STACK_TEXT:
    fffff880`07c20970 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x3f962




    FOLLOWUP_IP:
    nt! ?? ::FNODOBFM::`string'+3f962
    fffff800`02f50964 488b00 mov rax,qword ptr [rax]


    SYMBOL_STACK_INDEX: 0


    SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+3f962


    FOLLOWUP_NAME: MachineOwner


    MODULE_NAME: nt


    IMAGE_NAME: ntkrnlmp.exe


    DEBUG_FLR_IMAGE_TIMESTAMP: 4fa390f3


    STACK_COMMAND: .cxr 0xfffff88007c1ff90 ; kb


    FAILURE_BUCKET_ID: X64_0x3B_nt!_??_::FNODOBFM::_string_+3f962


    BUCKET_ID: X64_0x3B_nt!_??_::FNODOBFM::_string_+3f962


    Followup: MachineOwner
    ---------
    This is my latest minidump file from a BSOD.
     
  3. Olysian

    Olysian New Member

    Joined:
    Aug 31, 2012
    Messages:
    10
    Likes Received:
    0
    Receive 2 more BSODs this morning. 15 minutes apart ( a new record). Also, I've notice after my minidumps are save, my cpu fans are running really loud and fast. By any chance that there is dust clog in my heat sink. Because 2 weeks ago I brought some compressed air and clean my fans and dusty areas around my cpu. No blue screens for about a week. Maybe there is still more dust and this is the probable cause of my random BSODs/Hard FREEZES. I have update my NVIDIA graphic card to the latest.
     

    Attached Files:

  4. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    what is the system build and model number from which manufacturer please ?

    what is your system spec, such as CPU , PSU , Ram etc ?
     
  5. Olysian

    Olysian New Member

    Joined:
    Aug 31, 2012
    Messages:
    10
    Likes Received:
    0
    I attached a folder with all the info on there. Had 8 BSODs today, some weren't able to be transferred in minidump. This problem is really getting serious to the point I'm afraid of using my PC.
     

    Attached Files:

  6. ELiTEFX

    ELiTEFX New Member

    Joined:
    Aug 31, 2012
    Messages:
    86
    Likes Received:
    4
    have you done any work internally on the PC lately? Improperly installed hardware will cause the BSODs. If you have..open up your machine and make sure all hardware is seated in their slots properly, check cables, everything etc. not saying it is a sure fix but this will eliminate the possibility......
     
  7. Olysian

    Olysian New Member

    Joined:
    Aug 31, 2012
    Messages:
    10
    Likes Received:
    0
    Yeah I had a external network adapter installed on my pc, but I took that out few months ago. It was also causing my pc to crash. I think this BSOD is entirely diffferent and cause by another driver/hardware in the system.
     
  8. ELiTEFX

    ELiTEFX New Member

    Joined:
    Aug 31, 2012
    Messages:
    86
    Likes Received:
    4
    Agree 100%. The video driver is the most likely culprit. Also, (from my personal experience) remove your video card(s) and reinstall them. Sometimes they'll appear seated properly but are, in fact, not......best of luck

    EDIT: Just had another thought. 8 BSODs is a lot. I'd check all the hardware in your case (loose parts and gravity) THEN boot into the Bios. Load "Optimized Defaults" Save. Exit. Run it like that for a couple hours and see what happens......
     
    #8 ELiTEFX, Sep 1, 2012
    Last edited: Sep 1, 2012
  9. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    I am guessing you have added your own ram at some point as you have a strange number achieving 5gb using :


    • #dimm1 : 1024 MBytes
    • #dimm2 : 1024 MBytes
    • #dimm3 : 2048 MBytes
    • #dimm4 : 1024 MBytes

    The serial numbers are close, on dimms 1, 2 and 4 but I'm guessing you added the 2gb stick in dimm 3 yourself ?

    The 1gb sticks where made Week 52/Year 08 whereas the 2gb stick was made Week 03/Year 09 which means the metals value is very likely to be very different so affecting the component quality which will consequently make the RAM behave differently under load and produce parity errors only measurable in use by an O/S

    The first thing I would try is remove Dimms 2, 3 and 4 and try and get your system to crash using just the one stick,

    If that works ok then add the other 1gb sticks back in, retest and stress, then finally try the 2gb stick which I am guessing Will reproduce your crash +o(

    Let us know how it goes :cool:
     

Share This Page

Loading...