Clevo P170EM Laptop - BSOD when put to sleep?

C

Casey J. Burk

Hi, everyone. I'm trying to figure out why my Clevo P170EM laptop crashes with a BSOD when being put into sleep mode. My initial instinct is that it has something to do with my display drivers but before I get into that, let me give you some system information that can be helpful in tracking this problem down:


System Type:

Clevo P170EM Laptop


Operating System Info:
Windows 7 Professional, Service Pack 1 (64-bit)


Hardware Info:

  • i7-3720QM Processor @ 2.6GHz (8 CPUs)
  • 32GB RAM
  • Intel HD Graphics 4000 (The standard adapter.)
  • AMD Radeon HD 7970M (My gaming display.)


Software Info:


  • Crimson ReLive 17.6.2
  • DirectX 11 / DxDiag 6.01.7601
  • Minecraft consistently shows ~30FPS (more often, it's lower than this) and this is indicative of having some bad drivers despite the system showing no errors that would indicate any issues with the drivers themselves (besides the error output obtained from the BSOD).


Primary Problem:
The low frame rates aside, the laptop is consistenly undergoind a BSOD crash when being placed into sleep mode (i.e. - when I close the laptop lid). Using the "BlueScreenView" app from NirSoft (Blue screen of death (STOP error) information in dump files.), these crashes consistently indicate ntoskrnl.exe as being responsible for the crashes but often show dxgmms1.sys as being another problematic item, too (meaning, it sometimes is listed in the pink highlighting that BlueScreenView applies to entries that appear to be involve in the BSOD dumps).


Last BSOD Dump Details (obtained from BlueScreenView):

  • 093019-42323-01.dmp
  • 9/30/2019 1:01:08 AM
  • SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
  • 0x1000007e
  • ffffffff`c0000005
  • fffff800`02c84088
  • fffff880`03562ef8
  • fffff880`03562760
  • ntoskrnl.exe
  • ntoskrnl.exe+80088
  • NT Kernel & System
  • Microsoft® Windows® Operating System
  • Microsoft Corporation
  • 6.1.7601.23807 (win7sp1_ldr.170512-0600)
  • x64
  • ntoskrnl.exe+80088
  • C:\Windows\Minidump\093019-42323-01.dmp
  • 8
  • 15
  • 7601
  • 280,584
  • 9/30/2019 7:34:00 AM


As I type this, I have the following "important updates" from Microsoft that I can download and install:
- 2019-03 Security Update for Windows 7 for x64-based Systems (KB4474419)
- 2019-09 Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 7 and Server 2008 R2 for x64 (KB4514602)
- 2019-09 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4516065)
- 2019-09 Security Update for Windows 7 for x64-based Systems (KB4474419)
- Windows Maclicious Software Removal Tool x64 - August 2019 (KB890830)

I also have the following "optional updates" that I can download and install:
- 2019-09 Preview of Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4516048)
- 2019-09 Preview of Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 7 and Server 2008 R2 for x64 (KB4516551)
- Intel - System - 4/12/2017 12:00:00 AM - 14.28.47.630
- Microsoft .NET Framework 4.8 for Windows 7 for x64 (KB4503548)
- Western Digital Technologies - WDC_SAM - 11/30/2017 12:00:00 AM - 1.2.0.0

One thing of interest to me is the Intel entry I see in the optional updates for 14.28.47.630. Nothing explains what it's used for and since my Intel Driver & Support Assistant interface indicates that everything is up-to-date, it makes me apprehensive of installing it. Thoughts?



Updating video drivers for this laptop has always been a pain and I'm scared to go down that path before updating everything with Windows first. I've found that updating display drivers is easier to deal with as long as Windows has been completely updated, so I'm not even going to consider doing it until I've installed every necessary update available. I haven't updated Windows in awhile but not-so-ironically, these BSOD crashes seemed to become consistent after updating my Intel display driver a few weeks ago. (The BSODs happened before then but were less consistent / sporadic.)

Any ideas what might be causing these BSODs or ways in which I can troubleshoot them? I'm a little scared of using "verifier" because I've never used it before and I've read how it can "brick" your system but if I need to run it to figure out where the problem is, I will. I'm also about to scan the disk upon reboot to reclaim any lost / bad sectors, etc.--a standard thing I try to do when trying to solve problems. Once I get that done, I'll probably try to update Windows unless any of you have any other suggestions. I could use some insight here.

Continue reading...
 

Similar threads

M
Replies
0
Views
360
Marcin Cichoń
M
M
Replies
0
Views
106
Marcin Cichoń
M
Back
Top Bottom