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

Periodic BSOD 0x7E During Bootup


  • Please log in to reply
24 replies to this topic

#1 donfrankrice

donfrankrice

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:07:58 PM

Posted 12 May 2015 - 12:42 PM

A couple of months ago, I installed approximately 50 Lenovo ThinkCentre 10B6 desktops running Win7 Pro x64 into our offices.  They were all imaged from a known-good image.  After a few weeks, a small number have started experiencing the 0x7E BSOD during bootup.  The error flashes long enough to prepare the dump file, and then automatically reboots, only to crash again.  I can boot the station into Safe Mode without issue, and then when I reboot the system comes up normally.  All is well for a couple of days, and then the problem returns.
 
I have seen some reports of the 0x7E being caused by USB video devices, but these desktop stations do not have any video source other than onboard video.  USB devices include the usual mouse and keyboard, and some also have a Star Micronics receipt printer and Honeywell barcode scanner. 
 
I have seen other reports suggest that Avast Antivirus could be to blame, but that is not installed on these stations.
 
I have also come across two pages on the Microsoft Support site that talk about this stop error (https://support.microsoft.com/en-us/kb/2528614 and https://support.microsoft.com/en-us/kb/979538).  Each has a hotfix available for download, but the filenames are different and I do not know which one to apply.
 
I have one such station just down the hall, so I can grab any necessary files fairly easily.
 
Thanks in advance for the assist!
 
Don

BC AdBot (Login to Remove)

 


#2 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,052 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:07:58 PM

Posted 12 May 2015 - 01:43 PM

Hi -

Bugcheck 0x7e = thread threw an exception.  The exception error code is in P1 (1st number of the 4 inside the parenthesis after 0x7e).  Usually, it is 0xc5 - memory access violation.

 

If the BSODs are software related, a 3rd party driver will likely be at fault and MAY be named on the blue screen and listed in the dump files.

 

Dumps + system files would be helpful.  Please follow these instructions -

 

http://www.sysnative.com/forums/bsod-crashes-kernel-debugging/68-blue-screen-of-death-bsod-posting-instructions-windows-10-8-1-8-7-vista.html

 

Upload the resulting zip file(s) to OneDrive or other host and provide a link in your next post.

 

https://onedrive.live.com/

 

It is best that we work with just one system even though others have the same BSODs.

 

Regards. . .

 

jcgriff2


Microsoft MVP 2009-2015

#3 donfrankrice

donfrankrice
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:07:58 PM

Posted 12 May 2015 - 02:36 PM

Here is the Perfmon report

 

Here is the SysnativeFileCollectionApp folder

 

In answer to the questions in step 5 of the Sysnative post:

 

OS - Win7 Pro SP1 x64 - original OS, purchased with the machine, and was placed as an image when unboxing the station

 

Age - 8 months

 

Image placed 2 months ago

 

CPU - Core i5-4570

 

Video Card - Intel® HD Graphics 4600

 

System Manufacturer - Lenovo ThinkCentre M73 10B60008US

 

Desktop PC

 

This is not asked for, but the station is running Trend Micro version 11.


Edited by donfrankrice, 12 May 2015 - 02:38 PM.


#4 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,052 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:07:58 PM

Posted 12 May 2015 - 08:30 PM

Hi. . .
 
Thank you for the files.
 
4 of the 5 dumps did have bugcheck 0x7e - thread threw an exception
1 had bugcheck 0x3b - system service threw an exception
 
All 5 had exception error code - 0xc0000420 - assertion failure
 
Executing an ".exr" (Display Exception Record) Windbg KD command on the exception record tells us the assertion = "concurrent BIOS calls" 

3: kd> .exr 0xfffff880033d9478
ExceptionAddress: fffff800038032da (hal!x86BiosCall+0x0000000000000022)
   ExceptionCode: c0000420 (Assertion failure)
  ExceptionFlags: 00000000
NumberParameters: 0
Assertion: *** Concurrent BIOS calls

Assertions are typically used by driver developers during driver development (coding) for debugging purposes and should be removed prior to the final release.  Assertions can be found in Windows, but only in "checked" builds. 
 
Since we are dealing with dozens (or more..?) of new systems and only a few are blue-screening, I believe the problem here is likely a poorly written 3rd party driver or a 3rd party beta driver.  I do not believe that a Microsoft driver is to blame.
 
The assertion message  "concurrent BIOS calls" does indicate it is coming from a driver and not the BIOS; however, looking up your system led me to a driver update page containing BIOS updates.
 
Your current BIOS info: 

       System Model: 
10B60008US               
BIOS: LENOVO BIOS Rev: FCKT57A 0.0

 
Driver updates - http://support.lenovo.com/us/en/products/desktops-and-all-in-ones/thinkcentre-m-series-desktops/thinkcentre-m73
 
BIOS update - http://support.lenovo.com/us/en/products/desktops-and-all-in-ones/thinkcentre-m-series-desktops/thinkcentre-m73/downloads/DS038324
 
Again -- system info needs to be confirmed to assure that those drivers + BIOS are in fact for your system. 
 
As for the BSODs + assertion... assuming my assumptions are correct, we're looking for a 3rd party driver. The only driver mentioned in the dumps is the Microsoft legacy video driver vga.sys - so it is possible the driver we're looking for is related to video. 
 
http://www.sysnative.com/drivers/driver.php?id=vga.sys
 
vga.sys is not the problem here.  It appeared on the stack and may have been there calling another driver.
 
DirectX Kernel Diagnostics reports you are running on-board Intel 4600 video.  This should be the driver for video:

igdkmd64.sys Mon Jun 24 11:44:47 2013 (51C8696F)

http://www.sysnative.com/drivers/driver.php?id=igdkmd64.sys
 
I don't see any driver updates at Lenovo for video.
 
Driver Verifier may help us here.  Run it and see if it flags any 3rd party drivers - http://www.sysnative.com/forums/bsod-crashes-kernel-debugging/29-driver-verifier-bsod-related-windows-10-8-1-8-7-vista.html
 
Let it run for at least 24 hours.  If Driver Verifier detects a driver violation, it will force a BSOD and provide additional information in the dump.
 
Regards. . .
 
jcgriff2


Windbg Dump Log File

Spoiler


Edited by jcgriff2, 12 May 2015 - 08:35 PM.

Microsoft MVP 2009-2015

#5 donfrankrice

donfrankrice
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:07:58 PM

Posted 14 May 2015 - 07:28 AM

I just started up verifier.  I have left a note on the station, asking staff members to leave it running tonight so that I can get a full 24 hours in.



#6 donfrankrice

donfrankrice
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:07:58 PM

Posted 15 May 2015 - 08:00 AM

Here are the results of the verifier /query that I ran on this station after 24 hours had passed without BSOD:

 

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation.  All rights reserved.

C:\Users\staff>verifier /query
5/15/2015, 8:38:59 AM
Level: 0000092B
RaiseIrqls: 0
AcquireSpinLocks: 17645299
SynchronizeExecutions: 1038280
AllocationsAttempted: 49697766
AllocationsSucceeded: 49697766
AllocationsSucceededSpecialPool: 49697766
AllocationsWithNoTag: 28
AllocationsFailed: 0
AllocationsFailedDeliberately: 0
Trims: 42778555
UnTrackedPool: 1

Verified drivers:

Name: iusb3hcs.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Name: iastora.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Name: amdxata.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Name: fastboot.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 1
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 4112

Name: iastorf.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 3
PeakNonPagedPoolAllocations: 4
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 296
PeakNonPagedPoolUsageInBytes: 272

Name: tmcomm.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 4
CurrentNonPagedPoolAllocations: 38
PeakPagedPoolAllocations: 7
PeakNonPagedPoolAllocations: 39
PagedPoolUsageInBytes: 151596
NonPagedPoolUsageInBytes: 169696
PeakPagedPoolUsageInBytes: 606252
PeakNonPagedPoolUsageInBytes: 169852

Name: tmtdi.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 1926
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 2038
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 1065256
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 1082908

Name: igdkmd64.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 15
CurrentNonPagedPoolAllocations: 659
PeakPagedPoolAllocations: 16
PeakNonPagedPoolAllocations: 1067
PagedPoolUsageInBytes: 2638128
NonPagedPoolUsageInBytes: 2925456
PeakPagedPoolUsageInBytes: 2638228
PeakNonPagedPoolUsageInBytes: 3176160

Name: iusb3xhc.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 4
CurrentNonPagedPoolAllocations: 393
PeakPagedPoolAllocations: 5
PeakNonPagedPoolAllocations: 397
PagedPoolUsageInBytes: 484
NonPagedPoolUsageInBytes: 658120
PeakPagedPoolUsageInBytes: 528
PeakNonPagedPoolUsageInBytes: 708452

Name: hecix64.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 1
CurrentNonPagedPoolAllocations: 2
PeakPagedPoolAllocations: 1
PeakNonPagedPoolAllocations: 5
PagedPoolUsageInBytes: 112
NonPagedPoolUsageInBytes: 264
PeakPagedPoolUsageInBytes: 112
PeakNonPagedPoolUsageInBytes: 776

Name: rt64win7.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 4105
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 4105
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 613420
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 613420

Name: ndis.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 6
CurrentNonPagedPoolAllocations: 8796
PeakPagedPoolAllocations: 8
PeakNonPagedPoolAllocations: 8832
PagedPoolUsageInBytes: 984
NonPagedPoolUsageInBytes: 2606380
PeakPagedPoolUsageInBytes: 1156
PeakNonPagedPoolUsageInBytes: 2624492

Name: psadd.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 1
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 132
PeakNonPagedPoolUsageInBytes: 0

Name: intcdaud.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 69
PeakPagedPoolAllocations: 3
PeakNonPagedPoolAllocations: 72
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 38304
PeakPagedPoolUsageInBytes: 560
PeakNonPagedPoolUsageInBytes: 38456

Name: iusb3hub.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 3
CurrentNonPagedPoolAllocations: 29
PeakPagedPoolAllocations: 9
PeakNonPagedPoolAllocations: 31
PagedPoolUsageInBytes: 8340
NonPagedPoolUsageInBytes: 4420
PeakPagedPoolUsageInBytes: 12592
PeakNonPagedPoolUsageInBytes: 4892

Name: rtkvhd64.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 820
PeakPagedPoolAllocations: 2
PeakNonPagedPoolAllocations: 822
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 671396
PeakPagedPoolUsageInBytes: 438272
PeakNonPagedPoolUsageInBytes: 672396

Name: tmpreflt.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 3
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 240

Name: vsapint.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 7500
CurrentNonPagedPoolAllocations: 5
PeakPagedPoolAllocations: 7742
PeakNonPagedPoolAllocations: 25
PagedPoolUsageInBytes: 42148384
NonPagedPoolUsageInBytes: 16944
PeakPagedPoolUsageInBytes: 50447496
PeakNonPagedPoolUsageInBytes: 19664

Name: tmxpflt.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 7475
CurrentNonPagedPoolAllocations: 78
PeakPagedPoolAllocations: 9030
PeakNonPagedPoolAllocations: 82
PagedPoolUsageInBytes: 2605064
NonPagedPoolUsageInBytes: 308664
PeakPagedPoolUsageInBytes: 3672128
PeakNonPagedPoolUsageInBytes: 317688

Name: tmevtmgr.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 5
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 14
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 80
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 2092

Name: tmactmon.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 6
PeakPagedPoolAllocations: 5
PeakNonPagedPoolAllocations: 6
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 96
PeakPagedPoolUsageInBytes: 10240
PeakNonPagedPoolUsageInBytes: 96

Name: secdrv.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 1
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 3
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 72
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 316
PeakNonPagedPoolUsageInBytes: 0

Name: tmnciesc.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 1497
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 2311
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 5026164
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 8554588

Name: tmeevw.sys, loads: 1, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 73
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 139
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 23992
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 46492

Name: dump_diskdump.sys, loads: 0, unloads: 0
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Name: dump_iastora.sys, loads: 2, unloads: 1
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 0
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 0
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 0
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 0

Name: dump_dumpfve.sys, loads: 2, unloads: 1
CurrentPagedPoolAllocations: 0
CurrentNonPagedPoolAllocations: 1
PeakPagedPoolAllocations: 0
PeakNonPagedPoolAllocations: 1
PagedPoolUsageInBytes: 0
NonPagedPoolUsageInBytes: 16400
PeakPagedPoolUsageInBytes: 0
PeakNonPagedPoolUsageInBytes: 16400

C:\Users\staff>







 



#7 donfrankrice

donfrankrice
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:07:58 PM

Posted 15 May 2015 - 10:32 AM

I've pulled down the latest BIOS (dated 5/5/15), and hope to install it later today.  As for video, Lenovo has a download for the Intel Haswell Onboard VGA Driver, which should be the same as the HD 4600.  Even so, I've pulled down the Intel Driver Update Utility and will have it scan for updates.



#8 donfrankrice

donfrankrice
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:07:58 PM

Posted 15 May 2015 - 12:53 PM

OK, BIOS is flashed, and the Intel Driver Update Utility found an updated video driver that was released a month ago.  Crossing fingers...



#9 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,052 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:07:58 PM

Posted 15 May 2015 - 11:33 PM

But no BSOD yet...

Is driver verifier still running?

If at 48 hours or more, turn it off for now.

From CMD type/paste: verifier /reset

 

This is perplexing!


Microsoft MVP 2009-2015

#10 donfrankrice

donfrankrice
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:07:58 PM

Posted 16 May 2015 - 06:33 PM

I reset it after 24 hours. No BSOD has been reported so far. If it b is going to do it, it should be by Monday or Tuesday.

#11 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,052 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:07:58 PM

Posted 17 May 2015 - 12:13 AM

I spoke with some hardware experts at lunch today and they took an interest in the BIOS update & also said the "concurrent BIOS calls" message could be related to Lenovo software that interacts with or probes the BIOS & motherboard for system information. 

 

They likened it to Asus' ATK0110 mobo utility driver ASACPI.sys - http://www.sysnative.com/drivers/driver.php?id=ASACPI.sys

 

They said the system image may be the issue here because of different version motherboards & that the Lenovo software may need to be reinstalled to allow the different boards (versions) & BIOS to properly communicate with the Lenovo software + Windows.

 

I hope I wrote that the way they conveyed it to me!

 

Does any of that make sense to you?  I am not a hardware expert -- I sit on the software side of the fence.


Microsoft MVP 2009-2015

#12 donfrankrice

donfrankrice
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:07:58 PM

Posted 18 May 2015 - 09:43 AM

I am not a hardware expert either.  I cannot 100% rule out the image, though neither can I say it is the problem.  The image was created from one of the 10B6 stations that I unboxed - I just turned it on, configured it the way I wanted it, and then imaged it and then deployed that image to the remaining 10B6 stations.  My understanding of the imaging process is that as long as the model PC is the same then the image can be deployed to it without issue.  These are all the same model station, and their serial numbers are all starting with the same prefix, which suggests belonging to the same batch.  As such, the boards should be the same, right?

 

In any event, which Lenovo software are your hardware guys referring to as possibly needing to be reinstalled?  Is it the Lenovo Solutions Suite or is it just the drivers that would need to be reloaded - chipset, BIOS, video, etc.?



#13 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,052 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:07:58 PM

Posted 18 May 2015 - 08:10 PM

I sent a request to them with a link to the Lenovo driver site seeking additional info.
 
My guess would be chipset drivers.
 
BTW - any more BSODs on existing systems (ones that BSOD'd before)?
 
Any new ones blue-screening?

EDIT:
 

As such, the boards should be the same, right?


I had the same question during our lunch. They replied that yes, the boards are the same, but the revision numbers may differ & that the only way to know if the revision number was different was to physically look at the numbers printed on the board.

One guy explained that today's newer boards communicate more directly (or perhaps "differently"...?) with the BIOS; that each revised board may do so slightly differently and that the info from the board is retained (somewhere in Windows/ Lenovo software).

I do recall them explaining to me that the image was created using "revision number X" board (like 001); you are deploying the image (created on "version 001" board - for example) on systems with "version 002", "version 003" boards, which may be just different enough from "version 001" board to cause a problem.

They all were in agreement that if available, the BIOS update should be applied.

Edited by jcgriff2, 18 May 2015 - 08:23 PM.

Microsoft MVP 2009-2015

#14 donfrankrice

donfrankrice
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:07:58 PM

Posted 19 May 2015 - 08:38 AM

So far things seem OK.  I sent instructions out to our facilities on Friday to let people know how they can get the station back up and running should it encounter this problem.  Sometimes that means that staff will stop reporting issues that they know they can correct, so I have been asking around here this morning.  Nothing appears to have experienced a BSOD over the weekend or yesterday.  The one that I updated the BIOS and video drivers on has been working well.



#15 Wrench97

Wrench97

  • BSOD Kernel Dump Expert
  • 7 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:S.E. Pennsylvania
  • Local time:07:58 PM

Posted 19 May 2015 - 12:33 PM

Hi donfrankrice what we were reffering to was the utilities software or troubleshooting programs from Lenovo they interact with the bios to get the sensor values for temps and voltages, cpu states or even simply uptime for example. If/when the program is installed it can set configurations for the motherboard bios version installed as well as the motherboard version slight version changes may just be the brand or model of a sersor chip, if you have the utility set for one version then deploy it on another it can reek havoc.

It's been a long time since did any Lenovos but utilities like  Lenovo Application Interface ,   Lenovo Solution Center for Windows, or Message Center Plus for Windows could be the culprits.

 

Do these machines have TPM's in them?






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users