Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Previous BSOD's constant, now less often - Crash but no BSOD


  • Please log in to reply
6 replies to this topic

#1 ScottsXJ

ScottsXJ

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:06:08 AM

Posted 28 November 2017 - 10:31 PM

I have been experiencing this issue for a little over a year. Ever since I performed the update to Windows 10.
 
I have ton lots of troubleshooting. From complete re-installation of Windows. Reset of Windows. Swapped out the HDD, and added more memory.
 
Prior to the most recent clean installation of Windows, I would experience the crashes quite often. More specifically they would happen on boot. I would hardly ever get to the login screen. When I would, they sometimes would produce a BSOD and would always indicate the Watchdog timer.
 
After the recent clean installation of Windows, the crashes occur far less often. Usually once every few days. It's a complete system lock up and after several minutes the machine will restart itself or I can power it down manually.
 
I have attached the requested logs and specs below.
 
Thanks for any and all assistance!
 
Speccy:
 
HP Notebook - 15-ac151dx
http://speccy.piriform.com/results/maV2hLD2JBQmcHHqJIHNYCL

Edited by ScottsXJ, 28 November 2017 - 10:49 PM.


BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,089 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:10:08 AM

Posted 29 November 2017 - 08:54 AM

This sounds like a hardware problem to me.

 

Have you monitored your temps?  If not, try one of these free tools:

SpeedFan:  http://www.almico.com/sfdownload.php
HWMonitor:  https://www.cpuid.com/softwares/hwmonitor.html
HWInfo:  https://www.hwinfo.com/download.php

 

Blow the vents out with canned air (DO NOT USE a vacuum or an air compressor - they can physically damage the system)

Ensure that the sides and back of the system are not blocked and that they have good airflow.
If possible, also try a cooling pad to ensure that lot's of cooler air is supplied to the system.

Start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

If ALL of those pass, then try this procedure to isolate the problem device(s):  http://www.carrona.org/strpdown.html

FYI - the last link was designed for desktop systems.  It'll work on laptops, but there's just not much that you can do on a laptop - as most components are soldered to the motherboard (and replacing the motherboard on a laptop is a big job!).

 

If you'd like us to look at your reports (for a more detailed analysis), Please do the following:
- open Event Viewer (run eventvwr.msc from the "Run" dialog)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on the "Administrative Events" heading
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

FYI - If we're looking for Event ID 41 errors (unexplained shutdowns), there's more info on that here:  http://support.microsoft.com/kb/2028504
The Event ID 41 error is simply Windows saying that it doesn't know why it shutdown.
 


Edited by usasma, 29 November 2017 - 08:55 AM.

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 ScottsXJ

ScottsXJ
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:06:08 AM

Posted 29 November 2017 - 09:22 AM

Thanks for the reply!

I think you may be correct with the hardware issue. Specifically on the point on monitoring the temperature. I had rub across a BSOD and immediately after reset I ran the BSOD tool again.

I noticed that my laptops fans really seem to Rev up during so. After reading your post I ran the tool again but this time monitored it with coretemp.

I'm not sure how accurate the "max" temp section was; but in a matter of seconds of rubbing it again it reached the max and DPC watchdogged again.

I will have to investigate further. But I will also upload the event viewer logs later today. My original thought was that this may be driver related but now I feel like it could be more of a heatsink issue.

EDIT: Upon further investigation I found that I messed with the fan settings in the Bios while searching for any sort of speed step settings. Which resulted in the higher Temps. They seem to be at normal Temps now.

Edited by ScottsXJ, 29 November 2017 - 10:45 PM.


#4 ScottsXJ

ScottsXJ
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:06:08 AM

Posted 29 November 2017 - 09:50 PM

I am performing the hardware diagnosis tests next.

EDIT: I performed the memory, and CPU stress tests. Both passed with no errors. The HDD is only a few months old and the issues happened before and after replacing the HDD.

I almost feel like the next logical step is the motherboard if this is not software.
 
Here is the event viewer logs.

Attached Files


Edited by ScottsXJ, 29 November 2017 - 10:43 PM.


#5 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,089 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:10:08 AM

Posted 30 November 2017 - 07:04 AM

I saw 3 things that I thought were significant in the Admin logfile:
- processor firmware errors - look for an update to your BIOS/UEFI

- HAL events - the watchdog reports issues just before the Event ID 41 (unexpected reboot).

- Fast startup error - I suggest disabling Fast Startup

 

For the HAL errors, we may be able to get more info from the Sysnative BSOD reports:

Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum)   http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR, .7z or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.

 

 

Beyond that, keep up with the hardware diagnostics.  Diagnosing a motherboard problem is takes a long time and isn't real easy.  Good luck!
 


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#6 ScottsXJ

ScottsXJ
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:06:08 AM

Posted 30 November 2017 - 11:41 PM

So as of now, the lock up have occurred much more often. They are displaying a BSOD WATCHDOG Violation screen consistently.

I'm curious as they had become some less frequent and the only change as of late has been using the diagnostic tools and me applying a Windows Feature update.

Upon crash, it attempts to restart but it locks on boot consistently. This happens almost every time and if I'm lucky I can make it to the login screen before it locks.

As well, I am unable to even boot into Safe Mode as when I get to recovery options it still locks up.

Per your mention of checking the BIOS/UEFI I have already applied the most recent update.

As of now I'm stuck with only able to boot from USB to run the diagnostic tools which come back clear.

Unsure of what to check next.

#7 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,089 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:10:08 AM

Posted 01 December 2017 - 07:33 AM

Most often this is a hardware problem - although it can be software related also.

 

I suggest finishing the hardware diagnostics ( http://www.carrona.org/hwdiag.html ) if you're able.

If they all pass, or if you're not able to finish them - then I'd suggest the stripdown procedure ( http://www.carrona.org/strpdown.html )

As an alternative, you can try a clean install:

 

A clean install is:
- Windows is installed to a freshly partitioned hard drive with legitimate installation media (W10:  https://www.microsoft.com/en-us/software-download/windows10 ).
- The installation media is only a copy of Windows, not the OEM recovery disks that you can make on some systems.
- Windows is fully updated after it's installed.  That's ALL updates - none excepted.
- NO 3rd party software is installed.
- There are no errors in Device Manager (if you find any, post back for suggestions).

This will wipe everything off of the computer, so it's advisable to backup your stuff first.
Also, it will wipe out all the special software that the OEM added to the system, so if you rely on any of that - let us know what it is so we can figure out a way to save/download it (the easiest way is to create/obtain the OEM;s recovery media)

If unable to find recovery media that has the software (or if you suspect that this is a hardware problem), you can make an image of your system that'll preserve everything in the state that it was in when you made the image.  You can also do this if you don't want to try another hard drive - yet you want to be able to return to the current system state.
One drawback to this is that you're making an image of a malfunctioning system - so, if there are errors in the system software, you'll have a nice copy of them :(
Another drawback is that the image of the system will be very large - so you'll most likely need a large external drive to store it on.
But, this will allow you to save everything on the hard drive (although you'll need an image viewer to get things out of the image).
The point here is that, if it's a hardware problem, then you can restore the system to the point it was when you made the image - after you repair the hardware problem.
You can obtain more info on imaging in the Backup/Imaging/DiskMgmt forums located here:  http://www.bleepingcomputer.com/forums/f/238/backup-imaging-and-disk-management-software/

The point of doing this (the clean install) is to:
- rule out Windows as a problem (if the problem continues, it's not a Windows problem as you completely replaced Windows
- rule out 3rd party software (if the problem continues, it's not a 3rd party software problem as you didn't install any 3rd party software)
- so, if the problem continues, it must be a hardware problem.

OTOH, if the problem stops, then it was either a Windows or 3rd party software problem.  If the problem doesn't come back, then you've fixed it.  Then all that remains is setting the computer back up the way that you'd like it and importing your data from the backup you made.


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users