Bccode 1000007e

[jona_77]

having problem with pc shutting down and restarting saying crit error.as follows

bccode:1000007e

bcp1:c0000005

bcp2:804e3687

bcp3:f79afbb4

bcp4:f79af830

osver:5 1 2600

sp.2.0

product:256.1

any ideas please!!

[TheTerrorist_75]

Click the Start button the select Run. In the Run box type eventvwr.msc and press the <Enter> key. In the left hand window select each item one at a time and look in the right window for any red Xs. Double click each one with a red X then click on the clipboard symbol below the up and down arrows and paste the contents here in a reply.

[Pete_C]

having problem with pc shutting down and restarting saying crit error.as follows

bccode:1000007e

bcp1:c0000005

bcp2:804e3687

bcp3:f79afbb4

bcp4:f79af830

osver:5 1 2600

sp.2.0

product:256.1

any ideas please!!

http://www.aumha.org/a/stop.php

0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

Essentially the same error as 0x7E above.

0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for additional information.

My understanding is that the 0x1 are more likely to be hardware incompatabilities or defects while 0x0 versions are more likely to be software or driver related.

http://msdn2.microsoft.com/en-gb/library/ms795746.aspx

Describes the meaning of your four parameters

1 The exception code that was not handled

2 The address where the exception occurred

3 The address of the exception record

4 The address of the context record

0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.

This can be caused by anything from faulty RAM, an incorrect/corrupt device driver, poorly written/updated software and more commonly under Windows XP Service pack 2, malware/adware installations.

Applications that attempt to violate DEP will receive an exception with status code STATUS_ACCESS_VIOLATION (0xC0000005).

Note: It is possible to "Turn Off" DEP in the boot.ini file but this really would be a last step!

/NOEXECUTE

This option is only available on 32-bit versions of Windows when running on processors supporting no-execute protection. It enables no-execute protection (also known as Data Execution Protection - DEP), which results in the Memory Manager marking pages containing data as no-execute so that they cannot be executed as code. This can be useful for preventing malicious code from exploiting buffer overflow bugs with unexpected program input in order to execute arbitrary code. No-execute protection is always enabled on 64-bit versions of Windows on processors that support no-execute protection.

There are several options you can specify with this switch:

/NOEXECUTE=OPTIN Enables DEP for core system images and those specified in the DEP configuration dialog.

/NOEXECUTE=OPTOUT Enables DEP for all images except those specified in the DEP configuration dialog.

/NOEXECUTE=ALWAYSON Enables DEP on all images.

/NOEXECUTE=ALWAYSOFF Disables DEP. (This setting doesn't provide any DEP coverage for any part of the system, regardless of hardware DEP support. The processor doesn't run in Physical Address Extension (PAE) mode unless the /PAE option is present in the boot.ini file.)

My bet would be an incompatible antivirus / firewall (in this case it would be the virtual machine aspect ) if you have a third party one or an incompatible video card.