Anyone have any ideas? This has been occuring sporatically since April of last year. Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional information about the problem: BCCode: 50 BCP1: FFFFFA81091EC9A0 BCP2: 0000000000000000 BCP3: FFFFF8800445BD81 BCP4: 0000000000000005 OS Version: 6_1_7601 Service Pack: 1_0 Product: 256_1 Files that help describe the problem: C:\Windows\Minidump\011812-26722-01.dmp C:\Users\Cinema Namon\AppData\Local\Temp\WER-66690-0.sysdata.xml

The Stop 0x00000050 (PAGE_FAULT_IN_NONPAGED_AREA) indicates that invalid system memory has been referenced (during a read operation, as indicated by the value of the second parameter). This Stop usually occurs after the installation of faulty hardware or in the event of failure of installed hardware. Locate the .DMP file in the \Windows\Minidump folder, upload it to your Windows Live SkyDrive, make it publicly accessible and post the URL here, so we can analyze it and try to understand how you can fix this issue. Bye.Luigi Bruno - Microsoft Community Contributor 2011 Award

Luigi, Thanks for your reply. Hopefully I did this correctly...try this link: https://skydrive.live.com/redir.aspx?cid=aadb34625f67387e&resid=AADB34625F67387E!119&parid=AADB34625F67387E!115&authkey=!AGA9KZzYtktYaCM There's also an old version out there but I'm sure it's the same issue. Thanks

According to the information provided by the dump file, the faulting module seems to be dxgkrnl.sys, the DirectX Graphics Kernel; the informations cannot help determining the faulting process. Did you change your video card? Is it fully compatible with Windows 7? Did you install the most recent version of the drivers and software for your video card? Bye.Luigi Bruno - Microsoft Community Contributor 2011 Award

The video card I have installed is: GIGABYTE GV-R455D3-512I Radeon HD 4550 512MB 64-bit DDR3 PCI Express 2.0 x16 HDCP Ready Video Card and I installed it at the time I built this computer in 9/2010. I chose this one because it was cheap and it had HDMI which my motherboard didnt. According to Microsoft this video card is compatible with Windows 7. I believe I have the latest driver....in checking Gigabyte's website the latest driver has a date of 1/2010..which is before my actual build...so there hasn't been a driver update since my installation. The very first Blue screen occured on 9/21/2010 and for your reference I've loaded that dump in skydrive @: https://skydrive.live.com/redir.aspx?cid=aadb34625f67387e&resid=AADB34625F67387E!120&parid=AADB34625F67387E!115&authkey=!AFVIhSCJ5W361v0 The next Blue screen occured on 4//5/2011 and that dump can be seen here: https://skydrive.live.com/redir.aspx?cid=aadb34625f67387e&resid=AADB34625F67387E!121&parid=AADB34625F67387E!115&authkey=!AGWJdCLP1y1x0wU Just curious if it's the same problem. The dumps have been occuring every month(ish) since 4/5/2011. Thanks again for your time.

Hi, From the dump file in 2011, the BSOD can be caused by bad memory. Please check memory first. Diagnosing memory problems on your computer http://windows.microsoft.com/en-US/windows7/Diagnosing-memory-problems-on-your-computer Memtest86 http://www.memtest.org/ Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. If possible, please replace the memory for a test. If the BSOD occurred recently, please upload the latest dump file in 2012. Niki Han TechNet Community Support

Niki, Thanks for your reply. My first dump of 2012 is linked above in my second post. I also posted the very first BSOD above as well. I was hoping the BSOD would be caused by the same issue but it appears that it is not. I've got 8GB of memory in this box comprised of 4 2GB DIMMS. Is there anything that indicates which stick might be bad? Don't want to just replace all 4 DIMMS. Thanks

0x50 isn't always caused by memory errors, it could be a bad driver and driver verifier might help to identify which one based on the dumps produced after verifier is enabled, http://mikemstech.blogspot.com/2011/12/troubleshooting-0x50.html http://mikemstech.blogspot.com/2011/12/enable-driver-verifier-to-help-identify.html http://mikemstech.blogspot.com/2011/11/windows-crash-dump-analysis.html If you suspect a RAM issue, you might try memtest86+, http://mikemstech.blogspot.com/2011/11/troubleshooting-memory-errors.html -- Mike Burr Interesting Reading on Technology and Finance