Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8012540e628, ffffd00047926368, ffffd00047925b80}
Probably caused by : iaLPSS2i_I2C.sys ( iaLPSS2i_I2C+e628 )
Followup: MachineOwner
Hi Maude,
the driver verifier only revealed false positives and if you haven't already please turn it off.
You say here:
Did some de- and reinstalling and for five minutes, I haven't had a crash.
This is a little vague and can you post what you removed and then re-installed please, thanks.
The above dump file is blaming the Intel Serial IO driver and checking the dates you do have a later driver on the support page.
iaLPSS2i_I2C.sys Mon Sep 21 04:08:09 2015: Intel Serial IO I2C host controller driver
Product support I once turned on verifier while I was in safe mode and there were plenty of drivers to choose which are hidden in regular mode. Might one of them be the one to blame?
It's possible I guess but nothing is appearing driver wise in the dump files. Only one driver was mentioned and to be honest that's almost certainly a false positive. The driver was the realtek HD audio driver and you could always install the version off the support page if you so wish.
Try running these scans again:
File scans
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type:
sfc /scannow
press enter and await results
In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).
If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.
So update as above and see how you go. If a bsod does occur please just post the dump file, don't start up the verifier until we've had chance to view the dump files.
Best of luck and post any new dump files.
On a more personal note I have to admit that if I owned the machine I would have already returned it. It's clearly not working as intended and I'm sure when you handed over your hard won money you never envisioned having to do hours of troubleshooting. It's obviously entirely up to you but I'd at least give them a call?