Model: System Product Name Manufacturer: System manufacturer Microsoft Windows 7 Home Premium Service Pack 1 (X64) MiniToolBox by Farbar Version: 17-06-2016 Ok I ran minitoolbox by farbar - I also downloaded speccy and took a snapshot - details are below This was probably caused by the following module: ntoskrnl.exe (nt+0圆F980)īugcheck code: 0x50 (0xFFFFF8800EE176F5, 0x1, 0xFFFFF800033586EB, 0x2) On Sat 00:25:26 your computer crashed or a problem was reportedĬrash dump file: C:\Windows\Minidump\082617-12261-01.dmp On Fri 10:47:12 your computer crashed or a problem was reportedĬrash dump file: C:\Windows\Minidump\122818-12604-01.dmpīugcheck code: 0x50 (0xFFFFFFFFFFFFFFFF, 0x8, 0xFFFFFFFFFFFFFFFF, 0x0) On Fri 10:48:49 your computer crashed or a problem was reportedĬrash dump file: C:\Windows\Minidump\122818-12027-01.dmpīugcheck code: 0x50 (0xFFFFFFFFFFFFFFFC, 0x0, 0xFFFFF800033C7681, 0x0) On Fri 10:50:10 your computer crashed or a problem was reportedĬrash dump file: C:\Windows\Minidump\122818-11169-01.dmpīugcheck code: 0x50 (0xFFFFFFFFFFFFFFFC, 0x0, 0xFFFFF80003393681, 0x0) On Fri 10:52:45 your computer crashed or a problem was reportedĬrash dump file: C:\Windows\Minidump\122818-4399-01.dmpīugcheck code: 0x50 (0xFFFFFFFFFFFFFFFC, 0x0, 0xFFFFF800033C9681, 0x0) Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. The crash took place in a file system driver. This was probably caused by the following module: ntfs.sys (0xFFFFF880018C67E3)īugcheck code: 0x24 (0x1904FB, 0xFFFFF8800A2D9958, 0xFFFFF8800A2D91C0, 0xFFFFF880018C67E3)įile path: C:\Windows\system32\drivers\ntfs.sysīug check description: This indicates a problem occurred in the NTFS file system. On Fri 11:00:06 your computer crashed or a problem was reportedĬrash dump file: C:\Windows\Minidump\122818-4492-01.dmp This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. On Fri 11:34:59 your computer crashed or a problem was reportedĬrash dump file: C:\Windows\Minidump\122818-4492-02.dmpīugcheck code: 0x50 (0xFFFFFFFFFFFFFFFC, 0x0, 0xFFFFF800033D2681, 0x0)īug check description: This indicates that invalid system memory has been referenced. Possibly this problem is caused by another driver that cannot be identified at this time. The crash took place in the Windows kernel. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This might be a case of memory corruption. Product: Microsoft® Windows® Operating Systemīug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)īugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800033BF356, 0x0, 0x7)įile path: C:\Windows\system32\ntoskrnl.exe On Fri 12:38:01 your computer crashed or a problem was reportedĬrash dump file: C:\Windows\Minidump\122818-4446-01.dmp I wasnt able to read the windows dump files so I downloaded a tool called whocrashedme and here is what it shows I then started in safe mode and ran a disk check - the system restarted and completed the diskcheck. I then restarted the computer and I got a blue screen again (but i dont think it said the same error such as Page fault in non paged area) I ran a search in google and came accross a way to disable page caching by going to system properties, advanced performance settings, virtual memory and Uncheck the Automatically manage paging file size for all drives box and then select No paging file. it does however remain ok in safe mode with networking. I tried to boot the computer a couple more times with the same result. Today I started the computer and it started just fine - I logged into my user and then after about 1 minute I got the blue screen that read Page fault in no pages area.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |