TechSpot

Windows BSOD during or after startup (.dmp log attached)

By Scytha87
Oct 9, 2014
Post New Reply
  1. Hi!

    Two weeks ago I bought a second-hand full configuration. After installed windows 7 (later I tried win 8.1 but the result was the same) a weird problem emerged. When turn on the PC (from totally power off state) the windows logo reveals and reboot the system with various BSODs (sometimes the system reaches the desktop - but max. 1 minute later did the same error). System repair is not working, but a few (2-3) attempts afterward the system normalizing and everything works fine. Curious that problem only concern when the PC stay at least 1 or 2 hours power off. Neither reset nor restart from windows cause this problem (or when power off and suddenly power on the machine). When the system startup occur correcctly everything work fine in the system no BSOD or anything else even when I heavily load the system (for example games, tests).
    I tested the RAM, CPU, VGA (use integrated instead of radeon), SSD but it seems everything is okay. I changed the SSD with HDD - same bad result. I did windows clean install, but before I started to install the drivers and programs the problem appears again. Maybe I rule out the softver-driver incompatibility?
    I'm totally clueless at this point so I waiting for your instruction.



    Configuration:

    Asrock Z68 pro3 (bios 2.10)

    i5-2500K

    2x4 GB Corsair Vengeance RAM

    120 gb Corsair Force 3 SSD

    Sapphire r9 270

    Creative Xi-fi music soundcard



    Thanks for help!



    ps. I attached a few of the bsod-s result: http://i59.tinypic.com/205xq12.jpg



    DMP FILE:





    Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Bitmap Dump File: Only kernel address space is available


    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred SRV*c:\Vistasymbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*c:\Vistasymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17031.amd64fre.winblue_gdr.140221-1952
    Machine Name:
    Kernel base = 0xfffff802`0608e000 PsLoadedModuleList = 0xfffff802`063582d0
    Debug session time: Thu Oct 9 16:40:36.904 2014 (UTC + 2:00)
    System Uptime: 0 days 17:28:03.604
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........
    Loading User Symbols

    Loading unloaded module list
    .....................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7E, {ffffffffc000001d, fffff800f38fdec9, ffffd000c6573f88, ffffd000c6573790}

    Probably caused by : memory_corruption

    Followup: memory_corruption
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
    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: ffffffffc000001d, The exception code that was not handled
    Arg2: fffff800f38fdec9, The address that the exception occurred at
    Arg3: ffffd000c6573f88, Exception Record Address
    Arg4: ffffd000c6573790, Context Record Address

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {KIV TEL} Szab lytalan utas t s Szab lytalan utas t skiad s t rt nt.

    FAULTING_IP:
    msrpc!LRPC_BASE_CCALL::SendReceive+119
    fffff800`f38fdec9 c4 ???

    EXCEPTION_RECORD: ffffd000c6573f88 -- (.exr 0xffffd000c6573f88)
    ExceptionAddress: fffff800f38fdec9 (msrpc!LRPC_BASE_CCALL::SendReceive+0x0000000000000119)
    ExceptionCode: c000001d (Illegal instruction)
    ExceptionFlags: 00000000
    NumberParameters: 0

    CONTEXT: ffffd000c6573790 -- (.cxr 0xffffd000c6573790;r)
    rax=0000000000000074 rbx=ffffc0003a842010 rcx=ffffc000395e24b8
    rdx=0000000000000000 rsi=ffffc0003a842080 rdi=ffffc0003ad63000
    rip=fffff800f38fdec9 rsp=ffffd000c65741c0 rbp=ffffd000c6574440
    r8=0000000000000000 r9=0000000000000020 r10=00000000a0000000
    r11=fffff800f390dcc0 r12=ffffe001187e20b8 r13=ffffe0011879ca60
    r14=0000000000000000 r15=ffffe0011879cab0
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
    msrpc!LRPC_BASE_CCALL::SendReceive+0x119:
    fffff800`f38fdec9 c4 ???
    Last set context:
    rax=0000000000000074 rbx=ffffc0003a842010 rcx=ffffc000395e24b8
    rdx=0000000000000000 rsi=ffffc0003a842080 rdi=ffffc0003ad63000
    rip=fffff800f38fdec9 rsp=ffffd000c65741c0 rbp=ffffd000c6574440
    r8=0000000000000000 r9=0000000000000020 r10=00000000a0000000
    r11=fffff800f390dcc0 r12=ffffe001187e20b8 r13=ffffe0011879ca60
    r14=0000000000000000 r15=ffffe0011879cab0
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
    msrpc!LRPC_BASE_CCALL::SendReceive+0x119:
    fffff800`f38fdec9 c4 ???
    Resetting default scope

    DEFAULT_BUCKET_ID: CODE_CORRUPTION

    BUGCHECK_STR: AV

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    ERROR_CODE: (NTSTATUS) 0xc000001d - {KIV TEL} Szab lytalan utas t s Szab lytalan utas t skiad s t rt nt.

    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

    LAST_CONTROL_TRANSFER: from fffff800f38fe3d9 to fffff800f38fdec9

    FAILED_INSTRUCTION_ADDRESS:
    msrpc!LRPC_BASE_CCALL::SendReceive+119
    fffff800`f38fdec9 c4 ???

    STACK_TEXT:
    ffffd000`c65741c0 fffff800`f38fe3d9 : ffffe001`1879cab0 00000000`00000001 ffffe001`1879ca60 ffffe001`187e20b8 : msrpc!LRPC_BASE_CCALL::SendReceive+0x119
    ffffd000`c6574230 fffff800`f38e51f1 : ffffd000`c6574a40 00000000`00000000 00000000`00000001 ffffd000`c6574888 : msrpc!NdrSendReceive+0x99
    ffffd000`c6574270 fffff800`f38e5360 : 00000000`00000000 fffff800`f42a4c10 fffff802`00000008 ffffd000`c65742a0 : msrpc!NdrpClientCall3+0xf1
    ffffd000`c65744b0 fffff800`f4268db2 : 00000000`00000000 00000010`00000004 00000000`00000000 ffffc000`395e23b0 : msrpc!NdrClientCall3+0x80
    ffffd000`c6574830 fffff800`f4268c0b : ffffe001`1879cab0 00000000`00000000 ffffe001`1879ca00 00000000`00000000 : NETIO!RpcNsiParameterChange+0x7a
    ffffd000`c65748d0 fffff800`f458238b : ffffd000`c65749e8 00000000`fffffffe ffffe001`194435c0 00000000`00000000 : NETIO!NsiParameterChange+0x15b
    ffffd000`c65749c0 fffff800`f4582294 : 00000000`00000000 00000000`00000000 ffffe001`1722fe50 ffffe001`194936e0 : tcpip!IppNotifyInterfaceChangeAtPassive+0xeb
    ffffd000`c6574a70 fffff800`f4252035 : ffffe001`194936e0 00000000`00000000 fffff802`06374180 ffffe001`18830900 : tcpip!InetNsiWorkQueueRoutine+0x15
    ffffd000`c6574aa0 fffff802`060e105f : ffffe001`18824fb0 00000000`00000000 ffffe001`176d4a10 ffffe001`176d4480 : NETIO!NetiopIoWorkItemRoutine+0x35
    ffffd000`c6574af0 fffff802`060e1adb : fffff802`065249ac fffff802`060e0f84 ffffd000`c6574bd0 ffffe001`18824fb0 : nt!IopProcessWorkItem+0xdb
    ffffd000`c6574b50 fffff802`0615d794 : ffffe001`172f7b00 ffffe001`188307c0 ffffe001`188307c0 ffffe001`1727b900 : nt!ExpWorkerThread+0x293
    ffffd000`c6574c00 fffff802`061e85c6 : ffffd000`c7640180 ffffe001`188307c0 ffffe001`19889880 ffffc000`3964b680 : nt!PspSystemThreadStartup+0x58
    ffffd000`c6574c60 00000000`00000000 : ffffd000`c6575000 ffffd000`c656f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


    CHKIMG_EXTENSION: !chkimg -lo 50 -db !msrpc
    6 errors : !msrpc (fffff800f38fdec1-fffff800f38fdef9)
    fffff800f38fdec0 00 *80 0f b7 83 24 01 00 00 *c4 89 77 30 66 83 c0 .....$.....w0f..
    ...
    fffff800f38fdee0 00 *82 ff ff 66 09 47 04 44 *8b 77 28 48 8b 03 48 ....f.G.D.w(H..H
    fffff800f38fdef0 8b *92 20 01 00 00 48 8d 05 *7d 62 00 00 48 3b d0 .. ...H..}b..H;.

    MODULE_NAME: memory_corruption

    IMAGE_NAME: memory_corruption

    FOLLOWUP_NAME: memory_corruption

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MEMORY_CORRUPTOR: STRIDE

    STACK_COMMAND: .cxr 0xffffd000c6573790 ; kb

    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE

    BUCKET_ID: MEMORY_CORRUPTION_STRIDE

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:memory_corruption_stride

    FAILURE_ID_HASH: {574dbc1b-92cb-fb09-cb7a-cacc1bb2c511}

    Followup: memory_corruption
    ---------

    0: kd> lmvm memory_corruption
    start end module name
     
  2. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    What antivirus program are you running?
     
  3. Scytha87

    Scytha87 TS Rookie Topic Starter

    Nothing at this time, because I did a windows clean install. I didn't install driver or software. Anyway I used to use Avira Free AV.
    Since the clean install the problem is exist. Strange that now the system is always reaches the desktop, but about 30-60 sec. later come the BSOD message. Last time: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED and "msrpc.sys" error...
     
  4. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    This is most likely a hardware error. Test the memory using Memtest86 version 5.01. Let it run for at least 7 passes. Any errors at all mean trouble:
    http://www.memtest.org/
     
  5. Scytha87

    Scytha87 TS Rookie Topic Starter

    Thx for advice you are right. One of the two RAM module (Kit - 2x4gb Corsair Vengeance) was the problem. The BSOD absolutely gone when I take out the wrong ram. But the memtest86 doesn't show problem (runs 10 hours - 12 pass)... I ran the longest test version of windows 8.1 integrated diagnostic tool - but the same - no error. It is possible, that the RAM cause serious symptomps, but the test programs don't find the error?
     

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...