Occasional BSOD - BCCode: 1000007e

Seithes · 24 Jul 2017

I recently had a BSOD which was caused by Avast drivers and managed to solve the issue here:

Daily BSOD - BCCode: 1000007e Solved - Windows 7 Help Forums

It is possible it may be related, but the codes appear to be different and I no longer use Avast so the solution will be different.

I've had this BSOD three times so far, two of them occurring today.

BSOD

13/7/17 13.30pm

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFF80000003
BCP2: FFFFF80002E76C50
BCP3: FFFFF88003307BE8
BCP4: FFFFF88003307450
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

BSOD 2

24/7/17 12.16pm

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFF80000003
BCP2: FFFFF80002E74C50
BCP3: FFFFF88003315BE8
BCP4: FFFFF88003315450
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

BSOD 3

24/7/17 13.32pm

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFF80000003
BCP2: FFFFF80002EC4C50
BCP3: FFFFF880031FBBE8
BCP4: FFFFF880031FB450
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Hope you guys can help me out with this, as previously; I suspect the USB's unreliable connections to be part of the problem and was using Android Studio during both instances.

Thanks,

- Seithes

**axe0** · 24 Jul 2017

Diagnostic Test

DRIVER VERIFIER

Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

Seithes · 25 Jul 2017

Hi Axe0,

I've taken a full backup and started the verification process. I won't be able to keep an eye on it as it is an office computer, but hopefully there is some kind of log for me to check tomorrow to see if anything did happen. So far it's only messing with my music lol but I'll let you know how it goes.

Thanks for the help again,

- Seithes

Layback Bear · 25 Jul 2017

As you posted, this is a office computer. Have you contacted the I.T. department at work for help?

From post #3

I've taken a full backup and started the verification process. I won't be able to keep an eye on it as it is an office computer

So far it's only messing with my music lol but I'll let you know how it goes.

I'm not understanding the above for a 'office computer'.

Jack

Seithes · 25 Jul 2017

Not particularly relevant to the issue, just mentioning that I would not be near the computer for several hours when I finish up for the day. Also, since we are a very small start up, there isn't an IT department to speak of. I'd be the most qualified in the office to do this kind of thing.

As for the music, I listen to music on Youtube while I work and since my drivers are being stress tested, its partially freezing during playback.

Not entirely sure how I've confused the situation lol but thanks anyways for taking a look at my issue.

Thanks,

- Seithes

Seithes · 27 Jul 2017

The Driver verifier has now been running for a little over 44 hours and so far I haven't had any more bluescreens, although I've only been here to witness about 16 of those hours.

I've ran sysnative again and will attach the report here just in case, but I think this means the drivers are alright.

Any other suggestions I could try, or should I just keep the verifier running for now?

EDIT: Seems I spoke too soon, just caught the laptop booting up and asking if it should start normally. Looks like it bluescreened after all so I'm re-uploading the sysnative report.

EDIT2: And again..

Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFF80000003
BCP2: FFFFF80002E6DC50
BCP3: FFFFF88003307B88
BCP4: FFFFF880033073F0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Thanks,

- Seithes

**axe0** · 27 Jul 2017

Follow these instructions please.
Blue Screen of Death (BSOD) Posting Instructions - Windows 7 Help Forums

Seithes · 27 Jul 2017

File contents seem to be fairly similar, but here ya go. Must have used the wrong exe.

**axe0** · 28 Jul 2017

Its partly similar.

The errors are due to hardcoded breakpoints which should not ever be present on consumer systems, unless there is a tech to perform live debugging.

See if there is a BIOS update available.

Seithes · 31 Jul 2017

Thanks again Axe0,

After checking out the windows update, I found a few optional updates that looked fairly important including a system update from Lenovo. I've just finished installing all the updates so hopefully the issue will be resolved now.

I'll keep the post open for a day to make sure but if I have no issues I'll mark this as solved tomorrow morning.

Thanks again,

- Seithes