so far I have gotten, among other BSOD errors, win32k.sys dxgmms1.sys several IRQL errors, system service exception and a few others I can't remember. There seems to be no related cause between what programs I am running and the crash. I was running in 64 bit, ran a registry sweep and the only issues were 64 bit related keys. I started running it in 32 bit and still had some issues. I ran the win 7 upgrade advisor, and that came back with everything passing. I even took it in to a PC repair shop and they couldn't find out what was wrong and the memory was fine, the hdd was fine, power supply was fine. Please help. Hardware eVGA P55 LE mobo i5 760 Lynnfield G.skill 4 GB RAM barracuda 7200 hdd black widow 850w PSU geforce GTX 460 palit 1gb gpu

To see the cause I have to take a look at the dumps with the Debugging Tools for Windows. Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your public Skydrive [1] folder and post a link here. André [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

https://cid-7e686d9e7f1fefcf.office.live.com/self.aspx/.Documents/Dumps.zip I think I got it right

the link doesn't work. Please put the file into your public folder or change the sharing permissions"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

I changed permissions, I think it should work

PAGE_FAULT_IN_NONPAGED_AREA (50) - Invalid system memory was referenced. STACK_TEXT: nt!KeBugCheckEx nt! ?? ::FNODOBFM::`string'+0x40ec0 nt!KiPageFault+0x16e nt!MiRemoveWorkingSetPages +0x337 nt!MmCleanProcessAddressSpace +0x4ca IMAGE_NAME: memory_corruption Bug Check 0x7F: UNEXPECTED_KERNEL_MODE_TRAP 0x00000008 , or Double Fault , indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault: * A kernel stack overflow. This overflow occurs when a guard page is hit, and the kernel tries to push a trap frame. Because there is no stack left, a stack overflow results, causing the double fault. * A hardware problem. CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt 8 errors : !nt (fffff80002ee0484-fffff80002ee04bc) fffff80002ee0480 48 8b c2 48 *d3 e8 12 48 ba 00 00 00 *62 fb f6 ff H..H...H....b... fffff80002ee0490 ff 4d 8b d5 *2f f8 ff ff 3f 49 c1 ea *07 4c 8d 1c .M../...?I...L.. fffff80002ee04a0 10 48 b8 00 *74 60 82 04 09 00 00 41 *70 e2 ff 01 .H..t`.....Ap... fffff80002ee04b0 00 00 48 2b *a4 80 f9 01 0f 87 f2 4e *27 00 45 33 ..H+.......N'.E3 MODULE_NAME: memory_corruption Please download memtest86+ [1], burn a new bootable CD (use a CD-RW if possible) from the ISO (download and use ImgBurn [2] to do this or make double click on the ISO in Windows 7), reboot your PC and scan your RAM 4-5hours for errors. If it detects errors, replace the faulty RAM. If the memtest tells no error, please download CPU-Z [3], look in the memory and SPD tab and verify that the current RAM Speed and the Timings match to the values that you see in the SPD tab. If your RAM run at CR (Command Rate) 1T, change the value into 2T in the BIOS. This should fix the crashes. André [1] http://www.memtest.org/download/4.10/memtest86+-4.10.iso.zip [2] http://www.imgburn.com/index.php?act=download [3] http://www.cpuid.com/softwares/cpu-z.html"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

Hi, Please update the BIOS and all drivers to the latest versions from the manufacture. Also test if the issue occurs in Safe Mode. Regards, NikiPlease 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.