2.5.0 and 2.4.0
6GB L1 READ&WRITE
Windows 10 Anniversary
(CPU-i7/Gigabyte Z170XP-SLI-Motherboard/16GB-Memory/Many-Harddisks):
Both versions make Windows unbootable until Windows removes PrimoCache on a repair
BSOD 2.5.0 and 2.4.0 BAD_POOL_CALLER Topic is solved
Re: BSOD 2.5.0 and 2.4.0 BAD_POOL_CALLER
I'd appreciate it if you can answer my questions about this problem.
1) Did you install these two versions before Windows 10 Anniversary build? If yes, did this kind of problem happen?
2) Did you try versions before 2.4.0? If yes, did this kind of problem happen?
1) Did you install these two versions before Windows 10 Anniversary build? If yes, did this kind of problem happen?
2) Did you try versions before 2.4.0? If yes, did this kind of problem happen?
Re: BSOD 2.5.0 and 2.4.0 BAD_POOL_CALLER
And do you remember the first parameter of BSOD "BAD_POOL_CALLER"? Or do you have a minidump file for the bsod?
Re: BSOD 2.5.0 and 2.4.0 BAD_POOL_CALLER
I'd appreciate it if you can answer my questions about this problem.
1) Did you install these two versions before Windows 10 Anniversary build? If yes, did this kind of problem happen?
I know 2.4.0 worked before Windows 10 updated to the Anniversary build and worked well.
I do not recall if I had updated to 2.5.0 on Windows 10.
2) Did you try versions before 2.4.0? If yes, did this kind of problem happen?
I have used 2.4.0 on this PC and it has worked well. I only have experienced issues this weekend. I did not upgrade to Windows 10 Anniversary myself so I am not exactly sure when it upgraded on its own.
My most recent try:
Running 2.5.0 on Win10 Ann installs fine.
System reboots fine.
I create cache ~7GB
The overhead is much much smaller than I am used to seeing (~50MB)
Once I enable the cache memory is allocated on task manager fine.
On reboot, I am unable to boot back into Win10 Ann
Win10 Ann tries to repair itself
Is unsuccessful but I select Advanced Options | Boot into Windows 10 and it works
I restored the system as many applications (including PrimoCache) is gone
I do not remember the first parameter of BSOD "BAD_POOL_CALLER".
I will look for a minidump file.
escaward
1) Did you install these two versions before Windows 10 Anniversary build? If yes, did this kind of problem happen?
I know 2.4.0 worked before Windows 10 updated to the Anniversary build and worked well.
I do not recall if I had updated to 2.5.0 on Windows 10.
2) Did you try versions before 2.4.0? If yes, did this kind of problem happen?
I have used 2.4.0 on this PC and it has worked well. I only have experienced issues this weekend. I did not upgrade to Windows 10 Anniversary myself so I am not exactly sure when it upgraded on its own.
My most recent try:
Running 2.5.0 on Win10 Ann installs fine.
System reboots fine.
I create cache ~7GB
The overhead is much much smaller than I am used to seeing (~50MB)
Once I enable the cache memory is allocated on task manager fine.
On reboot, I am unable to boot back into Win10 Ann
Win10 Ann tries to repair itself
Is unsuccessful but I select Advanced Options | Boot into Windows 10 and it works
I restored the system as many applications (including PrimoCache) is gone
I do not remember the first parameter of BSOD "BAD_POOL_CALLER".
I will look for a minidump file.
escaward
Re: BSOD 2.5.0 and 2.4.0 BAD_POOL_CALLER
I have the .dmp file but I am unsure how to get it to you. It won't attach in the forum.
escaward
UPDATE:
I sent my minidmp file to [email protected] via email.
escaward
UPDATE:
I sent my minidmp file to [email protected] via email.
Re: BSOD 2.5.0 and 2.4.0 BAD_POOL_CALLER
Yes, we have got the minidump file. Thank you very much for your information!
Recently we're working a new version to see if it solves all strange problems in Windows 10 anniversary build. I'll keep you updated.
Recently we're working a new version to see if it solves all strange problems in Windows 10 anniversary build. I'll keep you updated.
Re: BSOD 2.5.0 and 2.4.0 BAD_POOL_CALLER
Hello Support,
Has there been any update to this bug? I am unable to use either of my two PromiCache keys for fear of causing a complete wipe of my systems.
Regards,
Eric
Has there been any update to this bug? I am unable to use either of my two PromiCache keys for fear of causing a complete wipe of my systems.
Regards,
Eric
Re: BSOD 2.5.0 and 2.4.0 BAD_POOL_CALLER
We're still working on this version. We already find and fix some problems, and are still checking others. I'll notify you as soon as we release it.
Thank you!
Thank you!
Re: BSOD 2.5.0 and 2.4.0 BAD_POOL_CALLER
Hello Support,
Could you share any update? It has been a month.
Regards,
Eric
Could you share any update? It has been a month.
Regards,
Eric
Re: BSOD 2.5.0 and 2.4.0 BAD_POOL_CALLER
I'm sorry for the delay of the new version! Now the version 2.6.0 is ready. We plan to publish it within one or two days.
You can download it first from the following link before its release.
https://www.romexsoftware.com/download/ ... .Setup.zip
BTW, we checked this BSOD, it seems that the problem may be related to C-Media Sound Card driver (cmudaxp.sys). You may check if this driver is updated to the latest version.
Thank you for the patience!
You can download it first from the following link before its release.
https://www.romexsoftware.com/download/ ... .Setup.zip
BTW, we checked this BSOD, it seems that the problem may be related to C-Media Sound Card driver (cmudaxp.sys). You may check if this driver is updated to the latest version.
Thank you for the patience!