Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

PC freezing/BSOD issues

Options
  • 22-06-2015 5:18pm
    #1
    Registered Users Posts: 3,387 ✭✭✭


    My PC has frozen twice in the last week, completely hangs and has to be reset using the button. I uploaded both minidump files to an online minidump analyser (http://www.osronline.com/).


    Which comes back with:


    rash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
    Online Crash Dump Analysis Service
    See http://www.osronline.com for more information
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9200.16912.amd64fre.win8_gdr.140502-1507
    Machine Name:
    Kernel base = 0xfffff801`17e81000 PsLoadedModuleList = 0xfffff801`1814daa0
    Debug session time: Sun Jun 14 07:25:04.324 2015 (UTC - 4:00)
    System Uptime: 0 days 0:57:21.913
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,
    it must be protected by a Probe. Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffffb240adf6300, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff88004dd6940, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000002, (reserved)

    Debugging Details:



    Could not read faulting driver name
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff801181d9168
    GetUlongFromAddress: unable to read from fffff801181d91f8
    fffffb240adf6300 Nonpaged pool

    FAULTING_IP:
    nvlddmkm+ee940
    fffff880`04dd6940 428b8401a4230000 mov eax,dword ptr [rcx+r8+23A4h]

    MM_INTERNAL_CODE: 2

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: AV

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    TRAP_FRAME: fffff8800a935560 -- (.trap 0xfffff8800a935560)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000ffffffff rbx=0000000000000000 rcx=000000a3ffffff5c
    rdx=00000000ffffffff rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88004dd6940 rsp=fffff8800a9356f0 rbp=fffff8800a935760
    r8=fffffa800adf4000 r9=0000000000000008 r10=0000000000000000
    r11=fffffa800ad9f730 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz na po nc
    nvlddmkm+0xee940:
    fffff880`04dd6940 428b8401a4230000 mov eax,dword ptr [rcx+r8+23A4h] ds:fffffb24`0adf6300=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80117f9c1bc to fffff80117edb540

    STACK_TEXT:
    fffff880`0a935378 fffff801`17f9c1bc : 00000000`00000050 fffffb24`0adf6300 00000000`00000000 fffff880`0a935560 : nt!KeBugCheckEx
    fffff880`0a935380 fffff801`17f15c2b : 00000000`00000000 fffffb24`0adf6300 fffffa80`0c595900 00100110`00000000 : nt! ?? ::FNODOBFM::`string'+0x338a2
    fffff880`0a935420 fffff801`17ed8fee : 00000000`00000000 00000000`00000000 00000000`00052700 fffff880`0a935560 : nt!MmAccessFault+0x55b
    fffff880`0a935560 fffff880`04dd6940 : 00000000`0004b8b0 fffffa80`0aef7000 fffffa80`0b814000 fffffa80`0fc2ebe0 : nt!KiPageFault+0x16e
    fffff880`0a9356f0 00000000`0004b8b0 : fffffa80`0aef7000 fffffa80`0b814000 fffffa80`0fc2ebe0 00000000`0004b8b0 : nvlddmkm+0xee940
    fffff880`0a9356f8 fffffa80`0aef7000 : fffffa80`0b814000 fffffa80`0fc2ebe0 00000000`0004b8b0 fffffa80`0aef7000 : 0x4b8b0
    fffff880`0a935700 fffffa80`0b814000 : fffffa80`0fc2ebe0 00000000`0004b8b0 fffffa80`0aef7000 fffffa80`0fc2ebe0 : 0xfffffa80`0aef7000
    fffff880`0a935708 fffffa80`0fc2ebe0 : 00000000`0004b8b0 fffffa80`0aef7000 fffffa80`0fc2ebe0 fffff880`04dd6dbc : 0xfffffa80`0b814000
    fffff880`0a935710 00000000`0004b8b0 : fffffa80`0aef7000 fffffa80`0fc2ebe0 fffff880`04dd6dbc 00000000`00000000 : 0xfffffa80`0fc2ebe0
    fffff880`0a935718 fffffa80`0aef7000 : fffffa80`0fc2ebe0 fffff880`04dd6dbc 00000000`00000000 fffff8a0`052bf85b : 0x4b8b0
    fffff880`0a935720 fffffa80`0fc2ebe0 : fffff880`04dd6dbc 00000000`00000000 fffff8a0`052bf85b 00000000`00000000 : 0xfffffa80`0aef7000
    fffff880`0a935728 fffff880`04dd6dbc : 00000000`00000000 fffff8a0`052bf85b 00000000`00000000 00000000`000452b6 : 0xfffffa80`0fc2ebe0
    fffff880`0a935730 00000000`00000000 : fffff8a0`052bf85b 00000000`00000000 00000000`000452b6 00000000`00000001 : nvlddmkm+0xeedbc


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nvlddmkm+ee940
    fffff880`04dd6940 428b8401a4230000 mov eax,dword ptr [rcx+r8+23A4h]

    SYMBOL_STACK_INDEX: 4

    SYMBOL_NAME: nvlddmkm+ee940

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nvlddmkm

    IMAGE_NAME: nvlddmkm.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 5566824f

    FAILURE_BUCK X64_AV_nvlddmkm+ee940
    ET_ID:
    BUCKET_ID: X64_AV_nvlddmkm+ee940

    Followup: MachineOwner



    I've been a bit lazy and was letting Asus' EZ updater look after BIOS updates etc. Thing is it was not updating anything, probably because it needed to be updated itself-oh the irony...

    I updated the BIOS there, and am currently downloading all the other drivers (chipset etc.), as well as running windows update.

    I ran the windows memory diagnostic there and it came up good-is there a better option like memtest86+ (it supports 64 bit despite the name) that would be worth trying?

    I ran intel burn test for a few passes to make sure the cooler (Corsair H8i) was doing its thing, and the temp hit 81 deg C on the extreme setting, but sits at about 29-31 deg C normally, 50’s when gaming.
    The PC is less than a year old, and has run perfectly until now-so hopefully its software/driver based.
    Can anyone shed some light on what else I can try?

    I also uploaded the minidumps if anyone that knows a bit about same could give a look I would really appreciate it.


Comments

  • Posts: 0 [Deleted User]


    Judging by your dump, you might need to check your video card. nvlddmkm.sys (the Nvidia display driver) was the culprit. Could be a bad driver, faulty video card or power issues.


  • Registered Users Posts: 3,387 ✭✭✭glynf


    Will do, thanks. Nvidia experience was acting up lately as well-now uninstalled.


  • Registered Users Posts: 3,387 ✭✭✭glynf


    Did it again, froze while playing GTA online. No minidump file created. No overclocks on the cards or CPU, all drivers, BIOS etc. latest versions. Whats the best memory test to try?


  • Registered Users Posts: 3,387 ✭✭✭glynf


    So I ran memtest overnight, 9 passes no errors. Also ran gpu 3D mark for 30 Mins with no issues, plan to try furmark for a few hours this evening. This should show if it's gpu related.


Advertisement