RBS + Core BSOD on every boot

Discussion in 'Systems' started by Limzui, Feb 2, 2018.

Thread Status:
Not open for further replies.
  1. Limzui

    Limzui Member

    I've been trying to search around for any possible causes of this but i can't seem to find any. Weird thing is that I have 2 friends with the same RBS + Core setups and both of them are having the exact same issue.

    Details:
    1. Upon booting up the RBS with the core connected, the keyboard lights up but the screen stays black
    2. After approximately a minute the login screen finally loads up and goes to the desktop (I don't have a windows login password)
    3. Once at the desktop, about 10 seconds later the laptop BSODs. BSOD message doesn't always stay the same but the underlying culprit is always ntoskrnl.exe. BSOD messages include: irql_not_less_or_equal, page_fault_in_nonpaged_area, kernel_security_check_failure
    4. After the laptop reboots itself from the BSOD, it will startup as per normal and everything will run normally without any further issue until the next time the laptop is turned on

    -This issue only started recently within the past few months so I suspect it's related to a windows update
    -I have no desire to talk to support over this issue as I'm very certain that they're clueless and will ask me to perform a factory reset
    -The issue also happens when the RBS is powered on without the core attached (not sure if this happens 100% of the time, but when core is attached, definitely 100% of the time)
    -Me and my 2 friends' setups are: RBS (6500U) + Core V1, RBS (6500U) + Core V2, RBS (7500U) + Core V2

    I really hope someone out here can shed some light on what's causing this and maybe help out with a solution. If you need any additional details feel free to let me know.

    Thanks for taking the time to read this.
     
    jackcastrov likes this.
  2. Joikansai

    Joikansai Well-Known Member VANGUARD

    I’m on 7500U Stealth and Core V2, I’ve also Blade 14 7700HQ. On Blade 14 it’s no such issues but you have to disable GPU on the Core to let it hot plug (plug and play without rebooting). The problem with the Stealth i think is the power supply from the core and if you have it worked fine before then maybe some Windows Update is the culprit. But the solution for me is just unplug the Core after using it or before closing the lid. Try to unplug it when the green light shows (screen off) with the Core plugged, it’ll wake the screen in my experience. I hope Razer also addresses this though since some users maybe use the USB ports especially on V2 even not using the GPU inside the Core (as docking station). Btw I’m not on FCU and has no BSOD issues only the don’t waking up screen after sleep with Core plugged.
     
  3. lorein0688

    lorein0688 New Member

    Try to install the latest drivers as in many cases the BSOD error is related to drivers. So, go to computer manufacturer website and try installing the latest update for the incompatible device driver.

    If this help you then is okay if not then then try uninstalling the latest program installed and perform system restore to fix the BSOD issues.

    fixwindowserrors.biz
     
  4. Limzui

    Limzui Member

    I did a system recovery and installed all the latest drivers from Razer's software download page as well as Intel Driver & Support Assistant and Nvidia's website. The issue is still persisting. After running driver verifier I have narrowed down the offending driver to Rzudd.sys.

    WhoCrashed report:
    This was probably caused by the following module: rzudd.sys (0xFFFFF80B40DF8DF0)
    Bugcheck code: 0xD5 (0xFFFFF70668B3CFFA, 0x0, 0xFFFFF80B40DF8DF0, 0x0)
    Error: DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
    file path: C:\WINDOWS\system32\drivers\rzudd.sys
    product: Razer Rzudd Engine
    company: Razer Inc
    description: Razer Rzudd Engine
    Bug check description: This indicates that a driver has referenced memory which was earlier freed.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rzudd.sys (Razer Rzudd Engine, Razer Inc).
    Google query: rzudd.sys Razer Inc DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL

    I'm gonna try to uninstall and reinstall all my Razer software again and hope for the best...
     
  5. Limzui

    Limzui Member

    Reinstalling of Razer software did not work. Ended up contacting Razer Support. I have reproduced my message to them below in full:

    I have uninstalled and reinstalled the TB3 driver (ver 15.3.39.250) from the link provided as suggested. Unfortunately the issue is still unresolved.


    Additional information that might help:

    -I’m using Razer Blade Stealth 6500U, with Razer Core V1 United States version, and ASUS GTX 1070 STRIX
    -I have 2 other friends with similar setups who are encountering the same issue as me
    -Their setups are: [Razer Blade Stealth 6500U, Razer Core V2 (SG), Zotac GTX 1060 AMP! 6GB] & [Razer Blade Stealth 7500U, Razer Core V2 (SG), ASUS GTX 1060 Dual]
    -Razer devices I have connected to my RBS: Razer Core V1 United States version, Firefly Hard, Mamba TE, Blackwidow X TE, Man O’ War wireless
    -The issue only started recently, about 1-3 months back
    -The problem only happens on a cold boot. It doesn’t happen on restarts
    -The problem also does not happen when I boot up immediately after shutting down, only happens when I boot up after a few hours since last shut down
    -The BSOD stop code is usually different on every boot, but all of them points to some form of memory corruption or power failure
    -Some of the BSOD stop codes I have encountered are including but not limited to: DRIVER_POWER_STATE_FAILURE, VIDEO_ENGINE_TIMEOUT_DETECTED, WIN32K_CRITICAL_FAILURE_LIVEDUMP, CUSTOM_ERROR, IRQL_NOT_LESS_OR_EQUAL, PAGE_FAULT_IN_NON_PAGED_AREA, BAD_POOL_HEADER, DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
    -Using WhoCrashed to analyse dump files will always not be able to identify the offending driver as the crashes all happen in the windows kernel
    -The faults will always be found in these executables: ntoskrnl.exe, ntkrnlmp.exe, nvlddmkm.sys
    -After running Driver Verifier (standard settings, select all drivers), the offending driver will be narrowed down to rzudd.sys
    -After the BSOD caused by running driver verifier, Synapse becomes crippled and I have to uninstall and reinstall it before I can use it again.
    -[Note] I have only enabled kernel dumps instead of complete dumps as the BSODs are happening in the windows kernel.
    -[Might be unrelated] Everytime I on my laptop and Synapse auto signs in, all my connected Razer devices sync properly except for my Blackwidow X TE lighting. It will always revert back to spectrum cycling and I have to always manually change it back to custom. My custom chroma profile doesn’t disappear but it’s always just not set to default when it should be.


    WhoCrashed report after running driver verifier:

    Crash dump directories:
    C:\WINDOWS
    C:\WINDOWS\Minidump
    C:\WINDOWS\LiveKernelReports

    On Mon 12/2/2018 11:43:26 PM your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\Minidump\021218-17984-01.dmp
    This was probably caused by the following module: rzudd.sys (0xFFFFF807A37F8CE0)
    Bugcheck code: 0xD5 (0xFFFF80073B4DEFA0, 0x0, 0xFFFFF807A37F8CE0, 0x0)
    Error: DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
    file path: C:\WINDOWS\system32\drivers\rzudd.sys
    product: Razer Rzudd Engine
    company: Razer Inc
    description: Razer Rzudd Engine
    Bug check description: This indicates that a driver has referenced memory which was earlier freed.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rzudd.sys (Razer Rzudd Engine, Razer Inc).
    Google query: rzudd.sys Razer Inc DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL


    Bluescreenview report:


    ==================================================
    Dump File : 021218-17984-01.dmp
    Crash Time : 12/2/2018 11:43:26 PM
    Bug Check String : DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
    Bug Check Code : 0x000000d5
    Parameter 1 : ffff8007`3b4defa0
    Parameter 2 : 00000000`00000000
    Parameter 3 : fffff807`a37f8ce0
    Parameter 4 : 00000000`00000000
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+175880
    File Description :
    Product Name :
    Company :
    File Version :
    Processor : x64
    Crash Address : ntoskrnl.exe+175880
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\WINDOWS\Minidump\021218-17984-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 16299
    Dump File Size : 936,852
    Dump File Time : 12/2/2018 11:49:41 PM
    ==================================================

    Steps I have previously taken to try to solve the problem:

    -Performed a sfc /scannow
    -Performed a DISM /online /cleanup-image /restorehealth
    -Performed a chkdsk /scan
    -Performed a F9 System Recovery
    -Updated all Intel drivers using Intel Driver & Support Assistant
    -Updated Nvidia Geforce Drivers & Geforce Experience
    -Updated all RBS hardware Drivers on your software download page
    -Did a clean uninstall of all Razer software (Synapse 2.0 and Cortex), and deleting all leftover Razer folders in my RBS, before reinstalling the latest versions from the website
    -Checked for latest windows updates

    I hope all these will be of help to you and your team in solving my case. I look forward to your reply.

    To which they asked me to fill up a RMA form. I have 2 friends, one of which has a brand new (~3 months) Blade stealth and Core V2 which are also experiencing the same problem. I am pretty certain a RMA won't be able to solve anything.
     
  6. Joikansai

    Joikansai Well-Known Member VANGUARD

    Thunderbolt driver doesn’t have anything to do with your BSOD, I’ve already tried 3 different TB3 driver (for better performance) and no issues at all till now, I’m guessing the culprit is windows version, due battery issue I’m still on Creator 1703, both on stealth and Blade 14. Try to look at eGPU.io i think I saw similar BSOD issues there but not on same brands eGPU setting, they do some drivers etc configuration I think.
     
  7. Limzui

    Limzui Member

    I'm on Win 10 v1709, OS build 16299.214. I searched eGPU.io and I found one article that describes something similar to what I'm experiencing, however that article is targeted towards mPCIe and NGFF/M.2 eGPUs, not Thunderbolt 3 ones like the core. The article URL is https://egpu.io/forums/expresscard-...ving-detection-bootup-and-stability-problems/

    The particular section is reproduced here as well:

    3. A black bootup screen or ACPI_BIOS_ERROR windows bootup BSOD

    Here the BIOS doesn’t know what to do or mangles the ACPI when it sees an eGPU. The latter preventing Windows from loading successfully. So the solution is to not let the BIOS see the eGPU. A couple of ways of doing that as below. The PSU must be set to be permanently on as described above for this to work.

    1. Set the delays on the eGPU adapter (PTD – EXP GDC or CLKRUN/PERST# on PE4L/PE4C). Boot into Windows or Setup 1.35. Is the eGPU detected? Note: if this bypassed the black bootup screen then you’ll probably find a reboot will again black screen the system. This delay works when doing a cold boot from the system being powered off.

    2. Start the system without the eGPU adapter interconnect HDMI cable disconnected(eg: between eGPU adapter and EC/mPCIe/M2 end).

    – halt Windows bootup with F12/F8 attach your interconnect cable. Is the eGPU detected in Windows device manager?
    – or boot into Setup 1.35 , attach your interconnect cable, hit F5 to scan for the eGPU. Is the eGPU detected?

    3. With no eGPU attached:

    – halt Windows bootup with F12/F8 hotplug your eGPU adapter interface. Is the eGPU detected in Windows device manager?
    – or boot into Setup 1.35 , hotplug your eGPU adapter interface, hit F5 to scan for the eGPU. Is the eGPU detected? If the eGPU isn’t detected, bootup with wifi connected into Setup 1.35, hotplug your eGPU interface, hit F5 to scan for the eGPU.

    The suggested solution makes sense but I have no idea how to do it for the Core.
     
  8. Joikansai

    Joikansai Well-Known Member VANGUARD

    I don’t understand also that (on eGPU.io), but for reference you can attach it to support so they could address the issue quicker, maybe there’s also users that facing similar issue besides your friend. If o were you of course I want also simply plug the core to the stealth, let synapse and windows doing their job without configuring like user on egpu.io, that’s what the core and stealth made for. If you wouldn’t mind, how about testing it on Creator(1703)?
     
  9. Limzui

    Limzui Member

    Update for anyone out there with the same issue as me:

    This what I sent to Support because naturally all their remedy steps are copy-pasted and don't work:
    Just to share with you what I have found out so maybe you can share this with the relevant departments:
    • The cause of the problem is shutting down a RBS while it is connected to a Razer Core
    • If the above condition is fulfilled, the next time you turn the RBS on, regardless if it is connected to a Core or not, it will show a black screen for a long time before loading the desktop and then it will bluescreen shortly after
    • The problem should lie with Razer software utilizing Nvidia resources
    • The workaround I have employed that prevents the black and bluescreens from happening is: Before shutting down my RBS when it is connected to a Core, I open up the Nvidia GPU activity and clicked “Disconnect GPU” (See attached)
    • After disconnecting the GPU, I shut down the RBS as per normal
    • The next time I boot up my RBS, it will boot up perfectly fine, but the GPU will be disabled in the device manager
    • I just need to manually enable the graphics card in the device manager each time
    Disconnect GPU.png
     
  10. Joikansai

    Joikansai Well-Known Member VANGUARD

    It’s weird, I just finished AC Origins and mostly played on stealth and Core v2, the only issue was CPU throttling but solved with undervolting it. You don’t have to disable GPU on setting with stealth actually since it has no dGPU that would crash with GPU in the core, plug and unplug only that what I need to do, even if after sleep it doesn’t recognize the GPU. GPU Issue maybe? How about your friend who has similar setting with me (stealth i77500 and Core v2), does he also still have BSOD Issue?
     
  11. Limzui

    Limzui Member

    I do not have any throttling issues. But I do have a 95mv undervolt (just to reduce temps). For me if i do not disconnect my GPU i will definitely get a bluescreen the next time i turn on my RBS. It has been happening every single day for a few months already. Disconnecting my GPU was the only reliable way I have managed to solve it so far. My friend stays at his college dorm and only goes home during the weekends so he only has his core 2/7 days a week. He also experiences the same problem everytime he goes back to his dorm (because the last time he shut down his RBS was with his core connected at home)
     
  12. Joikansai

    Joikansai Well-Known Member VANGUARD

    I see, is it still under warranty? I would rise RMA ticket if it still is. It should be designed for hot plug (plug and play) with stealth. I have to disable dGPU only on my Blade 14, and it is also with their software (gpu switcher), super easy especially when you’re using external monitor and want still to use smoothly without restarting it when the Core is off. My throttling Issue was only when I play PUB or AC Origins on stealth without uVolting, with same uV value as yours it’s smooth. Playing OW, Destiny 2, I don’t need to uVolting it.
     
  13. Limzui

    Limzui Member

    Both are not under warranty any more. I believe my issue has nothing to do with PnP, as I am not even unplugging my core at all. My core is plugged into my RBS 24/7. It has been for more than a year and I have had no problems with that for almost a year until recently.
     
  14. Joikansai

    Joikansai Well-Known Member VANGUARD

    What windows version do you have on it now? Try to run previous version before you get the issue, I’m not quite sure but I think i saw also BSOD issue after Windows Update on egpu subreddit.
     
  15. Limzui

    Limzui Member

    I'm on Windows 10 Home ver 1709. I don't intend to do a roll back as it is too troublesome, and I am currently satisfied with my temporary workaround so I'll leave it as it is for now. Thanks for taking the time to reply to my thread nonetheless Joikansai :)
     
Thread Status:
Not open for further replies.
Sign In with Razer ID >


Don't have a Razer ID yet?
Get Razer ID >