Bitcoin Forum
June 15, 2024, 11:02:05 PM *
News: Voting for pizza day contest
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: mining rig crash - ntoskrnl  (Read 219 times)
Sn1p3r (OP)
Newbie
*
Offline Offline

Activity: 48
Merit: 0


View Profile
October 22, 2017, 06:27:44 PM
 #1

Hello,

first Im sorry if this is wrong place for such inquiry.

6x 1060 6GB
2x 650w PSU

I would need help with this issue, rig was working for days without problem.

Quote



==================================================
Dump File         : 102217-31000-01.dmp
Crash Time        : 10/22/2017 17:47:37
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff800`13056154
Parameter 3       : ffff9901`b188d800
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+16c580
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 10.0.15063.674 (WinBuild.160101.0800)
Processor         : x64
Crash Address     : ntoskrnl.exe+16c580
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\102217-31000-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 15063
Dump File Size    : 559,796
Dump File Time    : 10/22/2017 17:49:28
==================================================




Just please advice on how to handle this.

Thanks
leonix007
Sr. Member
****
Offline Offline

Activity: 1008
Merit: 297


Grow with community


View Profile
October 23, 2017, 09:47:30 AM
 #2

Hello,

first Im sorry if this is wrong place for such inquiry.

6x 1060 6GB
2x 650w PSU

I would need help with this issue, rig was working for days without problem.

Quote



==================================================
Dump File         : 102217-31000-01.dmp
Crash Time        : 10/22/2017 17:47:37
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff800`13056154
Parameter 3       : ffff9901`b188d800
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+16c580
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 10.0.15063.674 (WinBuild.160101.0800)
Processor         : x64
Crash Address     : ntoskrnl.exe+16c580
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\102217-31000-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 15063
Dump File Size    : 559,796
Dump File Time    : 10/22/2017 17:49:28
==================================================




Just please advice on how to handle this.

Thanks

Seems like a driver issue to me, check if you are using windows 10, its possible that you are a victim of OS Updates lately, try to uninstall and reinstall latest driver of your GPU, don't forget to turn off your OS update.

https://bitcointalk.org/index.php?topic=2283625.0

xxcsu
Hero Member
*****
Offline Offline

Activity: 1498
Merit: 597


View Profile WWW
October 23, 2017, 10:17:20 AM
 #3

did you set the page file for at least 16GB or more ?

This error might linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

Learn about Merit & new rank requirements , Learn how to use MERIT , make this community better
If you like the answer you got for your question from any member ,
If you find any post useful , informative use the +Merit button.
Sn1p3r (OP)
Newbie
*
Offline Offline

Activity: 48
Merit: 0


View Profile
October 23, 2017, 11:16:58 AM
 #4

Thank you guys for your suggestions.

I have two identical machines running one next to each other, with same hardware and same windows installed and identical settings.
so far I noticed it could be an RAM issue.

Second machines doesn't have any problem at all after all updates. I plugged my spare 2GB ram cookie and will see how it will go now.
I will definately now disable windows updates.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!