Windows 8 and 8.1 Forums

BSOD - before and after replacing RAM

  1. #1

    Posts : 14
    Windows 8.1

    BSOD - before and after replacing RAM

    I started a thread a while ago and You Fellas diagnosed the problem was the faulty RAM. So I bought and replaced using 2 other slot of memory that wasnt used before (i have 4 slots). It took some time, but sadly it started crashing again. 4 dmps and routine stuff attached. It happens usually in games but it happens sometimes in desktop so its random for me. Honestly Im running out of ideas what component or anything else is corrupted. Im asking and patiently waiting for You, Proffesionals BSOD killers

    PS. Im sorry about starting a new thread, but previous was a while ago and i marked it solved (but i was wrong about problem) so i hope if U dont mind :P

      My System SpecsSystem Spec

  2. #2

    Posts : 660
    windows 8.1

    The memory dumps don't point to anything specific, but are (IMO) suggestive of a misbehaving driver (one writing bad info to memory spaces that it doesn't own).

    Please update this driver Rt630x64 fffff800`4091c000 fffff800`409b0000 Fri May 10 11:59:08 2013 (518cc4ec) 0009d8fe Rt630x64.sys.
    Driver Description: Realtek PCI/PCIe Adapters
    Driver Update Site: Realtek

    If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions: Driver Verifier Settings


    Due tothe age of the system, it's possible that it's not compatible with Windows 8.1- you may have to consider moving back to Windows 8 or even Win7 in order toget acceptable performance.
      My System SpecsSystem Spec

  3. #3

    Posts : 14
    Windows 8.1

    Ok so i know thats been some time but i managed to update Realtek, but the crashes go on... so I run Driver verifier,i done it before, so i just went with standard settings, restarted and maybe after 3 sec after logging into windows acc, driver verifier violation BSOD. I make it happen 2 times just to be sure, and Im uploading routine stuff again. I hope thats ok so far ;p

    P.s. If U dont mind, I'll keep in mind moving back with windows, but i rather leave it as the last resort ;p
      My System SpecsSystem Spec

  4. #4

    Posts : 660
    windows 8.1

    In the last 2 dumps, Driver Verifier blames NvStreamKms.sys

    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck C4, {2001b, fffff801680ecff0, 0, 0}
    *** WARNING: Unable to verify timestamp for NvStreamKms.sys
    *** ERROR: Module load completed but symbols could not be loaded for NvStreamKms.sys
    Probably caused by : NvStreamKms.sys ( NvStreamKms+2146 )
    Followup: MachineOwner
    0: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    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.
    Arg1: 000000000002001b, ID of the 'IrqlObPassive' rule that was violated.
    Arg2: fffff801680ecff0, A pointer to the string describing the violated rule condition.
    Arg3: 0000000000000000, Reserved (unused).
    Arg4: 0000000000000000, Reserved (unused).
    Debugging Details:
    DV_VIOLATED_CONDITION:  ObReferenceObjectByHandle should only be called at IRQL = PASSIVE_LEVEL.
    DV_MSDN_LINK: IrqlObPassive rule (wdm) (Windows Drivers)
    DV_RULE_INFO: 0x2001B
    BUGCHECK_STR:  0xc4_IrqlObPassive_XDV
    PROCESS_NAME:  nvstreamsvc.ex
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    LAST_CONTROL_TRANSFER:  from fffff801680e6258 to fffff801495dcfa0
    ffffd001`d866c758 fffff801`680e6258 : 00000000`000000c4 00000000`0002001b fffff801`680ecff0 00000000`00000000 : nt!KeBugCheckEx
    ffffd001`d866c760 fffff801`680d7fcf : 00000000`00110001 00000000`00110001 ffffe000`c2a520d8 ffffe000`c2a520d8 : VerifierExt!SLIC_abort+0x5c
    ffffd001`d866c7a0 fffff801`680d8000 : fffff801`49766d50 fffff801`4971dae5 00000000`00000200 fffff801`49af7872 : VerifierExt!SLIC_ObReferenceObjectByHandle_entry_IrqlObPassive+0x23
    ffffd001`d866c7d0 fffff801`49b108e9 : 00000000`00110000 ffffe000`bf4fb6a0 ffffcf82`14f62f01 fffff801`680da76d : VerifierExt!ObReferenceObjectByHandle_wrapper+0x30
    ffffd001`d866c810 fffff801`6aff7146 : 00000000`000004f4 ffffd001`d866c940 ffffcf82`14f62ff0 fffff801`49766980 : nt!VerifierObReferenceObjectByHandle+0x49
    ffffd001`d866c850 00000000`000004f4 : ffffd001`d866c940 ffffcf82`14f62ff0 fffff801`49766980 fffff801`6aff9060 : NvStreamKms+0x2146
    ffffd001`d866c858 ffffd001`d866c940 : ffffcf82`14f62ff0 fffff801`49766980 fffff801`6aff9060 00000000`00000000 : 0x4f4
    ffffd001`d866c860 ffffcf82`14f62ff0 : fffff801`49766980 fffff801`6aff9060 00000000`00000000 00000000`00000000 : 0xffffd001`d866c940
    ffffd001`d866c868 fffff801`49766980 : fffff801`6aff9060 00000000`00000000 00000000`00000000 fffff801`6aff6574 : 0xffffcf82`14f62ff0
    ffffd001`d866c870 fffff801`6aff9060 : 00000000`00000000 00000000`00000000 fffff801`6aff6574 ffffcf82`14ed4ea0 : nt!NonPagedPoolDescriptor+0x1c0
    ffffd001`d866c878 00000000`00000000 : 00000000`00000000 fffff801`6aff6574 ffffcf82`14ed4ea0 ffffd001`d866c940 : NvStreamKms+0x4060
    fffff801`6aff7146 ??              ???
    SYMBOL_NAME:  NvStreamKms+2146
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: NvStreamKms
    IMAGE_NAME:  NvStreamKms.sys
    FAILURE_BUCKET_ID:  0xc4_IrqlObPassive_XDV_VRF_NvStreamKms+2146
    BUCKET_ID:  0xc4_IrqlObPassive_XDV_VRF_NvStreamKms+2146
    FAILURE_ID_HASH_STRING:  km:0xc4_irqlobpassive_xdv_vrf_nvstreamkms+2146
    FAILURE_ID_HASH:  {eace86cc-8949-b87a-9cb9-66f67ee34f9a}
    Followup: MachineOwner
    From a previous post of mine (located here: BSOD at startup and lid closed DPC Watchdog ):
    ..... NvStreamKms.sys - an nVidia driver that belongs to the nVidia Streaming Kernel service.
    Check this post out for a possible fix:
    Or, you may want to uninstall the nVidia drivers and then install a fresh copy without the Streaming Kernel Service (I'm not familiar with nVidia drivers, so I don't even know if this is possible).
    Above info taken from Usasma

    Driver Description: nVidia Streaming Kernel service - may cause BSOD in Win8.1 systems (found in May 2014). Date/TimeStamp: Tue Apr 29 20:59:44 2014 (53604B00)
    Driver Update Site: From: BSOD at startup and lid closed DPC Watchdog )
    Possible fix:
    Or uninstall the nVidia drivers and then install a fresh copy without the Streaming Kernel Service (uncertain if this is possible)

    My suggestion would be (if above mentioned is not possible) to rollback the driver to a previous version.
      My System SpecsSystem Spec

  5. #5

    Posts : 14
    Windows 8.1

    OK, I was so happy when for some time it stopped, but my face got stoned when got hit by another BSOD and again and again. OKOK 5 crashes happened after resolving nvidia matter and those crashes highlighted once tcpip.sys and hal.dll alongside with always highlighted ntoskrnl.exe (Bluescreenview.exe). So I of course chcecked by DriverVerifier but it didnt crash PC even after logging in my user. If any of it matters I run full virus scan by dr.web cureit, it popped up 6 threats that was cured. But PC crashed day after
    I having this BSOD problem for long long time ( previously it was matter of Power suply box that wasnt have enough power and it was replaced later by OCZ stuff, later i wrote here earlier and mr.MasterChief diagnosed faulty RAM, and it was replaced, crashes goes on still. I keep my PC clean, fast running, im trying scan frequently, beeing careful, but the problem persists)( i stopped counting how many bsods happened honestly)
    Do U think its time for that last resort solution of going back to win7?
    Last edited by SoonEnough; 30 May 2014 at 16:01.
      My System SpecsSystem Spec

  6. #6

    Posts : 660
    windows 8.1

    The latest dumpfiles again do not point to a specific driver or problem, as far i can read/see.

    I must admit i begin running out of ideas for a solution.

    Some last wild/possible ideas i can think of are:

    The new memory you installed, did you check if it is compatible with your mainboard Asrock M3A770DE. In my analyse program the brand and model is not showed. Did you installed them in the adviced memoryslots?

    In one of the dumpfile in the procesname OLgame.exe is mentioned. This is the exe of a game Outlast i believe. You are using a genius mouse X-G500. Have you installed drivers for this mouse or are you using the generic windows drivers. The windows 8 drivers you can download from here Genius
      My System SpecsSystem Spec

  7. #7

    Posts : 14
    Windows 8.1

    About memory, when in previous thread Your Pro advised to change memory I bought the same Kingston DDR3 PC1600 HyperX CL9 but 8GB(2x4GB) instead of 4GB(2x2GB), and in asrock website it says that is supported. I mounted it on 2 other slots that wasnt used (4 slots in mainboard), when i changed memory i just go to bios and set it to default as adviced again by Your Pro.

    About mouse You are right, after refreshing windows I may just forgot about this and for some time i was using windows drivers, I just downloaded genius drivers and installed it.

    Ok this may look relevant but i throw SFC to scan and its says it cant reapair so I run DISM and it repaired 1 thing and then SFC didnt find any violations after DISM.

    P.s I hope kingston company isn't the matter of this issue :/
      My System SpecsSystem Spec

  8. #8

    Posts : 660
    windows 8.1

    In your asrock manual the advice for 1600 Memory is:

    5. If you adopt DDR3 1600 memory modules on this motherboard, it
    is recommended to install them on DDR3_A2 and DDR3_B2 slots.
    In the specifications 1600 ddr is supported but with (oc)
    Supports DDR3 1600(OC)/1333/1066/800 non-ECC, un-buffered memory

    In my analyse program i found that your memory is only running with 1333 mhz. So i suspect you have to make some adjustment in the bios.
    And it looks that you have installed the memory modules in a1 b1(BLUE).
    There is a asrockforum maybe you can ask there for help and the right set up for your memory hereASRock
      My System SpecsSystem Spec

  9. #9

    Posts : 14
    Windows 8.1

    Ok Ok , took some time and yea, if that changing of mine in BIOS will last (BSOD happen very less frequently) ill be happy, otherwise i just write in Asrock forums. Anyway thx for patience,knowladge and time and diagnose of course ;p
      My System SpecsSystem Spec

  10. #10

    Posts : 14
    Windows 8.1

    Hello again ;p i thought it was over but s.. happens. I wrote to dudes from ASRock, they point me to BIOS memory configuration that is stable (PC didnt blew up) heres thread if u wanna problem in setting new memory, BSODs by the way But problem is im getting some more BSOD, AND I KNOW that U said it was not accurate and not pointing to anything but i saw some autoanalysis from Instant Online Crash Analysis and i saw many strange and diffrent errors. U are Pro's and I dont know much about it so i have some amount of DMP's and stuff IF U are interested :P
    P.S I just hope that this changing in BIOS didnt some how mysteriously and deceptively corrupt my PC , if thats true, that makes me naive loser ;/
      My System SpecsSystem Spec

BSOD - before and after replacing RAM

Similar Threads
Thread Forum
BIOS Settings when replacing Win 8 HDD after Win 7
Hi, Please tell me if I am in the wrong Place or Wrong Forum. I have a New Asus X552LA with Win 8.1 64 Bit I also have a Spare New HDD I have Activated etc the Win 8.1 I would like to Remove the Win 8.1 HDD completely and save it until I want to use Win 8 On the New HDD, I would like to...
Installation & Setup
Replacing Win8 with Win7
I apologize if this thread is misplaced. I have a Lenovo K450 with Win8 pre-installed. I have a new copy of Win7 I purchased from Microsoft a few years back that I would like to install, but my PC seems to be locked to Win8. I can disable the secure boot in BIOS, and install WIN7, but...
Windows Updates & Activation
Replacing Laptop HDD
I got an HP laptop last year pre-installed with Windows 8 and I want to install a new HDD. How do I go about doing this and not losing any files? So far all I know to do is to create a system disc from the recovery manager, and then a recovery file on an external drive. Does this cover personal...
Installation & Setup
Replacing CPU + Motherboard.. Question
I'm about to replace(upgrade) my motherboard and CPU with a new one.. I just bought an i7 3770k + MSI Z77A-GD65. Anyways, after installing it and turning it on, will I be able to get to my desktop? If so, would I need to install a fresh OS? How would I do that? If I won't be able to get to my...
Drivers & Hardware
Is 8.1 replacing 8?
I run Win 8 on 2 desktops and I like 8 exactly as it is right now. I don't miss the Start Orb at all, and the Metro screen doesn't bother me. (One click and I'm on the desktop...not that difficult.) Nuff said. Now, it may be too early to ask this question, but does anyone here know if the...
General Support
Replacing Win 8 Pro 32 bit with 64 bit - How?
I upgraded my older, XP machine to Win 8 Pro. I did the on-line upgrade and all went well. Turns out it was a 32 bit install, even though the PC was 64 bit capable. (I understand now this is due to upgrading from XP) Yesterday I received my back up DVDs and decided to upgrade from the 32 bit...
Installation & Setup
Replacing the SSD?
I am looking at getting either a Samsung ATIV Smart PC 500T or the Asus VivoTab (not the RT) but I am wondering, is it possible to upgrade the SSD? My thought is that these may be running just normal SSDs and non chips soldered onto the board.
Drivers & Hardware

Eight Forums Android App Eight Forums IOS App Follow us on Facebook