📎 AI Summary:
The thread discusses a user experiencing recurring blue screens on their Windows PC, with troubleshooting suggestions including driver issues, system scans, and hardware checks. A contributor identifies the bug check 50 as potentially caused by outdated antivirus software, prompting the user to update or reinstall it and run system scans. Later, a second blue screen points to a problematic network driver (athrx.sys), with advice to update or replace the driver to resolve the issue, reflecting ongoing efforts to address the root causes of the crashes.
The thread discusses a user experiencing recurring blue screens on their Windows PC, with troubleshooting suggestions including driver issues, system scans, and hardware checks. A contributor identifies the bug check 50 as potentially caused by outdated antivirus software, prompting the user to update or reinstall it and run system scans. Later, a second blue screen points to a problematic network driver (athrx.sys), with advice to update or replace the driver to resolve the issue, reflecting ongoing efforts to address the root causes of the crashes.
Solution
kemical
Essential Member
Code:
*******************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41790, fffffa8001d74560, ffff, 0}
Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+8cf )
Followup: MachineOwnerBugcheck 1A means a severe memory management issue occurred which may or may not be failed or failing RAM.
As I already mentioned you either have a corrupt driver or operating system or the ram is starting to or has failed.
I did see that the process at the time of BSOD was dllhost.exe:
Code:
PROCESS_NAME: dllhost.exeThis is a Windows Process which is an umbrella for apps and services within Windows itself. This may indicate that windows is a little corrupted or a driver is causing the issue.
Your drivers could do with updating and checking I see updates available for your chipset (which is ultra important) as well as others.
Update your drivers using only the versions found here:
Link Removed
Edit: Under Intel Rapid storage driver you want the 2014 version.
Under chipset you want both chipset driver and Intel engine management driver. The rest are pretty straight forward as to which version to use.
If it's been a very long time since Windows 7 was installed consider a clean install and start afresh making sure you only use drivers from the support page.
If the bsod continues then you really need to check the RAM as mentioned before.
kemical
Essential Member
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff8000367d5da, fffff8800c313f20, 0}
Probably caused by : ntkrnlmp.exe ( nt!AlpcpReceiveMessagePort+aa )
Followup: MachineOwnerI couldn't see a driver mentioned, have you made any changes recently such installing something new?
Try running the sfc scanner again mentioned earlier in this thread.
kemical
Essential Member
Enable or disable Just-In-Time debugging
- Open Visual Studio. ...
- In the Options dialog box, select the Debugging folder.
- In the Debugging folder, select the Just-In-Time page.
- In the Enable Just-In-Time debugging of these types of code box, select or clear the relevant program types: Managed, Native, or Script. ...
- Click OK
jerryg50
Honorable Member
This link below contains a comprehensive description about the type of Blue Screen you are describing. It is basically indicating damaged operating system files. They go in to system recover from restore points and or recovery from a system image, and etc. Personally, I found when there are damaged files not caused by many improper shut downs there are faults with the hard disk. Hard disk faults can be intermittent. I would change the drive and restore the system from a last known good image backup. Do not make an image backup from the computer if there are faults! You can install a new drive and re-install if you do not have a known good system backup image.
Link Removed
kemical
Essential Member
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {8, 2, 1, fffff80003268a57}
Probably caused by : ntkrnlmp.exe ( nt!KeReleaseSemaphore+137 )
Followup: MachineOwnerwhen you say you've done all the test, does this include testing the RAM too?
Looking back over the dump files posted and the collective bugchecks as a whole could indicate a RAM issue.
Please run Memtest86 as outline in this guide: How to Test PC RAM with MemTest86
kemical
Essential Member
Ideally memtest86 needs to be run overnight like for 8hrs or so.
Also sometimes there are errors that even memtest86 won't pick up and it might be worth running the system on one stick of RAM at a time. If the system still blue screens swap the stick over for another and use the machine again. The idea is that your looking for the stick which doesn't bsod meaning the other/s are faulty.
You could try some basic bug testing.
Personally I would try re-installing the os especially if it's been a long time since it was refreshed. When i mean re-install I mean by the clean install method which wipes the drive clean.
You then add the drivers but nothing else, no third party apps and see if the machine blue screens.
If all seems well slowly start adding apps back, one at a time, checking on blue screens in between each install.
Manzoe
New Member
Been awhile since I had a blue screen and now I had 3 within short time. Everything you recommended was done and seemed computer was running well until this past week. Do you have anymore suggestions now for this problem? Thanks for all your help
kemical
Essential Member
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, 109b, 509031e, fffff8a00fafdd60}
GetPointerFromAddress: unable to read from fffff800034b7100
Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800034b72e8
GetUlongPtrFromAddress: unable to read from fffff800034b74a0
GetPointerFromAddress: unable to read from fffff800034b70d8
GetPointerFromAddress: unable to read from fffff800034b7100
Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800034b72e8
GetUlongPtrFromAddress: unable to read from fffff800034b74a0
Probably caused by : ntkrnlmp.exe ( nt!AlpcpCommunicationInfoDestroyProcedure+115 )
Followup: MachineOwnerof the three dump files sent, two are like the above.
Usually the above is caused by a driver although which driver is unknown.
Have you recently made any changes, either driver, application or hardware?
One way to determine the offending driver is to run whats called the driver verifier:
Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista
Post any new dump files.
