Search the Community

Link: Microsoft adds QR codes to Windows 10 'Blue Screen of Death' to help troubleshoot crashes

Thought I'd share this nugget of intel having spent the last few hours drilling down through the list of possible causes for some BSOD issues I was hitting. Scenario: - Gigabyte Z97 Sniper MB - Intel CPU - Gigabyte - System information viewer installed - Intel Extreme Tuning Utility (XTU) installed - Avast anti-virus installed Symptoms: - Intel XTU was not providing the CPU frequency and also reported it was being blocked from reading some information (but not crashing) - System information viewer was running when first installed (before any AV installs) but some weeks later (after no use) was BSOD crashing when run Cause: - Avast uses something called "hardware assisted virtualization" which obviously conflicts with these utilities Solution: Avast (2015) - Open Avast user interface (ie: double click the avast system tray icon) -> Settings -> Troubleshooting -> Un-tick/select "Enable hardware-assisted virtualization" option** ** There are warnings about doing this and the effect this change will have for things like sandbox so it may be something you choose to do when you need to do hardware monitoring tasks and then re-enable during "normal" usage. Result: - Intel XTU now reads and shows the CPU frequency in its monitor display - Gigabyte System Information Viewer no longer BSOD crashes Additional notes: I strongly suspect this issue extends to other hardware utilities for things like monitoring, overclocking, etc, and on numerous other motherboard types, etc... So, if you see any others that apply, please tag them on so others can find the issue and solution. Thanks Keywords (just to help others searching for this issue): anti virus, crash, blue screen, cpu, processor, monitoring, hardware

Hello, I have found out the hard way and wanted to share this information to see if this might help anyone else. During the summer we got onboard with Senso, coming from Impero. Software does seem like it worked well and so we pushed the client out to all devices. During the same summer we also upgraded to ESET Protect, which is also fully cloud. Not long after doing this and all staff returning we have discovered that the devices which both software were installed on started to Bluescreen randomly. And by randomly i mean literally no correlation with anything the staff members are doing. After many attempts to fully update, reinstall driver packages and resetting the devices the bluescreening would always come back straight away. After extracting the crash logs it looks like it came back to a possible issue with NETIO related to the ESET client. I then contacted ESET support to see if we could get this resolved. ESET then responded with the following "Do you run Senso in your environment? This is a known issue causing BSOD with ESET currently and we are still investigating and working with Senso Support to identify the issue and provide a workaround/solution." upon finding this out we liaised further with Senso and ESET to come to the following workaround; Disable the WFP Driver within Senso - This will resolve the issues at the expense of the following features; Dedicated Teacher Machine - https://support.senso.cloud/support/solutions/articles/79000116254-dedicated-teacher-pc Broadcast Screen – The options to select their own screen as “my computer” , you can add the teachers device to the group which will allow you to select the teachers device to be broadcasted. Website logs and control – We will not be able to record any visited URL’s nor we will we be able to control website access with block web etc. Application Control – Application logs will in fact still collect, however you will not be able to apply restrictions around what users can access Any element of Senso that will require packet \ IP level inspection will fail as this is what the WFP driver is used for, this is a complete list of functions you would lose when disabled. Upon applying this to a staff senso group, this was automatically disabled by senso and the devices have now seemingly cleared up, I'm only a few days in but will update if this is still an issue. This is the script they inputted into senso as a batch file under policies; $BlankFile = "c:\program files\renato\senso.cloud\disablefilter"$FileExists = Test-Path $BlankFileif($FileExists -eq $True){Return}else {New-Item -path "C:\program files\renato\senso.cloud" -Name "disablefilter" -itemtype file}Start-Sleep -s 10Restart-Service "senso.cloud.service" Hope this helps anyone out who may be in the same situation - Senso support can do all of this for you if you need help. At the time of me writing this there is still no fix and they seem to be pointing fingers at each other being the issue. Our hardware was Surface pro 7,8,9 Running windows 10 and 11 fully updated. Cheers, Quinn

Recently our RM ONE Eco machines running Windows 7 x64 have began to blue screen. There is no discovered pattern as to what is making them BS, although our suspicion is a windows update. The first one to go was approximately 2 weeks ago and they have been dropping off in that time. To press around 8 have crashed. The BS Error is BAD_SYSTEM_CONFIG_INFO, code 74 error, and shows while this windows 7 logo screen is floating about during boot up. We have found that by opening Safe Mode and ticking "OS Boot Information" in MSCONFIG the computer doesn't crash. This has led us to further investigate graphics or RAM issues, but theoretically I didn't believe OS Boot Info changed anything other than showing the Drivers load up and show the OS build version instead of showing the logo? We have the computer working in this manner, which is always good, but it would be nice to have a more water tight solution. Has anyone else had this issue with the Eco's? Thanks, TC.

Hey all, We have this strange problem whereby when we try and install windows using the install disc, on some PCs and a few laptop models we experience BSODs when booting from our original install disc. However if we use an SP2 disc, no BSODs occur. The disc we're using is the original XP disc, no SPs included, which is compatible with our volume licence. The XP SP2 disc works fine, but isn't compatible with our volume licence. I can't think of a way round this. I'm not sure if slipstreaming the original disc with SP2 will fix the bsod issue, and am not sure why the BSODs are occuring. Its a strange one. Any ideas peeps? cb

Hi, I have had this problem for a couple of months and its driving me mad. All of our existing machines appear to be running fine on the network but every time I build a new machine it hangs or BSOD's at "Applying your personal settings". I have had this problem on at least 2 different models of PC, possibly 4 (I can't remember now) - Optiplex 760, Optiplex 790 and also possibly on Optiplex 740 and Optiplex 780 (All of our PC's are Dell). But I have the same models working fine on the network, it's only when I try to install/re-install XP. So forgetting everything that I've done in the last couple of months to try fix it because I can't remember everything, here's what's happened in the last two days. I did the following steps on both of the Optiplex 790's at the same time. 1) Set up two Dell Optiplex 790's and installed XP Pro SP3 (using an ISO I downloaded from Microsoft Volume Licensing site). 2) Installed all of the latest drivers (from Dell's website using service tag) except for one of the chipset and the graphics drivers as they needed .NET Framework first. I also upgraded the BIOS at the same time. 3) Installed all available Windows Updates (excluding PowerShell, Windows Search, Browser Choice and Security Essentials or what ever it's called) 4) Installed last two drivers (mentioned in step 2) 6) Formatted D: drive. 5) Installed Adobe Flash Player, Reader and Shockwave from their website. 6) Installed Microsoft Office 2007 Enterprise from CD. 7) Installed Microsoft Updates and installed all of the updates available for Office along with Silverlight 8) Installed a driver from Microsoft Updates. I can't remember the exact name but it was something to do with Intel SOL. (I can probably check the update history if I need to get the name) 9) Installed Adobe CS5 Web Premium from CD. 10) Installed Adobe Acrobat 9 from CD. 11) Joined the computer to our domain and left both machines in the default "Computers" container in AD. 12) Logged in as the domain Administrator account. - At "Applying your personal settings" one machine rebooted (Probably a BSOD but they are set to reboot instead of displaying it by default) and the other just sat on that screen doing nothing for about 17 hours. 13) Logged in as the local Administrator account and enabled UserEnv logging and Winlogon logging, then rebooted. 14) Logged in as domain Administrator account and both machines logged in successfully... :@ 15) Logged out and logged in using my own account (Domain Admins & Administrators). Both machines rebooted. At this point I started using just one of the machines 16) Booted with it set to display any BSOD's instead of rebooting. 17) Logged in with my account and got a BSOD (0xC000021A) 18) Booted the same machine and used msconfig to disable all startup programs (then rebooted). 19) Logged in with my account and this time at "Applying your personal settings" I got a winlogon.exe error saying "The instruction at 0x7c911766 referenced memory at something. The memory could not be read". - When I clicked OK the PC rebooted obviously because winlogon was terminated. 20) On same machine logged in as local Administrator account again. 21) Used msconfig to disable all Non-Microsoft services and rebooted. 22) Logged on with my account and it rebooted again at the same place... As you can see these are clean installs of XP there is no imaging involved and they should only be loading our default policy which is linked to the domain and contains things like password expiry and "Always wait for the network at computer startup and logon". When I originally started having the problem I'm sure I remember that if you managed to get an account to log in by repeatedly deleting the local profile and logging back in until it worked, that account would always be able to log in to that machine in future (or so it appeared). So maybe it could be something to do with generating the user profiles. That's all I can remember right now, may think of other things later. If you need more information just ask Thanks in advance, Dan

Teacher found a 8MB powerpoint that consistantly BSOD's 1809 when printing, 3 different computers so far. Updated driver to Kyoceroa TASKalfa 3051ci KX 7.4.830.0 no change. Found an old laptop with 1609 on, which works. Think it's this file: https://jointhepod.org/teachers/mission-world-wide-web-assembly Anyone have similar problems?

Does anybody else have issues with Windows 10 DPC Watchdog errors? If so how have you fixed them? In my public school job the teachers have Windows 10 ASUS TP200S laptops and since September we've started to have an increasing amount of laptops with the DPS watchdog error code. Usually the laptop would lock up and then shortly the blue screen with the DPS Watchdog error would pop up before restarting. When trying to run the blue screen troubleshooter it finds no blue screens occurred even though I just experienced one. Usually we to fix this we try to allow the laptop to install any pending updates, I run checkdisk (chkdsk), and the system file checker (SFC-scan now) in addition to manually checking each driver to see if there are any updates for them. Sometimes this appears to work and other times the laptop comes back to us. The current laptop I'm working on, it first came in at the beginning of February and I did all the above then returned it to the teacher. No problem until recently the teacher started having multiple errors in one day. These errors are tricky and hard to duplicate in my experience they show no consistency, the error could happen whether you're at the login screen or in google classroom. Any advice and help would be appreciated it, thank you in advance!

Hello there. What I'm going to try and explain now may be very vague, but I just want to see if anyone else has had the same issue as me, so here goes! We have a Server 2008 Standard server. Installed on the server is Forefront TMG. I have configured a web chain out to a proxy the entire site uses provided by our local council. I have added all the rules into the firewall that we need as a school, and the net connection works exactly how I would expect it to. The issue I have, is that when any changes are made to any aspect of networking on the server, I get a BSOD telling me that fweng.sys is the problem (I don't have dump log to hand, but I can get it if anyone thinks they might be onto something.) The server can run in a stable fashion if the following is done: Disconnect internal and external interfaces from server Turn on server and leave to boot into Windows Log on and leave to settle reconnect network cables one at a time Check that internal shares can be reached Check that external websites can be reached Log off Once it's up and running, it serves the whole site perfectly until you try to make any changes to it. I can log onto the server and use it in any fashion I wish. So long as I don't try to make any changes in Forefront or adjust any network settings, I can be sure it won't "fall over" again. Obviously this is no good for us, as we are unable to do anything to this server in it's current state. We have disabled the internal network card, and have added an HP Broadcomm adapter in it's place. All drivers have been updated and we have attempted to run Windows update. When Windows update is run, we get a BSOD and the same error message about fweng.sys (which I believe is the Firewall Engine). We have NOT updated the firmware on the network cards, but we will be doing so over half term. Basically, I was wondering if anyone has come across an issue like this. Idea's and suggestions are very welcome.

Hi, Problem cropped up the last 3 weeks that I’m hoping is a M$ problem as its affecting many different laptops in the same scenario, and can be replicated We use Offline Files and Sync the entire user’s documents area. However users have been recently getting a BSOD (Blue Screen of Death/Doom/Rolf Harris/Whatever) all with the same error. The system in place allows them to log in offline (at home) and we allow them to connect to their own wireless systems also. Previously there have been no problems; the users are not doing anything specific to cause the error. Manipulating a word doc, facebook poker and we recreated it by just leaving Radio1 stream running. Its important to note that this DOES NOT happen when on the wireless at school Anyone else using the same / similar setup? Many thanks, Simon BSOD is as follows RDR_FILE_SYSTEM STOP: 0x00000027 (0x00000000BAAD0075, 0xFFFFFA6019B5CC58, 0xFFFFFA6019B5C630, 0xFFFFFA6006A3F300) rdbss.sys Address FFFFFA6006A3F300 base at FFFFFA6006A1C000

Hey Guys Sorry but this is the best place I find to ask questions and I'm having some serious issues with my laptop that some of you may know I bought only 2-3 days ago. Whenever my computer goes to sleep or is idle for a long time it BSOD and I can't understand why. So I did a fresh install of Windows, installed all the drivers that I needed and it is still doing it !!! I had to ring Dell but their customer support is appauling. A BSOD just occured while configuring Windows updates. I will upload the .dmp files if any of you could have a look. It says driver_state_failure in BlueScreen Viewer 0x100009f as the bug check code . Please help.... 111413-10108-01.zip

Hey, I have a laptop and upon boot up i get BSOD (Blue Screen Of Death) i have tried loading in safe mode and this also fails to work... the error i am getting is Unmountable-boot-volume. Any ideas? help would be greatly appreiciated

Damn, after a week of blaming WDS for my woes it turns out it's the bleedin' VMware. I'm using my ESXi 5.0.0 update 1 and using a VM8 machine. I built a Windows 7 64bit PC. (ace as I can use snapshots etc.) I deliberately did NOT install the VMware drivers as I wanted the image clean. Anyhow it turns out that sysprep kills the image. After a reboot the PC then BSOD's so bad I can't get back into windows to even look at the minidump. I can't read the bsod as it flies past so quick.... Anyone run into this? Ideas? NO DO NOT MENTION MDT! (I looking now but it's involved and I've invested loads of time to this:)