- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Coaching Changes
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
Windows blue screen error
Posted on 9/5/20 at 11:11 am
Posted on 9/5/20 at 11:11 am
I've gotten the Windows blue screen a few times now recently with the message K mode exception not handled. Google tells me its due to bad drivers. I updated Windows yesterday and got it again. Also, when it comes back up my Firefox extensions are gone.
How do I know which drivers to update? Do I have to go item by item in device manager or is there a way to quickly tell which one might be out of date or bad?
How do I know which drivers to update? Do I have to go item by item in device manager or is there a way to quickly tell which one might be out of date or bad?
2
Posted on 9/5/20 at 3:05 pm to Brosef Stalin
Sometimes you can find information on the driver causing the issue in your Event Viewer, sometimes not.
To access Event Viewer in Windows 10 just right-click on your Windows icon, go to Search then type in Event Viewer then click on Event Viewer.
Expand Windows Logs then click on System. Once this populates look for the red X's and/or yellow !'s. For something like this you should see a series of them in a row (as things fail) when the event occurs. Click on the earliest one around your most recent BSOD then go through them until you find one discussing which driver failed. You might end up having to do a little research on the hardware ID.
To access Event Viewer in Windows 10 just right-click on your Windows icon, go to Search then type in Event Viewer then click on Event Viewer.
Expand Windows Logs then click on System. Once this populates look for the red X's and/or yellow !'s. For something like this you should see a series of them in a row (as things fail) when the event occurs. Click on the earliest one around your most recent BSOD then go through them until you find one discussing which driver failed. You might end up having to do a little research on the hardware ID.
Posted on 9/5/20 at 3:50 pm to Bard
All of the recent error messages on Event Viewer are about Skype, which I've never used. Don't see how that failing would give a BSOD. Hopefully uninstalling it works.
Posted on 9/5/20 at 6:31 pm to Brosef Stalin
quote:
All of the recent error messages on Event Viewer are about Skype, which I've never used. Don't see how that failing would give a BSOD. Hopefully uninstalling it works.
Maybe it corrupted your audio or video driver?
Good luck!
Posted on 9/7/20 at 10:26 am to Bard
Its doing it again. 
The problem file is Ndu.sys. Found an article on Microsoft's page that said to update the ethernet driver. I did find an updated driver for the Realtek PCIe GBI Family Controller. Hopefully that fixes it. Running an sfc scan now.
The problem file is Ndu.sys. Found an article on Microsoft's page that said to update the ethernet driver. I did find an updated driver for the Realtek PCIe GBI Family Controller. Hopefully that fixes it. Running an sfc scan now.Posted on 9/8/20 at 12:30 pm to Brosef Stalin
There's freeware called bluescreenview by Nirsoft that Ive used in the past. Whenever windows crashes it saves a log in the minidump. This program displays the results of the minidump and makes it easier to identify the driver thats causing the crash.
quote:
?BlueScreenView v1.55
Copyright (c) 2009 - 2015 Nir Sofer
3K
Related Utilities
WinCrashReport - Displays a report about crashed Windows application.
WhatIsHang - Get information about Windows software that stopped responding (hang)
AppCrashView - View application crash information on Windows 7/Vista.
See Also
NK2Edit - Edit, merge and fix the AutoComplete files (.NK2) of Microsoft Outlook.
Description
BlueScreenView scans all your minidump files created during 'blue screen of death' crashes, and displays the information about all crashes in one table. For each crash, BlueScreenView displays the minidump filename, the date/time of the crash, the basic crash information displayed in the blue screen (Bug Check Code and 4 parameters), and the details of the driver or module that possibly caused the crash (filename, product name, file description, and file version).
For each crash displayed in the upper pane, you can view the details of the device drivers loaded during the crash in the lower pane. BlueScreenView also mark the drivers that their addresses found in the crash stack, so you can easily locate the suspected drivers that possibly caused the crash.
Posted on 9/8/20 at 12:36 pm to McChowder
I've tried looking at the minidump but it wants to open in Visual Studio. Is it just code? I don't know enough coding to understand that. It never actually opens though, just tries to.
Posted on 9/8/20 at 12:52 pm to Brosef Stalin
The software, bluescreenview, displays it in a more user friendly way. I would suggest just using that freeware.
Page 1 of 1
Popular
Back to top
Follow TigerDroppings for LSU Football News