I restarted my desktop (for the first time in a couple weeks), and on boot up ran into a BSOD: STOP: 0x0000007E (0xFFFFFFFFC0000005, 0xFFFFF8000355AB5A, 0xFFFFF880031CB3A8, 0xFFFFF880031CAC10) I tried system restore, but there was only 1 restore point which was from all the way back in January. I tried it anyway but after 10 minutes of running it said system restore could not be completed. I am confused why there is only one restore point. Additional info: I checked my BIOS and it is detecting my rams. CPU is Intel Sandy Bridge i5-2500k overclocked to 4.3GHz. I reclocked it back to stock speeds (3.3 GHz) in case it was causing the issue (I highly doubt that it is). But the problem persists. Running Windows 7. 12 GB of RAM at 1333 MHz OS on 64gb SSD. What is causing this? How should I fix it? Also, if it is caused by windows update, is there a way to undo the update with command prompt? I tried safemode, and the blue screen comes up as well, but I am able to access command prompt. --------------------------------------------- After about a week of frustration, I decided to simply restore my system to a disk image that I have (apparently). However, I wish to move it to a different drive (it is currently on my data disk), so I can start the restore. All my research on the location of disk image has been fruitless (people tend to put completely unhelpful answers).

Bug Check Code 0x7E: http://msdn.microsoft.com/en-us/library/ff559239(VS.85).aspx 0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred. Please use Microsoft Skydrive to upload dump files (c:\windows\minidumps). Once done, post a link here. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified IT Professional: Enterprise Administrator

For some reason there were no minidumps in the standard minidumps directory C:\windows\minidumps. However I did find a bunch of temp files (which all resemble minidumps) Here's a link to a rar archive of them: http://dl.dropbox.com/u/3085200/dump.rar I also uploaded a few to skydrive: https://skydrive.live.com/redir.aspx?cid=10d6d8d31f241df7&resid=10D6D8D31F241DF7!171

Hi, May I know if you can boot into normal mode successfully? If not, try the startup repair first. From the dump file, Bug Check Code 0x7E is caused by AppleCharger.sys. It is a driver used so the motherboard can charge Apple hardware such as iPhones or iPods. Therefore, you need to boot into Windows first and then remove or update the driver. Regarding your second question, restore points are automatically created by System Restore weekly and when System Restore detects the beginning of a change to your computer, such as when you install an update. However, the restore point will be damaged by virus or other computer clean program. Best Regards, Niki Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff800035c0b5a, The address that the exception occurred at Arg3: fffff880031cb3a8, Exception Record Address Arg4: fffff880031cac10, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". FAULTING_IP: nt!IoBuildDeviceIoControlRequest+2a fffff800`035c0b5a 8a484c mov cl,byte ptr [rax+4Ch] EXCEPTION_RECORD: fffff880031cb3a8 -- (.exr 0xfffff880031cb3a8) ExceptionAddress: fffff800035c0b5a (nt!IoBuildDeviceIoControlRequest+0x000000000000002a) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 000000000000004e Attempt to read from address 000000000000004e CONTEXT: fffff880031cac10 -- (.cxr 0xfffff880031cac10) rax=0000000000000002 rbx=fffff8a0008c6410 rcx=0000000000220448 rdx=0000000000000000 rsi=fffff8a0008c6410 rdi=0000000000000000 rip=fffff800035c0b5a rsp=fffff880031cb5e0 rbp=000000000000016d r8=fffff8a0008c6410 r9=000000000000016d r10=fffffa80096b4148 r11=0000000000000001 r12=0000000000000002 r13=000000000000016d r14=0000000000000000 r15=0000000000220448 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 nt!IoBuildDeviceIoControlRequest+0x2a: fffff800`035c0b5a 8a484c mov cl,byte ptr [rax+4Ch] ds:002b:00000000`0000004e=?? Resetting default scope PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 000000000000004e READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000350e0e0 000000000000004e FOLLOWUP_IP: AppleCharger+270c fffff880`03fd770c ?? ??? BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE LAST_CONTROL_TRANSFER: from fffff88003fd770c to fffff800035c0b5a STACK_TEXT: fffff880`031cb5e0 fffff880`03fd770c : fffff8a0`008c6410 00000000`00000002 fffff8a0`008c6410 00000000`000007ff : nt!IoBuildDeviceIoControlRequest+0x2a fffff880`031cb650 fffff8a0`008c6410 : 00000000`00000002 fffff8a0`008c6410 00000000`000007ff fffff8a0`008c6410 : AppleCharger+0x270c fffff880`031cb658 00000000`00000002 : fffff8a0`008c6410 00000000`000007ff fffff8a0`008c6410 00000000`0000016d : 0xfffff8a0`008c6410 fffff880`031cb660 fffff8a0`008c6410 : 00000000`000007ff fffff8a0`008c6410 00000000`0000016d fffff880`03fda100 : 0x2 fffff880`031cb668 00000000`000007ff : fffff8a0`008c6410 00000000`0000016d fffff880`03fda100 fffff880`031cb6b0 : 0xfffff8a0`008c6410 fffff880`031cb670 fffff8a0`008c6410 : 00000000`0000016d fffff880`03fda100 fffff880`031cb6b0 fffff880`031cb6a0 : 0x7ff fffff880`031cb678 00000000`0000016d : fffff880`03fda100 fffff880`031cb6b0 fffff880`031cb6a0 fffff880`03fda5bc : 0xfffff8a0`008c6410 fffff880`031cb680 fffff880`03fda100 : fffff880`031cb6b0 fffff880`031cb6a0 fffff880`03fda5bc ffffffff`ffffffff : 0x16d fffff880`031cb688 fffff880`031cb6b0 : fffff880`031cb6a0 fffff880`03fda5bc ffffffff`ffffffff fffff800`0339041c : AppleCharger+0x5100 fffff880`031cb690 fffff880`031cb6a0 : fffff880`03fda5bc ffffffff`ffffffff fffff800`0339041c 00000000`00060001 : 0xfffff880`031cb6b0 fffff880`031cb698 fffff880`03fda5bc : ffffffff`ffffffff fffff800`0339041c 00000000`00060001 fffff880`031cb6b8 : 0xfffff880`031cb6a0 fffff880`031cb6a0 ffffffff`ffffffff : fffff800`0339041c 00000000`00060001 fffff880`031cb6b8 fffff880`031cb6b8 : AppleCharger+0x55bc fffff880`031cb6a8 fffff800`0339041c : 00000000`00060001 fffff880`031cb6b8 fffff880`031cb6b8 00000000`00000002 : 0xffffffff`ffffffff fffff880`031cb6b0 fffff880`03fd7aaa : ffffffff`ffffffff 00000000`00000000 fffff880`03fda5bc 00000000`ffffffff : nt!DbgPrint+0x3c fffff880`031cb6f0 ffffffff`ffffffff : 00000000`00000000 fffff880`03fda5bc 00000000`ffffffff 00000000`00000000 : AppleCharger+0x2aaa fffff880`031cb6f8 00000000`00000000 : fffff880`03fda5bc 00000000`ffffffff 00000000`00000000 00000000`00000002 : 0xffffffff`ffffffff SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: AppleCharger+270c FOLLOWUP_NAME: MachineOwner MODULE_NAME: AppleCharger IMAGE_NAME: AppleCharger.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4bd65fdd STACK_COMMAND: .cxr 0xfffff880031cac10 ; kb FAILURE_BUCKET_ID: X64_0x7E_AppleCharger+270c BUCKET_ID: X64_0x7E_AppleCharger+270c Followup: MachineOwner --------- 2: kd> lmvm AppleCharger start end module name fffff880`03fd5000 fffff880`03fdd000 AppleCharger T (no symbols) Loaded symbol image file: AppleCharger.sys Image path: AppleCharger.sys Image name: AppleCharger.sys Timestamp: Tue Apr 27 05:54:05 2010 (4BD65FDD) CheckSum: 000093A3 ImageSize: 00008000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 __________________________________________________________________ Bug Check Code 0x7E: http://msdn.microsoft.com/en-us/library/ff559239(VS.85).aspx The BSOD was cause by AppleCharge.sys driver. Possibly that this driver belongs to Apple. If yes, try updating it or contact Apple Technical Support. Also, I suspect that this file belongs to a malware program. Please perform a full scan and uninstall all malware programs that have been detected. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified IT Professional: Enterprise Administrator

Hmm, I did some research on applecharger.sys. It is a driver that comes with GigaByte motherboards that supports faster charging on apple devices. I tried changing the file to AppleDriver.sys.bak, and got a different bluescreen: c0000145 {Application Error} The application was unable to start correctly (oxc000005). Click OK to close the application. I put applecharger.sys back and i started getting my old bluescreen again.

So you it will better to update it or contact its developer Technical Support. You can also try to uninstall it. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified IT Professional: Enterprise Administrator

If you want to disable it, you can't (as you've seen) just rename the file. Open the registry to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet*\services and find the key that contains applecharger.sys. Change the "Start" value to 4 to disable it. http://msdn.microsoft.com/en-us/library/ff557272(VS.85).aspx

Try to boot in safe mode and then check the system for malware just in case Windows MVP, paid Remote Assistance is available for XP, Vista and Windows 7. My page on Video Card Problems is now my most popular landing page. See my gaming site for game reviews etc. Developer | Windows IT | Chess | Economics | Hardcore Games | Vegan Advocate | PC Reviews