BAD_POOL_CALL when using Win32DiskImager

  1.    23 Mar 2016 #1

    BAD_POOL_CALL when using Win32DiskImager

    it's happened twice this month but what i was running along w/ Win32DiskImager was different each crash i havent looked at the crashdumps but Maybe USB Driver issue? because this issue wasnt present in the pre-release Insider preview builds or while i was still on Windows 8.1 (i'd attach the proper dump but the Collection tool is only making 1kb empty zips. )

    Attachment 71054
    Attachment 71055

    the version of the win32DiskImager i have been using each crash is also attached, the raw Dumps are attached as ""

    GPU Driver Version: 364.51 (NVidia Gefore driver vers)
    GPU: MSI GTX 760OC
    HDD: WD Black 1TB
    Ram: PC1333-8GB "Microcenter" brand (2x 2GB+ 1x4GB stick)
    PSU:750W OCZ Modular
    CPU: AMD APU A10-7850k @ Stock 3.7GHZ
    OS: Windows 10 Pro "Ver 1511" (Build 10586.164)
    LAN Driver: 9.1.402.2015 (realTek)
    Secondary Lan: VirtualBox "Host-Only" Adapter
    Mobo: Gigabyte GA-F2A88XM-D3H FM2+/FM2 mATX AMD Motherboard
    Sound Driver Ver: (realTek)
    Selected Sound output @ crashes: GPU HDMI out

    Hope this is enough info despite i cant get the crash dump collectin tool to work.
      My ComputerSystem Spec

  2. axe0's Avatar
    Posts : 13,819
    Windows 10 Pro
       23 Mar 2016 #2

    BAD_POOL_CALL when using Win32DiskImager Diagnostic Test BAD_POOL_CALL when using Win32DiskImager

    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My ComputersSystem Spec


Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 19:06.
Find Us