Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Random BSoDs, different stop codes each time


  • Please log in to reply
1 reply to this topic

#1 fastlane22

fastlane22

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:05:14 PM

Posted 12 April 2018 - 01:26 AM

Custom Build

Windows 10 Version 1709 

(OS Build 16299.371)

x64 bit

PC build Oct 2016

i5-6600k 3.5 Ghz CPU

Nvidia GeForce GTX 1060 6GB GPU

Gigabyte Z170X Gaming 5 Mobo

Corsair RM650x PSU

 

I built my PC about a year and a half ago and up until a two weeks ago, everything had run fairly smoothly. I don't know what precipitated the crashes, but lately I've been hit with a rash of them. Always a different error code. Sometimes just minutes after booting up, sometimes hours after playing a game or just web browsing. My PC also tends to just take forever to reboot, always seeming to loop thru starting to autofix the boot error and then restarting to boot again and this can go on for hours. 


On Wed 4/11/2018 8:50:05 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041118-7156-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF80B9E63AE6A) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80B9E63AE6A, 0xFFFFD50CD5BF7598, 0xFFFFD50CD5BF6DE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch. 
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 a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Wed 4/11/2018 8:50:05 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (0xFFFFF80B9E63AE6A) 
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80B9E63AE6A, 0xFFFFD50CD5BF7598, 0xFFFFD50CD5BF6DE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch. 
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Wed 4/11/2018 7:35:09 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041118-7437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175930) 
Bugcheck code: 0x19 (0xD, 0xFFFFCD03C0F4A000, 0x7F20F6EC3FDF675A, 0x2F30D32102198C97)
Error: BAD_POOL_HEADER
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 pool header is corrupt. 
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue). 
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 4/11/2018 7:00:11 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041118-8468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175930) 
Bugcheck code: 0x1A (0x61941, 0xE1DE7FF528, 0xD, 0xFFFFC6033781FA00)
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. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue). 
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 4/11/2018 6:35:56 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041118-6687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175930) 
Bugcheck code: 0xA (0xFFFFCA841FA5D010, 0x2, 0x0, 0xFFFFF8035E6EBEFF)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug. 
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. 
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 4/11/2018 5:42:40 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041118-6703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175930) 
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFF928542D1F860, 0xFFFF8288F6586450)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
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 video scheduler has detected a fatal violation. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 


HD Tune:         Crucial_CT525MX3 Error Scan

 
Scanned data   : 500586 MB
Damaged Blocks : 0.0 %
Elapsed Time   : 36:06
 
HD Tune:         Crucial_CT525MX3 Benchmark
 
Transfer Rate Minimum : 243.7 MB/sec
Transfer Rate Maximum : 360.9 MB/sec
Transfer Rate Average : 275.8 MB/sec
Access Time           : 0.2 ms
Burst Rate            : 154.9 MB/sec
CPU Usage             : 10.3%
 

 

Looking for help as this is driving me crazy.

Thanks for your time.

 
 



BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 2,955 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:06:14 PM

Posted 17 April 2018 - 10:23 AM

Can you follow

 

https://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/

 

and attach the requested files directly here in your next reply? Sorry for the late response.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users