Question
Applies to
17506 views
Win7 blue screen error 0x0000007e (c0000005 .... )
My computer crashed on boot up after I had to force restart while playing a game called Rumble Fighter.
I Know the error says "STOP : 0x0000007e (c0000005, 2, 3 , 4) 234 = parameters."
other information i can release is add. information such as:
BCCode: 1000007e
BCP1: C0000005
BCP2: 82C87781
BCP3: 8DF6F46C
BCP4: 8DF6F050
My laptop is a Samsung Rv511 and my OS is Win7 SP1.
my mini dump file: http://www.mediafire.com/download/bja7goe9o1bx1bb/MDMP.zip
All help is welcomed, thanks!
-Bill
Abuse history
Answer
Hi Bill,
All of the attached dump files are of the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) bugcheck.
This indicates that a system thread generated an exception which the error handler did not catch.
We seem to be dealing with a variety of driver issues here, so let's analyze this closely:
In a *1000007E bugcheck, the most important thing (generally) is the 1st parameter. In your case, the 1st parameter is always c0000005 which indicates an access violation occurred.
If we run an .exr:
0: kd> .exr 0xffffffff8291646c
ExceptionAddress: 82c85781 (nt!__InterlockedIncrement+0x00000005)
ExceptionCode: c0000005 (Access violation)
^^ See?
Now that we ran the .exr, let's go one step further and run a !thread to get the call stack:
STACK_TEXT:
82916530 97aea725 00000000 8291654c 97ae548b nt!__InterlockedIncrement+0x5
WARNING: Stack unwind information not available. Following frames may be wrong.
8291653c 97ae548b 82916940 86898c2c 82916560 AMPPAL+0x13725
8291654c 97ae4ffc 829165d8 00000003 86898c40 AMPPAL+0xe48b
82916560 97afa058 829165d8 86895478 86895460 AMPPAL+0xdffc
82916580 97afa23b 829165d8 8689887c 00000000 AMPPAL+0x23058
8291659c 97aeb167 829165d8 0000000a 00000000 AMPPAL+0x2323b
8291661c 8c11eeaa 8675b7b0 8291666c 868720e0 AMPPAL+0x14167
82916650 8c11e9e9 c00000bb 8291666c 82916808 ndis!ndisPnPNotifyBinding+0x13b
829166ec 8c0f5d99 868720e0 00000000 00000000 ndis!ndisPnPNotifyAllTransports+0x17b
82916718 90d5d248 868720e0 82916808 82916744 ndis!NdisFNetPnPEvent+0x99
82916728 8c0f5d77 871e5808 82916808 82916808 wfplwf!FilterNetPnPEvent+0x14
82916744 90d71cfc 868720e0 82916808 82916770 ndis!NdisFNetPnPEvent+0x77
82916754 8c0f5d77 869f8e10 82916808 82916808 pacer!PcFilterPnPEvent+0x14
82916770 90d9425c 868720e0 82916808 8291679c ndis!NdisFNetPnPEvent+0x77
82916780 8c0f5d77 8677b6c0 82916808 82916808 hssdrv6+0x125c
8291679c 9c0393ba 868720e0 82916808 871dbb00 ndis!NdisFNetPnPEvent+0x77
829167b4 8c0f5d77 871e5c08 82916808 90d8b1e0 nwifi!FilterNetPnPEvent+0xc6
829167d0 90d8460b 868720e0 82916808 868720e0 ndis!NdisFNetPnPEvent+0x77
829167ec 8c0cb35f 869fd008 82916808 877ed710 vwififlt!FilterNetPnPEvent+0x41
82916860 8c0cdfa6 868720e0 00000000 00000000 ndis!ndisDevicePnPEventNotifyFiltersAndAllTransports+0xe2
82916898 8c0fcc61 00000000 829168c4 85679000 ndis!ndisPnPPortActivation+0x7b3
829168b4 97638af8 868720e0 00000000 00580180 ndis!NdisMNetPnPEvent+0x76
8291691c 97638b84 868720e0 0000000a 82916940 bcmwl6+0x1caf8
82916990 97638e18 85679000 00000000 8df8749c bcmwl6+0x1cb84
829169f0 9763dd77 8df8749c 8df873bc 85675000 bcmwl6+0x1ce18
82916c38 9763ec38 85679000 0e040101 8df8749c bcmwl6+0x21d77
82916c6c 9763f5bd 85677b10 0e040101 8df8749c bcmwl6+0x22c38
82916ca8 9763f68e 82c17700 9763f7ff 85677a68 bcmwl6+0x235bd
82916cc4 9763857a 01679000 85677a20 86872028 bcmwl6+0x2368e
82916cdc 8c0ac2d6 85677a68 85677a48 82916d00 bcmwl6+0x1c57a
82916cec 82e5f613 86872028 85677a48 871ad020 ndis!ndisDispatchIoWorkItem+0xf
82916d00 82cc814b 85677a20 00000000 871ad020 nt!IopProcessWorkItem+0x23
82916d50 82e5412b 80000000 a4f353c0 00000000 nt!ExpWorkerThread+0x10d
82916d90 82cfb559 82cc803e 80000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
Starting from bottom going upward, we have various bcmwl6.sys calls which is the
All of the attached dump files are of the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) bugcheck.
This indicates that a system thread generated an exception which the error handler did not catch.
We seem to be dealing with a variety of driver issues here, so let's analyze this closely:
In a *1000007E bugcheck, the most important thing (generally) is the 1st parameter. In your case, the 1st parameter is always c0000005 which indicates an access violation occurred.
If we run an .exr:
0: kd> .exr 0xffffffff8291646c
ExceptionAddress: 82c85781 (nt!__InterlockedIncrement+0x00000005)
ExceptionCode: c0000005 (Access violation)
^^ See?
Now that we ran the .exr, let's go one step further and run a !thread to get the call stack:
STACK_TEXT:
82916530 97aea725 00000000 8291654c 97ae548b nt!__InterlockedIncrement+0x5
WARNING: Stack unwind information not available. Following frames may be wrong.
8291653c 97ae548b 82916940 86898c2c 82916560 AMPPAL+0x13725
8291654c 97ae4ffc 829165d8 00000003 86898c40 AMPPAL+0xe48b
82916560 97afa058 829165d8 86895478 86895460 AMPPAL+0xdffc
82916580 97afa23b 829165d8 8689887c 00000000 AMPPAL+0x23058
8291659c 97aeb167 829165d8 0000000a 00000000 AMPPAL+0x2323b
8291661c 8c11eeaa 8675b7b0 8291666c 868720e0 AMPPAL+0x14167
82916650 8c11e9e9 c00000bb 8291666c 82916808 ndis!ndisPnPNotifyBinding+0x13b
829166ec 8c0f5d99 868720e0 00000000 00000000 ndis!ndisPnPNotifyAllTransports+0x17b
82916718 90d5d248 868720e0 82916808 82916744 ndis!NdisFNetPnPEvent+0x99
82916728 8c0f5d77 871e5808 82916808 82916808 wfplwf!FilterNetPnPEvent+0x14
82916744 90d71cfc 868720e0 82916808 82916770 ndis!NdisFNetPnPEvent+0x77
82916754 8c0f5d77 869f8e10 82916808 82916808 pacer!PcFilterPnPEvent+0x14
82916770 90d9425c 868720e0 82916808 8291679c ndis!NdisFNetPnPEvent+0x77
82916780 8c0f5d77 8677b6c0 82916808 82916808 hssdrv6+0x125c
8291679c 9c0393ba 868720e0 82916808 871dbb00 ndis!NdisFNetPnPEvent+0x77
829167b4 8c0f5d77 871e5c08 82916808 90d8b1e0 nwifi!FilterNetPnPEvent+0xc6
829167d0 90d8460b 868720e0 82916808 868720e0 ndis!NdisFNetPnPEvent+0x77
829167ec 8c0cb35f 869fd008 82916808 877ed710 vwififlt!FilterNetPnPEvent+0x41
82916860 8c0cdfa6 868720e0 00000000 00000000 ndis!ndisDevicePnPEventNotifyFiltersAndAllTransports+0xe2
82916898 8c0fcc61 00000000 829168c4 85679000 ndis!ndisPnPPortActivation+0x7b3
829168b4 97638af8 868720e0 00000000 00580180 ndis!NdisMNetPnPEvent+0x76
8291691c 97638b84 868720e0 0000000a 82916940 bcmwl6+0x1caf8
82916990 97638e18 85679000 00000000 8df8749c bcmwl6+0x1cb84
829169f0 9763dd77 8df8749c 8df873bc 85675000 bcmwl6+0x1ce18
82916c38 9763ec38 85679000 0e040101 8df8749c bcmwl6+0x21d77
82916c6c 9763f5bd 85677b10 0e040101 8df8749c bcmwl6+0x22c38
82916ca8 9763f68e 82c17700 9763f7ff 85677a68 bcmwl6+0x235bd
82916cc4 9763857a 01679000 85677a20 86872028 bcmwl6+0x2368e
82916cdc 8c0ac2d6 85677a68 85677a48 82916d00 bcmwl6+0x1c57a
82916cec 82e5f613 86872028 85677a48 871ad020 ndis!ndisDispatchIoWorkItem+0xf
82916d00 82cc814b 85677a20 00000000 871ad020 nt!IopProcessWorkItem+0x23
82916d50 82e5412b 80000000 a4f353c0 00000000 nt!ExpWorkerThread+0x10d
82916d90 82cfb559 82cc803e 80000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
Starting from bottom going upward, we have various bcmwl6.sys calls which is the
Broadcom 802.11g Network Adapter driver. Going upward some more, we reach an
hssdrv6.sys call which is the Hotspot Shield Routing Driver (more than likely the cause here). I have seen it and solved many cases in which it was the cause of the crashes. Let's continue though.... if we go upward some more, we reach a few
AMPPAL.sys calls which is the Intel® Centrino® Bluetooth 3.0 + High Speed Virtual Adapter driver.
----------------------------------------------------------------------------------
Overall, as I said, Hotspot Shield is more than likely causing conflicts here. I recommend removal for troubleshooting purposes ASAP.
Regards,
Patrick
----------------------------------------------------------------------------------
Overall, as I said, Hotspot Shield is more than likely causing conflicts here. I recommend removal for troubleshooting purposes ASAP.
Regards,
Patrick
Debugger/Reverse Engineer.
Abuse history
Answer
Thank you all so much! Patrick I owe you my greatest gratitude.
I uninstalled HSS and restarted but it didn't work, however I system restore'd and it worked after that point and I'm now happily surfing the web.
This website is awesome and so are the people, I shall definitely use this website before I take it to the local repair man and get charged £50-£100.
Thanks so much,
Bill
Abuse history
