Solved Occasional BSOD - BCCode: 1000007e

[Seithes]

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]

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]

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]

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]

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]

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]

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

 

[Seithes]

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

 

[axe0]

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]

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

 

[Seithes]

Unfortunately I had another blue screen today, so it seems those updates did not resolve the issue after all. Seems there's another 3 updates appeared today so I'll try that and see if it'll help any. In the mean time, I've created another report that will hopefully shine more light on the issue.

Thanks,



- Seithes

 

[axe0]

Could you upload a kernel dump to a 3rd party uploader (dropbox, onedrive, google drive) and post a share link please.
The kernel dump is located in C:\Windows\Memory.dmp.

 

[Seithes]

Uploaded the memory.dmp to Google drive,

MEMORY.DMP - Google Drive

I know I've spoke about this before, but are there any mention of USB issues? Many of these blue screens seem to coincide with the USB hub coming loose and disconnecting my phone and keyboard. Keyboard is always plugged in, but I only get the blue screens while phones are plugged in. My assumption is it's disconnecting and reconnecting was causing issues but I guess that could also just be a symptom.

Anyways, just figured i'd mention it.

Thanks,


- Seithes

 

[axe0]

Thanks for the dump.

It appears that the minidump was a little insufficient.
As mentioned, the crash occurs because a breakpoint was reached.
There is also consistently I/O operations in all dumps, I/O operations contain packages so the Windows I/O system knows what to do with it. Unfortunately the minidump was insufficient because it could not display the package information.

2: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff880`031f3c28 fffff800`031e94f4 nt!KeBugCheckEx
01 fffff880`031f3c30 fffff800`031a713d nt!PspUnhandledExceptionInSystemThread+0x24
02 fffff880`031f3c70 fffff800`02ea0444 nt! ?? ::NNGAKEGL::`string'+0x21ac
03 fffff880`031f3ca0 fffff800`02e9febd nt!_C_specific_handler+0x8c
04 fffff880`031f3d10 fffff800`02e9ec95 nt!RtlpExecuteHandlerForException+0xd
05 fffff880`031f3d40 fffff800`02eb01ed nt!RtlDispatchException+0x415
06 fffff880`031f4420 fffff800`02e734ce nt!KiDispatchException+0x17d
07 fffff880`031f4ab0 fffff800`02e712f4 nt!KiExceptionDispatch+0xce
08 fffff880`031f4c90 fffff800`02e6bc51 nt!KiBreakpointTrap+0xf4
09 fffff880`031f4e28 fffff880`00edd790 [COLOR="Red"]nt!DbgBreakPoint+0x1 [/COLOR]// breakpoint
0a fffff880`031f4e30 fffff880`00edb14d Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+0x70
0b fffff880`031f4e70 fffff880`00ee7a6c Wdf01000!FxIoQueue::StopProcessingForPower+0x1ed
0c fffff880`031f4ec0 fffff880`00f502cf Wdf01000!FxPkgIo::StopProcessingForPower+0x22c
0d fffff880`031f4f30 fffff880`00ede0f8 Wdf01000!FxPkgPnp::PowerGotoD3Stopped+0x73
0e fffff880`031f4f90 fffff880`00eddda6 Wdf01000!FxPkgPnp::PowerEnterNewState+0x1d8
0f fffff880`031f50f0 fffff880`00ede627 Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
10 fffff880`031f5160 fffff880`00f5639f Wdf01000!FxPkgPnp::PowerProcessEvent+0x1b3
11 fffff880`031f5200 fffff880`00edaae7 Wdf01000!FxPkgPnp::PowerPolStopping+0x1b
12 fffff880`031f5230 fffff880`00eda5b9 Wdf01000!FxPkgPnp::PowerPolicyEnterNewState+0x1d7
13 fffff880`031f5390 fffff880`00edea01 Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x145
14 fffff880`031f5400 fffff880`00f53c9a Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x1c1
15 fffff880`031f54a0 fffff880`00eefdf5 Wdf01000!FxPkgPnp::PnpEventFailedIoStarting+0xe
16 fffff880`031f54d0 fffff880`00eefac6 Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a1
17 fffff880`031f5570 fffff880`00eef879 Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
18 fffff880`031f55e0 fffff880`00f526bd Wdf01000!FxPkgPnp::PnpProcessEvent+0x18d
19 fffff880`031f5680 fffff880`00eca5d7 Wdf01000!FxPkgFdo::_PnpSurpriseRemoval+0x25
1a fffff880`031f56b0 fffff880`00ec979a Wdf01000!FxPkgPnp::Dispatch+0x18f
1b fffff880`031f5710 fffff880`00ec9866 Wdf01000!FxDevice::Dispatch+0x19a
1c fffff880`031f5750 fffff800`030d9b11 Wdf01000!FxDevice::DispatchWithLock+0xa6
1d fffff880`031f5790 fffff800`03258791 nt!IopSynchronousCall+0xe1
1e fffff880`031f5800 fffff800`03256fb8 nt!IopRemoveDevice+0x101
1f fffff880`031f58c0 fffff800`032582d7 nt!PnpSurpriseRemoveLockedDeviceNode+0x128
20 fffff880`031f5900 fffff800`032583f0 nt!PnpDeleteLockedDeviceNode+0x37
21 fffff880`031f5930 fffff800`032f617f nt!PnpDeleteLockedDeviceNodes+0xa0
22 fffff880`031f59a0 fffff800`032f6d3c nt!PnpProcessQueryRemoveAndEject+0x6cf
23 fffff880`031f5ae0 fffff800`031dfa96 nt!PnpProcessTargetDeviceEvent+0x4c
24 fffff880`031f5b10 fffff800`02e7e195 nt! ?? ::NNGAKEGL::`string'+0x45f4b
25 fffff880`031f5b70 fffff800`0310cf12 nt!ExpWorkerThread+0x111
26 fffff880`031f5c00 fffff800`02e65de6 nt!PspSystemThreadStartup+0x5a
27 fffff880`031f5c40 00000000`00000000 nt!KiStartSystemThread+0x16

Dumping the package shows a driver from HTC misbehaving.

2: kd> !irp fffffa8010c88c60 7
Irp is active with 10 stacks 10 is current (= 0xfffffa8010c88fb8)
 No Mdl: No System Buffer: Thread fffffa800c753660:  Irp stack trace.  
Flags = 00000000
ThreadListEntry.Flink = fffffa800c753a50
ThreadListEntry.Blink = fffffa800c753a50
IoStatus.Status = 00000000
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = fffff880031f57c0
UserEvent = fffff880031f57d0
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000   
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = fffffa8010c88cd8
Tail.Overlay.Thread = fffffa800c753660
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = 00000000
Tail.Overlay.ListEntry.Blink = 00000000
Tail.Overlay.CurrentStackLocation = fffffa8010c88fb8
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_PNP(1b), IRP_MN_SURPRISE_REMOVAL(17)]
            0  1 fffffa80104c39a0 00000000 00000000-00000000    pending
	      [COLOR="red"]*** ERROR: Module load completed but symbols could not be loaded for ANDROIDUSB.sys[/COLOR]
 \Driver\HTCAND64
			Args: 00000000 00000000 00000000 00000000
IO verifier information:
No information available - the verifier is probably disabled

2: kd> lmvm ANDROIDUSB
Browse full module list
start             end                 module name
fffff880`070c7000 fffff880`070d6000   ANDROIDUSB   (no symbols)           
    Loaded symbol image file: ANDROIDUSB.sys
    Image path: \SystemRoot\System32\Drivers\ANDROIDUSB.sys
    Image name: ANDROIDUSB.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR="red"]Mon Oct 26 09:54:23 2009[/COLOR] (4AE563BF)
    CheckSum:         0001787F
    ImageSize:        0000F000
    File version:     2.0.7.1
    Product version:  2.0.7.1
    File flags:       2 (Mask 3) Pre-release
    File OS:          40000 NT Base
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      HTC, Corporation
    ProductName:      HTC Device Driver
    InternalName:     HTCAND.sys
    OriginalFilename: HTCAND.sys
    ProductVersion:   2.00
    FileVersion:      2.00 built by: WinDDK
    FileDescription:  ADB Interface
    LegalCopyright:   HTC, Corporation. All rights reserved.

As it appears this driver is pretty dated.
Check if HTC has any software updates.

 

[Seithes]

I've tried updating the drivers but unfortunately it doesn't look like anything new has came out for my phone. So, instead I've completely uninstalled the HTC drivers and the Android USB driver, restarted and then reinstalled HTC Sync.

I checked for updates on HTC sync and it said there were none so I uninstalled the phone syncing part (keeping the phone drivers).

All the drivers are back again and appear to be working. No idea if this will fix the issue, but best I could think of lol. I'll post another report if I have any more issues, but please let me know if you have any other suggestions.

Thanks,



- Seithes

 

[Seithes]

Unfortunately the reinstall has made no difference (Not that I'm surprised). The computer has had 2 BSODs today. I've compiled another report and hosted another memory dump in case that's of any use. Hopefully it'll uncover something new.

Memory Dump:
MEMORY.DMP - Google Drive

- Seithes

 

[axe0]

Did you check for BIOS updates?
Check if there are USB or chipset driver updates from lenovo.

 

[Seithes]

I already updated with everything that was available the other day, there are no other updates available for now. It's looking like the USB extension/phone cable I was using is to blame though. After swapping that out the issue has not occurred again so far and my phone has been plugged in all day.

My guess is a loose connection kept triggering the driver files until there was an issue, so I guess all I can really do is swap the cable and hope these break points aren't triggered again.

Thanks for the attempt though, I appreciate you taking the time to check out and try to solve my issue.

Cheers