Guitar pro causes BSOD

[MrGent]

Hello!

I wonder if you guys can help me.
Whenever I install Guitar Pro 5.2 it causes a Bad Pool Header Blue Screen of Death (even in safe mode).

Performing a System Restore to an earlier version removes the error but I want to use the software!!

I am running Windows 7. Minidump files attached - Any help interpreting these and finding a cure would be much appreciated.

Many Thanks,
MrGent

 

[Arc]

Hello MrGent.

You have supplied two crash dumps, and both of those results the same.

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR=Red][B]BAD_POOL_HEADER (19)[/B][/COLOR]
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, [COLOR=Red]and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.[/COLOR]
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffff900c29fc000, The pool entry we were looking for within the page.
Arg3: fffff900c29fc240, The next pool entry.
Arg4: 0000000025240000, (reserved)

Debugging Details:
------------------


BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800024fd100
GetUlongFromAddress: unable to read from fffff800024fd1c0
 fffff900c29fc000 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800023f8cae to fffff800022cdfc0

STACK_TEXT:  
fffff880`05faeef8 fffff800`023f8cae : 00000000`00000019 00000000`00000020 fffff900`c29fc000 fffff900`c29fc240 : nt!KeBugCheckEx
fffff880`05faef00 fffff960`00049425 : 00000000`007104a6 00000000`00000000 fffff880`64667454 fffff880`05faf050 : nt!ExDeferredFreePool+0x12da
fffff880`05faefb0 fffff960`00051e1c : 00000000`007104a6 fffff880`05faf060 00000000`00000000 00000000`00710012 : win32k!EngFreeMem+0x21
fffff880`05faefe0 fffff960`0004916b : fffff900`c2b75940 00000000`00000001 00000000`00000001 00000000`00000000 : win32k!bLoadGlyphSet+0x104
fffff880`05faf010 fffff960`0004930a : fffff900`c2b75940 fffff900`00000001 fffff900`c2b75940 fffff960`001bb564 : win32k!bReloadGlyphSet+0x24b
fffff880`05faf6d0 fffff960`00049262 : 00000000`00000000 fffff900`c2b75940 fffff900`00000001 fffff900`c2bf7564 : win32k!ttfdQueryFontTree+0x66
fffff880`05faf720 fffff960`00096013 : fffff960`00049208 fffff900`c2b75c70 00000000`00000001 00000000`00000000 : win32k!ttfdSemQueryFontTree+0x5a
fffff880`05faf760 fffff960`00095eb3 : fffff880`05faf870 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!PDEVOBJ::QueryFontTree+0x63
fffff880`05faf7e0 fffff960`00050066 : fffff900`c0091000 00000000`00000000 00000000`00000002 00000000`00000000 : win32k!PFEOBJ::pfdg+0xa3
fffff880`05faf840 fffff960`000aa61c : fffff900`c2bf7450 fffff880`05fafad0 fffff880`05faf9d0 fffff880`05fafb20 : win32k!RFONTOBJ::bRealizeFont+0x46
fffff880`05faf960 fffff960`0007b0e5 : 00000000`10018000 fffff900`00000000 00000373`00000000 02c06400`00000002 : win32k!RFONTOBJ::bInit+0x548
fffff880`05fafa80 fffff960`0007b07b : 00000000`00000000 fffff880`05fafca0 00000000`70616d63 00000408`07414800 : win32k!ulGetFontData2+0x31
fffff880`05fafaf0 fffff960`0007af51 : 00000000`ffffffff 00000000`ffffffff 00000000`00000000 fffff880`05fafb70 : win32k!ulGetFontData+0x7f
fffff880`05fafb40 fffff800`022cd253 : 00000000`68010373 00000000`00000000 00000000`001edc38 00000000`00000000 : win32k!NtGdiGetFontData+0x4d
fffff880`05fafbb0 00000000`74480b4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001edc18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74480b4a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!EngFreeMem+21
fffff960`00049425 4883c420        add     rsp,20h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  win32k!EngFreeMem+21

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50aeecc6

FAILURE_BUCKET_ID:  X64_0x19_20_win32k!EngFreeMem+21

BUCKET_ID:  X64_0x19_20_win32k!EngFreeMem+21

Followup: MachineOwner
---------

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Also, upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

 

[fireberd]

The current version is 6. Their site doesn't list what 5.2 is compatible with.

 

[MrGent]

Thanks for your reply, using the verifier caused a different type of blue screen.

Minidump and MsInfo file attached.

Cheers,
MrGent
​

 

[Arc]

Hello MrGent.

This latest crash is indicating to AMD USB Filter Driver, which is a part of the chipset drivers. You may searh for updates in http://support.amd.com/us/Pages/AMDSupportHub.aspx.

Lot of other USB errors are also present there.

fffff880`033d34a0  fffff880`05a0adb8 USBPORT!USBPORTBUSIF_UsbdBusInterfaceReference
fffff880`033d34a8  fffff880`05a0adc8 USBPORT!USBPORTBUSIF_UsbdBusInterfaceDereference
fffff880`033d34b0  fffff880`05a0d244 USBPORT!USBPORTBUSIF_UsbdBusGetUSBDIVersion
fffff880`033d34b8  fffff880`05a0d2e0 USBPORT!USBPORTBUSIF_UsbdBusQueryBusTime
fffff880`033d34c0  fffff880`05a0c170 USBPORT!USBPORTBUSIF_UsbdBusSubmitIsoOutUrb
fffff880`033d34c8  fffff880`05a0ce20 USBPORT!USBPORTBUSIF_UsbdBusQueryBusInformation
fffff880`033d34d0  fffff880`05a0cde4 USBPORT!USBPORTBUSIF_UsbdIsDeviceHighSpeed

Do some general USB related troubleshooting. For the port, first, uninstall and reinstall the USB ports drivers.

1. Right click on Computer icon > manage. It will open the computer management window.
2. Click on "Device Manager" in the left pane, it will list all installed devices up.
3. Expand "USB Serial Bus Controllers" by clicking on the triangle in front of it.
4. Click on one item to select, then right click and uninstall.
5. Do the same for all.
6. Restart the computer.
7. At restart, windows will auto configure the appropriate drivers.

And, Disable USB Selective Suspense too.
USB Selective Suspend - Turn On or Off

For the devices, first, detach all the USB devices other than the keyboard and mouse.
Then, Update the drivers for them all, including the keyboard and mouse, if any third party drivers are installed for them. Sometimes, the USB errors are also caused by some special type of malwares that I have experienced. So, scan the system for possible virus infection.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Norton Internet Security is also contributing to your crash.

fffff880`033d3c48  fffff880`044c59efUnable to load image [URL="http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys"]IDSvia64.sys[/URL], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys"]IDSvia64.sys[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=IDSvia64.sys"]IDSvia64.sys[/URL]
 IDSvia64+0x179ef

Uninstall Norton and all Symentec products using Norton Removal tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download and install and update those, and then run full system scans with both of them, one by one.


And, Have you ever made a clean install in these years? Let us know. You have some factory bloatware installed over time.