New
#1
BSOD 64bit 0x1EE408 PFN_LIST_CORRUPT 0x75BC0 MEMORY_MANAGEMENT
Hi fellow techies!
This PC I built for a friend for PRO Poker Online, so needs to be rock solid.
But of course of all my recent builds this is failing randomly, usually from cold start will be sat with chrome open, few tabs and postgres always on in background - bang BSOD.
Or many poker sites open, camtasia, chrome, postgres, skype all running for 8 hours+ no problem, start to close down/idle - bang BSOD.
Am hoping not memory as we have tried two different sets and same occurs.
Have removed various AV we tried, ie. Avast. MSE, no change but less frequent.
ATM we're running into BSOD every ~1 week.
I hsve little acces to PC as it is in constant use to a tight schedule, so I cant pull it a apart and re-add at my leisure unfortunately.
It had a valid key for Windows to get all updates/fixes etc but then that was mine which I needed for others, so he is waiting to purchase after proved. Same occurred with key.
Hardware is all new; i5 1150, asrock H81M-HDS, Samsung ssd 120gb, intell ssd 40gb, 1tb green WD, corsair or crucial 8gb ram, asus radeon 5450, 500w psu.
Driver verifier hasnt been run as i am not physically at pc to fix if wont boot!
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASRock, H81M-HDS
CPU: GenuineIntel Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8525328384 total
SF diags and dumps attached
Code:On Sat 03/01/2015 11:17:39 GMT your computer crashed crash dump file: C:\Windows\Minidump\010315-5865-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x4E (0x99, 0x1EE408, 0x0, 0x1EE488) Error: PFN_LIST_CORRUPT file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that the page frame number (PFN) list is corrupted. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Mon 29/12/2014 09:42:14 GMT your computer crashed crash dump file: C:\Windows\Minidump\122914-5803-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x4E (0x99, 0xC65EE, 0x0, 0xC6AEE) Error: PFN_LIST_CORRUPT file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that the page frame number (PFN) list is corrupted. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Wed 24/12/2014 07:59:00 GMT your computer crashed crash dump file: C:\Windows\Minidump\122414-5834-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x1A (0x41201, 0xFFFFF68000004568, 0x2F400000B052C025, 0xFFFFFA800F59E370) Error: MEMORY_MANAGEMENT file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Wed 17/12/2014 05:01:45 GMT your computer crashed crash dump file: C:\Windows\Minidump\121714-7690-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x1A (0x41201, 0xFFFFF68000021568, 0x96600001C0349867, 0xFFFFFA800A40CEC0) Error: MEMORY_MANAGEMENT file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Thu 04/12/2014 00:24:18 GMT your computer crashed crash dump file: C:\Windows\Minidump\120414-6692-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x4E (0x99, 0x1B0329, 0x2, 0x1A9A8) Error: PFN_LIST_CORRUPT file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that the page frame number (PFN) list is corrupted. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sat 29/11/2014 23:23:23 GMT your computer crashed crash dump file: C:\Windows\Minidump\112914-6552-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x1A (0x403, 0xFFFFF6800002C5E8, 0xF400000052088825, 0xFFFFF680000C6C10) Error: MEMORY_MANAGEMENT file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a severe memory management error occurred. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sat 22/11/2014 17:51:51 GMT your computer crashed crash dump file: C:\Windows\Minidump\112214-6302-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x4E (0x99, 0xCA4A1, 0x0, 0xC6A21) Error: PFN_LIST_CORRUPT file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that the page frame number (PFN) list is corrupted. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Wed 12/11/2014 23:22:30 GMT your computer crashed crash dump file: C:\Windows\Minidump\111214-6208-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000314834E, 0xFFFFF880093655E0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Thu 06/11/2014 07:03:24 GMT your computer crashed crash dump file: C:\Windows\Minidump\110614-5959-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x4E (0x99, 0xB71BF, 0x0, 0xB723F) Error: PFN_LIST_CORRUPT file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that the page frame number (PFN) list is corrupted. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Tue 04/11/2014 19:37:36 GMT your computer crashed crash dump file: C:\Windows\Minidump\110414-5709-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x4E (0x7, 0x16BD8D, 0x100000, 0x0) Error: PFN_LIST_CORRUPT file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that the page frame number (PFN) list is corrupted. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.