I am running Windows 7 64bit on a Dell Inspiron 15. I get the following error message. Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.768.3 Locale ID: 1033 Additional information about the problem: BCCode: 7f BCP1: 0000000000000008 BCP2: 0000000080050031 BCP3: 00000000000406F8 BCP4: FFFFF800030AA6AE OS Version: 6_1_7600 Service Pack: 0_0 Product: 768_1 Files that help describe the problem: C:\Windows\Minidump\040811-22386-01.dmp C:\Users\Joshua Weaver\AppData\Local\Temp\WER-47564-0.sysdata.xml Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt I have uploaded my MINIDUMP file to my skydrive.live account. I have allowed vivian xing (v-vxin@hotmail.com) to access these files. If you happen to come across this post please respond. Thank you. you can email me at dtreida@gmail.com

Hello, Bug Check Code 0x7F: http://msdn.microsoft.com/en-us/library/ff559244(VS.85).aspx Please use Microsoft Skydrive to upload dump files (%systemroot%\minidumps\ like c:\windows\minidumps). Once done post a link here. If you want to debug dump files without my help, use Windbg and refer to this Microsoft article: http://support.microsoft.com/kb/315263 This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 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

https://cid-9c8876af04b6c877.office.live.com/self.aspx/.Documents/Minidump.zip

Hello, please set the folder for public access. I am unable to open it. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 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

I have now made the file public, so you should be able to access it now. I thought I had already changed it but I guess not...Looking forward to your response

I have now made it public

Ok well I decided to go ahead and try some things I found elsewhere on the internet. I ran some FREE malware/spyware programs on the computer and was able to get rid of a ton or errors. I ran some FREE registry fixers and optimized my drive. I recommend Advanced SystemCare3, the free version worked well enough to get the computer back in operating shape. I was then able to get rid of Mcafee and install norton to help seal the deal. I got rid of the crappy McAfee virus software I had installed and bought Norton 360 and put it on my computer. I ran Norton and found even more bad files. I have not had any freezing problems, blue screens, or anything since I have done all of this. I am now able to get my windows updates going again so i can get this computer completely updated and ready. I did have to do a lot of this stuff in safe mode, for those of you that are having the same problems.

Hello, KMODE_EXCEPTION_NOT_HANDLED (1e) 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: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000008, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. MODULE_NAME: nt FAULTING_MODULE: fffff80002050000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: +3832393839656339 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000008 EXCEPTION_PARAMETER2: 0000000000000000 WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd 0000000000000000 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. BUGCHECK_STR: 0x1E_c0000005 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff800020faa39 to fffff800020c0740 STACK_TEXT: fffff880`09091ce8 fffff800`020faa39 : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt+0x70740 fffff880`09091cf0 00000000`0000001e : ffffffff`c0000005 00000000`00000000 00000000`00000008 00000000`00000000 : nt+0xaaa39 fffff880`09091cf8 ffffffff`c0000005 : 00000000`00000000 00000000`00000008 00000000`00000000 fffff880`09092001 : 0x1e fffff880`09091d00 00000000`00000000 : 00000000`00000008 00000000`00000000 fffff880`09092001 fffff880`09092080 : 0xffffffff`c0000005 STACK_COMMAND: kb FOLLOWUP_IP: nt+70740 fffff800`020c0740 48894c2408 mov qword ptr [rsp+8],rcx SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt+70740 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: ntoskrnl.exe BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- ----------------------------------------------------------------------------------------- Bug Check Code 0x1E: http://msdn.microsoft.com/en-us/library/ff557408(VS.85).aspx Please start by updating all possible drivers. It is also possible that a security software that is installed is causing such problem. Personally, I don't recommend the use of registry cleaners because they may cause severe problems so I recommend that you restore your system state using a restore point that dates before the cleaning operation. As you have many dump files, I recommend that you use memtest86+ to check that all is okay with your RAM. If a faulty one was detected then replace it. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 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

Thank You for your support.

Hi, Just un-install the latest driver installed in your PC or use system restore to restore your previous good configuration. http://aloysiusjegan.in Aloysius Jegan