Blue screens at random

kemical

Windows Forum Admin
Staff member
Premium Supporter
#21
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:     MachineOwner
Hi,
Bugcheck 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.exe
This 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:
Support For GT70 2OC | Laptops - The best gaming laptop provider | MSI Global

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.
 


#22
Been 13 days so its getting better. Your suggestions helped next week I will be able to check the memory. Any suggestions with this one.
 


Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
#23
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:     MachineOwner
Hi,
I 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.
 


Manzoe

New Member
#24
Hi Kemical, This is not a blue screen but I was hoping you could tell me what this is and how to fix, it only comes up when I log on.
 


Attachments

kemical

Windows Forum Admin
Staff member
Premium Supporter
#25
Hi Kemical, This is not a blue screen but I was hoping you could tell me what this is and how to fix, it only comes up when I log on.
Enable or disable Just-In-Time debugging
  1. Open Visual Studio. ...
  2. In the Options dialog box, select the Debugging folder.
  3. In the Debugging folder, select the Just-In-Time page.
  4. In the Enable Just-In-Time debugging of these types of code box, select or clear the relevant program types: Managed, Native, or Script. ...
  5. Click OK
 


jerryg50

Honorable Member
#26
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80003333f73, fffff880037b5eb8, fffff880037b5720}

*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+c2fe )

Followup:     MachineOwner
Hi,
the above probable cause relates to your network driver:
athrx.sys Tue May 5 08:30:13 2015: Atheros network adapter driver
I checked your support page but there isn't a later driver. You could try simply removing the current version and installing a fresh copy.
Your support page is here:
Support For GT70 2OC | MSI Global

Please post any new dump files.

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.

How To Fix 1000007e Error?
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
#28
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:     MachineOwner
Hi,
when 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
 


#29
My son ran the memtest 86 for a couple of hours and found no errors, it made a couple of passes. I don't have visual studio on this computer so couldn't do anything with that.
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
#30
My son ran the memtest 86 for a couple of hours and found no errors
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.
 


kemical

Windows Forum Admin
Staff member
Premium Supporter
#32
Helpful if not a tad generic..
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.
Top