New
#1
solved
Solved...
Can be closed
Last edited by DaemonGx; 01 Oct 2013 at 14:49.
Random BSOD , error 0x0000000a ( fltmgr.sys + ntoskrnl.exe)
-
-
Computer Type: PC/Desktop
System Manufacturer/Model Number: Self assembled
OS: Windows 10 Home 64Bit
CPU: Intel Core i5 10400 @ 2.90GHz
Motherboard: Intel Corporation DG41WV (PROCESSOR)
Memory: 8.00GB Single-Channel Unknown @ 1329MHz (16-20-20-38)
Sound Card: Realtek High Definition Audio
Monitor(s) Displays: DELL E170S
Screen Resolution: 1280x1024 pixels
Keyboard: A4 Tech Co LTD
Mouse: A4 Tech Co Ltd/Logitech
Case: Nothing Fancy
Cooling: Fans
Hard Drives: 931GB TOSHIBA DT01ACA100 (SATA) 238GB TEAM TM8PS7256G (SATA SSD)
Internet Speed: 25 Mbps
Quote
Related Discussions
I am receiving random BSOD with two different bug check strings.
MEMORY_MANAGEMENT
PAGE_FAULT_IN_NONPAGED_AREA
I have updated all of my drivers. I have checked the memory with memcheck both by running it with both sticks installed and one stick installed (both sticks singly). I have checked...
The BSODs do not seem to happen at any specific time.
The computer is an HP with a Pegatron 2A86 Mobo.
I plan on running MemTest86 and will have images uploaded tonight.
For now, here are my WhoCrashed logs and (attached) is the SF files.
Thank you in advance for any help. My...
Hello,
A couple weeks ago i bought a brand new notebook (a Lenovo G470, running Windows 7 Home Premium x64 ) and a few days ago, it started BSOD'ing, to the point that it was impossible to use the computer because the BSOD happened almost every time.
The BSOD all had random error codes and...
Hello,
i'm having random bsod on my pc since I bought it 2 years ago.
Some of the BSOD errors are IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe, NTFS_FILE_SYSTEM Ntfs.sys and BAD_POOL_CALLER fileinfo.sys.
The frequency is random, sometimes it runs fine for over a week, and sometimes i have 2 bsod a day....
Hi,
I have been randomly receiving BSODs for quite some time however it appears to be occurring with more frequency now. There hasn't been a specific program running that appears to be linked to the BSOD. Through Event Viewer, the report blames fltmgr.sys and ntoskrnl.exe for the BSOD with a bug...