Below are a series of emails exchanged with my IT department documenting my issues and experiences.
I've removed any personal information and only included my personal submissions of the faults and BSOD's.
Note that today, November 22, 2023, BSOD's occurred repeatedly upon boot. I could not even reach the log-in screen. I performed a system recovery and was able to launch (which is why I was able to imitate this thread), however BSOD's are still occurring. The last one was during a memory test, however I was working/adding stress while the memory test was in progress, which may have made it self inflicted.
----------
Tue 9/5/2023 10:48 AM
Over the long weekend, I decided to bite the bullet and perform a fresh Window’s 11 install to try and counteract the occasional blue screens I’ve been receiving as of late (Justin is aware). It took about 8 hours by the time I got all of my software reinstalled, but everything seemed to be sorted and working as intended as of last night. I also took a Macrium Reflect image after the fresh install + my software installs so that I have a (presumed) clean restore point.
This morning, I came into the office and fired up my computer (plugged into my dock). My monitors were a mess because I hadn’t yet configured anything, so I began to set my extended displays, primary monitor, etc. While doing this, of course, I got another blue screen. Unfortunately, I didn’t catch the error message. I fired back up, and since then there have been no problems (similar M-O to my experiences prior to the clean install yesterday).
So, clearly a fresh install didn’t do the trick. I’m now wondering if it’s something to do with the drivers for my dock? Although, I’ve had blue screens before (prior to the fresh install) while at the race track and alike without the dock part of the equation what-so-ever…
The dock in question is a Visiontek unit (recommended by Anthony). The drivers were downloaded from the official website to ensure I had the latest, here:
Dock in Question: https://visiontek.com/products/vt4510-dual-display-4k-usb-3-0-usb-c-docking-station-with-100w-power-delivery
Drivers: https://www.synaptics.com/products/displaylink-graphics
Really not sure where to go from here.
Happy to send a log file if you’d care to remind me how to locate it… Or alternatively, arrange for you guys to remote in and poke around while things are still ‘fresh’.
If it’s possible that it’s hardware related (I can’t imagine that it is, but who knows), I’ll need to act prior to the warranty expiring.
----------
Wed 9/27/2023 9:57 AM
Logging another event –
Since we last spoke things have been flawless. However, this morning upon initial startup (after windows boot/login, and me firing up Outlook), I received a ‘PFN List Corrupt’ blue screen message. As per our last conversation I’m not sure there’s anything to be done (updates required?) however if there is something we can check, please let me know. After some quick googling around, it sounds as though this may have been driven by an app/software, so if there is a way to identify what the trigger may have been, I’d be interested.
----------
Mon 10/2/2023 10:47 AM
Logging another event –
This time it was “IRQL_Not_Less_Or_Equal”.
I’m starting to suspect that maybe it has something to do with Outlook. The error message seems to change, but whenever I have a crash, it seems to be right after the computer boots up and I hit outlook to launch. I get into Outlook and hit a mailbox or sub-folder, then the crash ensues.
This time, it relaunched me into the BIOS. It wasn’t exactly a screen I recognized, either – Asus ROG EZ Flash Utility?
I ended up exiting and things ended up launching fine and behaving normally since.
----------
Wed 10/4/2023 9:39 AM
Logging another blue-screen event –
This time it was “DPC_WATCHDOG_VIOLATION”.
The system restarted and went into that BIOS menu which I again exited and everything started up normally.
Once again, the crash happened after everything was booted up and I engaged MS Outlook. Outlook booted, I started to get overlays and reminders about meetings, began clicking through my folders and the system froze – my extended monitors crashed and I could only see the main laptop screen. I still had mouse function but couldn’t click anything. After about a minute, the aforementioned blue screen appeared.
I’ll look for updates in a moment, but I haven’t installed any new software nor have I done anything different to my knowledge.
The blue screens are seemingly happening on their own with increasing intensity.
----------
Thu 10/5/2023 6:43 PM
Another blue screen a moment ago (and another new error I haven’t seen before) – This time it was “Unexpected_Kernel_Mode_Trap”.
I was running on battery power in a board meeting. The battery died and the machine went to sleep. When I went back to my desk, I plugged in my USB-C dock + power and booted up. Upon boot-up, the blue screen was received. After some Googling, it sounds like this error may be hardware related, which leads me to wonder if it had something to do with my USB-C dock and the associated drivers. We once thought as though my issues could be related to these devices, but I don’t think we were able to conclude anything.
The dock is a VisionTek unit and the drivers are native to them (below).
Dock: https://visiontek.com/products/vt4510-dual-display-4k-usb-3-0-usb-c-docking-station-with-100w-power-delivery
Drivers: https://www.synaptics.com/products/displaylink-graphics/downloads/windows
----------
Mon 10/16/2023 11:46 AM
Following up on the blue-screen investigation. Did you uncover anything from the logs?
Things ran very smoothly this past week/weekend while in Atlanta, however this morning I received another blue screen – this time it was SYSTEM_SERVICE_EXCEPTION.
The crash occurred while trying to start Outlook. Outlook would launch, but say (Not Responding). After about 3 attempts to close and re-open (including in Outlook Safe Mode), the machine crashed and the blue screen appeared. Upon restart, another blue screen appeared during boot up (right when it got to the log-in screen), and while the windows welcome jingle began to play, it glitched and gave a bizarre noise. I couldn’t catch that error code because it happened too fast.
Again, I’m getting the impression that:
- There’s some tie-in to Outlook in all of this – once booted, crashes seem to happen when I launch Outlook / a few seconds later when it’s syncing up.
- Something with the driver for my multiscreen display (previous email), because these issues have not been happening as of late while at the track without my dock.
----------
Tue 10/24/2023 10:23 AM
Just had another blue-screen incident. “IRQL_Not_Less_Or_Equal”.
Same M-O as previous; PC booted up, I opened Outlook, and the crash occurred.
Interestingly, this time upon re-start, my extended monitors wouldn’t function. I checked for updated drivers (there was something), installed them, and still nothing. I did a few restarts and again, nothing. Finally, I rebooted the dock itself and they began to work again. This hasn’t been something I’ve experienced before.
I’m growing more and more convinced that these problems are related to either Outlook or the dock drivers.
This said, my brother (with the same PC and dock), is not having these issues…
**NOTE** BSOD's HAVE ALSO OCCURED WHILE NOT PLUGGED INTO THE DOCK!
----------
Mon 11/6/2023 11:17 AM
Just had another blue screen. This time, it didn’t seem to be a function of Outlook, but rather, MS Teams. I fired up outlook and looked at the sync progress. It didn’t stipulate any specific folders, only ‘Updating XXXXXX’, etc. This was all completed successfully – no crash.
I then went to fire up MS Teams (manually, I have auto boot turned off), and right as the window popped up, the blue screen crash occurred.
I can’t say I’ve documented a circumstance like this to this point; it has always seemed to be Outlook related. Although, perhaps it was firing up automatically unbeknownst to me?
I’ve also noticed that, at one point, I had two instances of Teams installed on the computer. One was simply called ‘MS Teams’, and the other was something like “MS Teams Classic (Work or School)” – the latter is what I still possess on the machine.
----------
Tue 11/7/2023 10:01 AM
It occurred again this morning – more severe this time. “IRQL_Not_Less_Or_Equal”, seemingly related to a MS Teams boot. I EXPLICITLY turned off auto-startup for MS Teams, yet it booted up on its own this morning for some reason. When the window popped up, the machine crashed. I had Outlook opening simultaneously, but did not see any syncing that may have correlated to the crash.
Upon restart, I received consecutive blue screens before even reaching the login screen.
Eventually I was prompted with a windows screen asking me if I wanted to restart again, go to safe mode, inspect other options, etc. I selected basic restart and ultimately it worked and I’m ok now.
Questions/comments are:
1) Why would MS Teams auto launch when I know 10000% that I had it turned off?
2) Issues seem to be related to MS Office products, Outlook and MS Teams specifically.
3) Another culprit could be my dock and its drivers. I know I’ve had these issues while not connected to it, but I don’t want to rule it out completely.
4) Today was one of the more severe experiences I’ve had in a while. Is there any update on a potential action plan? What about my comments yesterday regarding weird/duplicate versions of MS Teams?
----------
Mon 11/13/2023 10:36 AM
Adding to the blue-screen log/drama. Today was pretty severe. Had a handful in sequence so I didn’t grab the error codes.
Wondering if it had to do with the new MS Teams. It installed itself on Friday, and auto set itself to autoboot it seems (I’ve since turned that off once I got logged on). Once again it looks like multiple MS teams versions are on this machine – Classic and the new one.
- Turned on computer, dock plugged in. Got to log-in screen but nothing was responsive – keyboard, etc.
- Manually forced a restart via the power button.
- Restarted, was able to log in, MS Teams autobooted and function began, then after about 30 seconds a blue screen emerged.
- The machine restarted, and upon reboot another blue-screen emerged before the log-in screen came up.
- It tried to boot into a safe mode/bios debug mode automatically; I cancelled and did a regular restart as I’ve documented in this thread previously.
- Startup was successful, now functioning normally.
----------
Wed 11/15/2023 10:37 AM
Another blue screen this morning - “IRQL_Not_Less_Or_Equal”.
The failure occurred while launching MS Teams and Outlook. I did both somewhat simultaneously, although my feeling is that the crash corresponded to the Outlook calendar. It occurred right as I received pop-up notifications about upcoming meetings. I watched the sync status on the bottom, and I didn’t see anything that corresponded to a specific folder or action; I only noted what I mentioned above about the calendar/pop-up.
Upon restart, the computer froze on the log-in screen after I typed in my password.
A forced power-button restart was required.
After this, I began to function normally.
----------
Thu 11/16/2023 9:29 AM
Another blue screen this morning, although I did not catch the error code.
This time, I made sure to take it slow and open one app at time. MS Teams did not auto launch, so I launched outlook (manually) first. It began doing its syncing and while going through that process, it crashed. I’m admittedly guessing as to what point it crashed (I feel like it was calendar related as all of the new emails looked to have populated), but for what it is worth, Outlook was the only application open when it happened.
I also waited a good 30 seconds or more before clicking anything to ensure DropBox, OneDrive, and any/all background apps, were successfully loaded and stable before engaging a new one.
----------
Mon 11/20/2023 10:30 AM
3 blue-screens this morning, 2 of which occurred during boot-up either before the log-in screen, or immediately after hitting enter to log-in.
The 3rd failure occurred when I booted up MS Teams and joined a meeting.
This is becoming unwieldy. Can we elevate the priority of some of the corrective actions we’ve discussed? Has there been any response from Microsoft on the tickets (Re: Windows 11 compatibility with higher-end hardware)? I’m worried that, especially after today’s experience, my associations of the issues with MS Office software may be incorrect.
If we can also confirm a date for the server install, that would be appreciated.