P Penschu New member Joined May 25, 2014 Posts 2 May 25, 2014 #1 Hi. After Windows crashed today evening on a pc, and a hard restart (unplug cable) was the only opinion, the pc started to produce bluescreens. Mostly they occur randomly after starting a browser or already at login. I uploaded the dumps. Can someone help me and say whtas going wrong and how i fix it? Thanks in advance :) My Pc: Intel q8200 4Gb Ram Windows 8.1 (latest Updates) nvidia 7100/nForce 630i Attachments Dumps.zip 274.3 KB · Views: 5
Hi. After Windows crashed today evening on a pc, and a hard restart (unplug cable) was the only opinion, the pc started to produce bluescreens. Mostly they occur randomly after starting a browser or already at login. I uploaded the dumps. Can someone help me and say whtas going wrong and how i fix it? Thanks in advance :) My Pc: Intel q8200 4Gb Ram Windows 8.1 (latest Updates) nvidia 7100/nForce 630i
Jared Sysnative Staff, BSOD Kernel Dump Expert Joined Feb 3, 2014 Posts 1,591 Jun 1, 2014 #2 A lot of memory corruption. Code: BugCheck 1A, {41792, c00e56d8, 0, 40} Probably caused by : memory_corruption ( ONE_BIT ) A PTE has been corrupted, this looks like bad RAM. Code: 2: kd> dt nt!_MMPFN c00e56d8 +0x000 u1 : <unnamed-tag> +0x004 u2 : <unnamed-tag> +0x008 PteAddress : (null) +0x008 VolatilePteAddress : (null) +0x008 Lock : 0n0 +0x008 PteLong : 0 +0x00c u3 : <unnamed-tag> +0x010 OriginalPte : _MMPTE +0x018 u4 : <unnamed-tag> The page table entry is completely null, it's not valid. That doesn't make any sense from what I can tell. Run Memtest86 for AT LEAST 8 passes. Follow these instructions. https://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-with-memtest86.html
A lot of memory corruption. Code: BugCheck 1A, {41792, c00e56d8, 0, 40} Probably caused by : memory_corruption ( ONE_BIT ) A PTE has been corrupted, this looks like bad RAM. Code: 2: kd> dt nt!_MMPFN c00e56d8 +0x000 u1 : <unnamed-tag> +0x004 u2 : <unnamed-tag> +0x008 PteAddress : (null) +0x008 VolatilePteAddress : (null) +0x008 Lock : 0n0 +0x008 PteLong : 0 +0x00c u3 : <unnamed-tag> +0x010 OriginalPte : _MMPTE +0x018 u4 : <unnamed-tag> The page table entry is completely null, it's not valid. That doesn't make any sense from what I can tell. Run Memtest86 for AT LEAST 8 passes. Follow these instructions. https://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-with-memtest86.html
P Patrick Sysnative Staff Joined Jun 7, 2012 Posts 4,618 Jun 1, 2014 #3 Hi, In addition to MooMoo's great advice, ONE_BIT corruption generally in most if not all cases implies bad RAM. Regards, Patrifk
Hi, In addition to MooMoo's great advice, ONE_BIT corruption generally in most if not all cases implies bad RAM. Regards, Patrifk
P Penschu New member Joined May 25, 2014 Posts 2 Jun 1, 2014 #4 Hello. First of all thanks for your answers. I will check the Pc with memtest later. Is it possible that the sudden loose of voltage has "only" corrupted some important windows files? I was able to reapir the pc two days ago using sfc and dism and since then no other bluescreen has been raised. Regards
Hello. First of all thanks for your answers. I will check the Pc with memtest later. Is it possible that the sudden loose of voltage has "only" corrupted some important windows files? I was able to reapir the pc two days ago using sfc and dism and since then no other bluescreen has been raised. Regards
P Patrick Sysnative Staff Joined Jun 7, 2012 Posts 4,618 Jun 1, 2014 #5 Yes, very possible. Let us know how things go. Regards, Patrick