Blue Square & Dots (Freeze) + BSOD when Booting


  1. Posts : 9
    Windows 10 Pro x64 Version 1909
       #1

    Blue Square & Dots (Freeze) + BSOD when Booting


    Dear TenForums,

    https://i.imgur.com/6RE3c08.jpg
    https://i.imgur.com/10cQy1R.jpg

    I've recently bought and built a new system. However, after a couple of days of clean usage i started having Blue Lines & Dots during my booting which results in a freeze and not procede any further (i'd have to manually power it off/on for it to go away.

    I personally troubleshooted most of it (performed benchmarks with each monitor individually, updated drivers, etc). However, i finally ended up getting a BSOD today (DPC WATCHDOG VIOLATION).

    I took my time to investigate the issue and it ended being something related with SSD/Main Booting Drive (Driver, Firmware, etc). I downloaded Samsung Magician and replaced the Windows Driver with Samsung Driver per many suggestions online as i own a Samsung 970 PRO. However, Ztuker told me to personally use V2 log collector and produce a BSOD file so it could be reviewed and narrowed down more exactly to which was the main reason of the BSOD.
      My Computer


  2. Posts : 13,950
    Windows 10 Pro X64 21H1 19043.1503
       #2

    Thanks for moving over here.

    The log files are in a non-english language and some can not be analyzed. Please change the system language to English and post a new log collector zip. Use the V2 log collector shown in the Blue Screen of Death (BSOD) Posting Instructions link as it collects more information than the standard collector.

    Add, Remove, and Change Display Language in Windows 10
    How To Change Language In Windows 10 Operating System - YouTube

    You can put the language back to normal once done though you may have to do this multiple times if we need you to run the log collector script again in the future. Won't help with data that's already collected but newly generated data will be in English which can help.

    Thanks, Rich

    Want you to run the V2 log collector each time a BSOD occurs and upload the zip file.
      My Computers


  3. Posts : 13,950
    Windows 10 Pro X64 21H1 19043.1503
       #3

    Not mush useful info in the dumps unfortunately. There should be a full memory dump in C:\Windows\MEMORY.DMP. Please copy that to another location then zip it and upload to a file sharing site like OneDrive or Google Drive and post a share link to it here.

    May not be any more help but it will have more data so may be of use. Won't hurt to have it.

    Event logs may have some good info in them but since they are not n English I can't read them, sorry.
      My Computers


  4. Posts : 9
    Windows 10 Pro x64 Version 1909
    Thread Starter
       #4

    Hello, Ztruker. I've successfully applied the English Language Pack so everyone who's willing to contribute can take a look and have proceeded to zip the MEMORY.DMP and uploaded it to Google Drive. Leaving the share link below.

    Google Drive: Sign-in
      My Computer


  5. Posts : 1,867
    Windows 10 Pro 2004 20H1
       #5

    Your share link requires permission after signing in to Google Drive.

    Attachment 285262

    You can share individual files, and post the link to that file only.

    Then no one has to sign in, and then request permission.
      My Computer


  6. Posts : 9
    Windows 10 Pro x64 Version 1909
    Thread Starter
       #6

    I ended up suffering some kind of booting issue again and the system repaired some kind of data on the Disc-C (No BSOD).

    I've instantly collected data on the V2 log collector in hopes it displays some kind of helpful information. Also, i've uploaded another MEMORY.DMP and given the correct permissions: MEMORY.rar - Google Drive
      My Computer


  7. Posts : 1,867
    Windows 10 Pro 2004 20H1
       #7

    Your crash dump file thinks that pci.sys is the likely cuplrit.

    However, it usually isn't.

    In looking at your Windows Error Reports, there are three things that have caused app and kernel crashes, and a couple are likely responsible for the BSOD.

    Corsair - Corsair.Service.DisplayAdapter.exe

    Razer - RzSDKService.exe

    NVIDIA - nvlddmkm.sys

    Video drivers are famous for causing DPC WATCHDOG VIOLATIONS and blaming pci.sys.

    I would start by updating the drivers for those devices, and see if there is improvement.
      My Computer


  8. Posts : 9
    Windows 10 Pro x64 Version 1909
    Thread Starter
       #8

    Thank you for your reply, Navy.

    I ended up updating Corsair iCUE (Application that controls Chroma-related products of Corsair) which was running on an older driver version. I also investigated what you mentioned about the "Corsair.Service.DisplayAdapter.exe" and found many topics such as: Corsair.Service.DisplayAdapter - The Corsair User Forums which are pretty much related to the same kind of issue i'm suffering on my boot and many others as well. Worst scenario, i'll end up uninstalling the program.

    I couldn't find any driver updates for Razer Chroma SDK (RzSDKService.exe) neither for my Nvidia GPU which was updated 2 days ago. For now, it seems the main issue is the Corsair Application. However, i might be thinking there has to be an conflicting issue between the 2x Chroma-Controlled Application(s) that don't get along together. I'll perform some further testing for a couple of days or until i face another Booting Error/BSOD and report any updates over here.

    - - - Updated - - -

    I uninstalled the Corsair iCUE Software (Corsair.Service.DisplayAdapter.exe) and all it's remaining files under the HKEY Folder(s). However, i ended up getting another Blue Square during Boot that i had to manually force to shutdown and restart for it to go through. Uploaded my most recent V2 log collector in hopes it shows something useful this time. Not sure what else to end up doing for this to stop.
      My Computer


  9. Posts : 13,950
    Windows 10 Pro X64 21H1 19043.1503
       #9

    No new dumps.

    Looking at the system event log, I did find this:

    I see this error which is Razer Chroma SDK Service
    Code:
    6/25/2020 11:36 PM
    Windows Error Reporting
    Fault bucket 1727950090115760078, type 5
    Event Name: BEX
    Response: No disponible
    Cab Id: 0
    Problem signature:
    P1: RzSDKService.exe
    P2: 2.8.2.51
    P3: 5eeb662e
    P4: ucrtbase.dll
    P5: 10.0.18362.815
    P6: bea5fce0
    P7: 0009caa2
    P8: c0000409
    P9: 00000005
    P10: 
    Attached files:
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD66A.tmp.mdmp
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD6AA.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD6BA.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD6BE.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD6CF.tmp.txt
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_RzSDKService.exe_492d6ec0d5e233e37a3a0799189ee37c8cb1f13_89c86860_35487fea-be76-468f-9ae3-c5512f9c0249
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: f16c8cdc-4c91-4459-8caf-8796d5b25134
    Report Status: 268435456
    Hashed bucket: b5cd26462deb197087fae973aef43fce
    Cab Guid: 0
    Followed immediately by a 133 BSOD.
    Code:
    6/25/2020 11:36 PM
    Windows Error Reporting
    Fault bucket , type 0
    Event Name: BlueScreen
    Response: No disponible
    Cab Id: 0
    Problem signature:
    P1: 133
    P2: 0
    P3: 501
    P4: 500
    P5: fffff80727373358
    P6: 10_0_18363
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    Attached files:
    \\?\C:\Windows\Minidump\062520-12968-01.dmp
    \\?\C:\Windows\TEMP\WER-18343-0.sysdata.xml
    \\?\C:\Windows\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5383.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5393.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5392.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER53A3.tmp.txt
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_106952712a9fbd24b66fa85074e68384d0647069_00000000_cab_4311f060-80b4-4561-a84f-32bade755fe4
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: a35dc4dc-1186-4086-83f9-6622aae6cd7a
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    I suggest replacing your Razer mouse with a different one, and uninstall the driver for now.
    Test that way and see if the problem is resolved. If yes then you either need to find a new, up-level driver for your existing Razer mouse or get a new mouse.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 04:28.
Find Us




Windows 10 Forums