NickM Posted May 1, 2018 Share Posted May 1, 2018 Maybe not a DP issue, but yesterday I updated 2 machines to Windows 10 April 2018. Both appeared to run normally, but I get an immediate BSOD on the DP machine with "BAD_POOL_HEADER". The Internet says it's either bad RAM (I'm current running MEMCHECK on the DP machine) or a bad driver. Has anyone else had a similar problem? I haven't yet reinstalled DP and scanner, or reverted to pre-update Windows. Edit 1: I do run MalwareBytes on the crashing machine, shall remove it and see what happens. Quote Link to comment Share on other sites More sharing options...
0 Christopher (Drashna) Posted May 9, 2018 Share Posted May 9, 2018 13 hours ago, aniel said: i have to add that accessing the pool over lan/wan via ftp issue does not happen. From the dumps, that sounds consistent, as "SRV2" is the network share "stack"/driver. I think you already have, but try disable Network IO Boost, if you haven't. 13 hours ago, seanvree said: so me getting a BSOD right when I create a folder on network folder where the target is a DrivePool drive is totally different? That sounds different, but .... hard to tell. Enable verifier, get a new memory dump, open a ticket and let us know. Just in case. 19 hours ago, PocketDemon said: +1 on the "BAD_POOL_HEADER" issue on both machines with DP installed - support question raised as per the thread.  I think we already "resolved" yours actually!    For everyone, (will update main post), try this build: http://dl.covecube.com/DrivePoolWindows/rc/download/StableBit.DrivePool_2.2.1.925_x64_RC.exe  It may not fix the issue, but just in case.... stuza 1 Quote Link to comment Share on other sites More sharing options...
0 aniel Posted May 9, 2018 Share Posted May 9, 2018 i took a look at StableBit.DrivePool_2.2.1.925_x64_RC.exe changelog and no mention of this issue being fixed, can you elaborate please? Quote Link to comment Share on other sites More sharing options...
0 Christopher (Drashna) Posted May 9, 2018 Share Posted May 9, 2018 3 minutes ago, aniel said: i took a look at StableBit.DrivePool_2.2.1.925_x64_RC.exe changelog and no mention of this issue being fixed, can you elaborate please? * [Issue #27818] [D] Fixed bug in filename normalization after FileNameInformation query, when dealing with root directories.  But this may not be related to the issue here. In fact, it's probably not. But .... just in case. Quote Link to comment Share on other sites More sharing options...
0 aniel Posted May 9, 2018 Share Posted May 9, 2018 is that your elaboration, i mean im not trying to be rude or anything but im not willing to crash my $1500 gaming computer one more time base on a "It may not fix the issue, but just in case...." Quote Link to comment Share on other sites More sharing options...
0 Christopher (Drashna) Posted May 9, 2018 Share Posted May 9, 2018 No, you're not being. Sorry, I'm usually more verbose. Specifically, this code change is in regards to a crash dump that somebody did upload, and that the verifier did catch an issue, actually. And the crash type in question was the "bad pool header" crash. So on the off chance that this is related, or even the same issue. And no, it shouldn't cause the system to crash (at least any more that what you're already seeing). But since we can't really test it, because we're not seeing/experiencing the crashes.... there is no way to tell for certain if this is related to what you're seeing, or not. Quote Link to comment Share on other sites More sharing options...
0 aniel Posted May 9, 2018 Share Posted May 9, 2018 ok fair enough, im going to download, install, test and upload a new dump if it crashes. Quote Link to comment Share on other sites More sharing options...
0 aniel Posted May 9, 2018 Share Posted May 9, 2018 im happy to announce that so far issue seen to have been fixed. note: did install windows update KB4103721 that was available after rebooting, whether or not it contributed to the fix, idk, no mention in the change log. but im happy issue seen to be fixed Quote Link to comment Share on other sites More sharing options...
0 PocketDemon Posted May 10, 2018 Share Posted May 10, 2018 Touch wood the new version (2.2.1.926 - didn't try the RC as the later version was there) has resolved the issue on both machines. Many thanks for the prompt action. Quote Link to comment Share on other sites More sharing options...
0 Bren Posted May 10, 2018 Share Posted May 10, 2018 Today's update is fixed for me as well. Thanks. Quote Link to comment Share on other sites More sharing options...
0 seanvree Posted May 10, 2018 Share Posted May 10, 2018 fixed for me as well. Thanks! Quote Link to comment Share on other sites More sharing options...
0 stuza Posted May 10, 2018 Share Posted May 10, 2018 15 hours ago, Christopher (Drashna) said: for everyone, (will update main post), try this build: http://dl.covecube.com/DrivePoolWindows/rc/download/StableBit.DrivePool_2.2.1.925_x64_RC.exe  It may not fix the issue, but just in case.... All fixed. Thank you very much for the swift work and resolution! Quote Link to comment Share on other sites More sharing options...
0 Christopher (Drashna) Posted May 10, 2018 Share Posted May 10, 2018 Awesome!  I'm glad to hear it! 20 hours ago, aniel said: im happy to announce that so far issue seen to have been fixed. note: did install windows update KB4103721 that was available after rebooting, whether or not it contributed to the fix, idk, no mention in the change log. but im happy issue seen to be fixed So, it sounds like that fix before was the cause here. And we were only able to catch it because of the Verifier being enabled. Quote Link to comment Share on other sites More sharing options...
0 aniel Posted May 10, 2018 Share Posted May 10, 2018 45 minutes ago, Christopher (Drashna) said: Awesome!  I'm glad to hear it! So, it sounds like that fix before was the cause here. And we were only able to catch it because of the Verifier being enabled. ...and u lost me there. Quote Link to comment Share on other sites More sharing options...
0 MadSquabbles Posted May 11, 2018 Share Posted May 11, 2018 Fixed here too. Thanks guys! Quote Link to comment Share on other sites More sharing options...
Question
NickM
Maybe not a DP issue, but yesterday I updated 2 machines to Windows 10 April 2018.
Both appeared to run normally, but I get an immediate BSOD on the DP machine with "BAD_POOL_HEADER".
The Internet says it's either bad RAM (I'm current running MEMCHECK on the DP machine) or a bad driver.
Has anyone else had a similar problem?
I haven't yet reinstalled DP and scanner, or reverted to pre-update Windows.
Edit 1: I do run MalwareBytes on the crashing machine, shall remove it and see what happens.
Link to comment
Share on other sites
Top Posters For This Question
14
11
10
6
Popular Days
May 9
11
May 3
10
May 4
10
May 7
8
Top Posters For This Question
NickM 14 posts
aniel 11 posts
Christopher (Drashna) 10 posts
Jaga 6 posts
Popular Days
May 9 2018
11 posts
May 3 2018
10 posts
May 4 2018
10 posts
May 7 2018
8 posts
Popular Posts
aniel
im glad im not the only one, im have the same exact issues and i already opened a ticket, hopefully they fix it soon
Christopher (Drashna)
Hopefully!
NickM
I reverted the DP machine to the previous Windows build (1709 + updates), which now has DP 2.2.0.922 on it. The machine I'm copying FROM still has 1803 on it. I've copied several files from
64 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.