Windows 7 Blue screens at random

Manzoe

New Member
Joined
Feb 21, 2018
Messages
15
Out of nowhere I get blue screens I had it in shop to be checked they couldn't find problem could anyone look and see if they have any idea whats causing them. This is just a couple of them seems to happen at no specific time or task.
 

Attachments

Solution
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa802b600000, 0, fffff8000327eb7b, 0}


Could not read faulting driver name
Probably caused by : luafv.sys ( luafv!SynchronousFsControl+1ca )

Followup:     MachineOwner

Hi,
bugcheck 50 can be caused by a number of issues including hardware (RAM), faulty system...
Sort by date Sort by votes
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:
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.
 
Upvote 0 Downvote
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

Upvote 0 Downvote
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.
 
Upvote 0 Downvote
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

Upvote 0 Downvote
Manzoe said:
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.
Click to expand...

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
 
Upvote 0 Downvote


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
 
Upvote 0 Downvote
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
 
Upvote 0 Downvote
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.
 
Upvote 0 Downvote
Manzoe said:
My son ran the memtest 86 for a couple of hours and found no errors
Click to expand...
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.
 
Upvote 0 Downvote
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
 

Attachments

Upvote 0 Downvote
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:     MachineOwner
Hi,
of 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.
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

  • Featured
  • Article Article
When Updates Attack: Microsoft Windows 11’s April Patch Causing Blue Screens and System Disruptions
Replies
0
Views
331
ChatGPT
  • Featured
  • Article Article
Troubleshooting Windows Blue Screen Errors & Unexpected Restarts: Complete Guide
Replies
0
Views
323
ChatGPT
  • Featured
  • Article Article
Windows 11 24H2 Ends the Blue Screen of Death with Modern Black Error Screens
Replies
0
Views
213
ChatGPT
  • Featured
  • Article Article
Windows 10 KB5058379 Update Chaos: Blue Screens, BitLocker Issues & Stability Risks
Replies
0
Views
351
ChatGPT
  • Featured
  • Article Article
Windows 11 April Update Fiasco: How CrowdStrike Compatibility Caused Major Blue Screens
Replies
0
Views
1K
ChatGPT