Sp0iLedBrAt Posted January 9, 2010 Posted January 9, 2010 I chose to post here because this is more a software than a hardware problem.BTtray.exe reported that it could not start BTStackServer.exe, so I hit google search. There were a few solutions offered, like disabling BTtray.exe from MSCONFIG, reinstalling drivers, virus scans etc., but none worked. The driver version is 5.5.0.5700 by Broadcom (supplied by HP as HP Integrated Module with Bluetooth 2.1 Wireless Technology), dated 12/5/2008.Finally, I opened Program files\WIDCOMM\Bluetooth software and located BTStackServer.exe. Double-clicking revealed a new error 0xc0000005, which I traced through search as memory access violation, and I just don't know how to deal with that. It may help that the same error occurred a few days ago (still present) on sndvol32.exe, i.e. Volume.I would really appreciate any suggestion.P.S. Info: HP Compaq 615 Notebook PC with XP 32-bit, AMD Turion x2 Mobile at 2.2 GHz, 2 GB of DDR2 RAM, ATI Radeon HD3200
cluberti Posted January 9, 2010 Posted January 9, 2010 If you run process monitor and then double-click the .exe, does the process monitor log show any access denied errors?
Sp0iLedBrAt Posted January 10, 2010 Author Posted January 10, 2010 Well, I didn't see any specific "Access denied" errors, but there were plenty "Not found" markers for files and registry keys; so, I'm uploading the results for that process in hope it will mean more to some of you than it means to me.Thanks again
cluberti Posted January 10, 2010 Posted January 10, 2010 It looks like the error is indeed an access violation, and it's happening after BTStackServer.exe finishes loading wdmaud.drv and starts to initialize it. We can see in the procmon it looks through the Image File Execution Options keys, and then abruptly bails - and we can also tell it's likely not a permissions or access error, but perhaps a problem with something in the binary itself based on what it's reading in from the registry. Procmon won't tell us any more than it has, only a crash dump of the .exe failing will tell us more. What I would suggest is downloading and installing the debugging tools for windows, creating a folder called c:\adplus, then opening a command prompt, changing to the directory you installed the Debugging Tools into (usually C:\Program Files\Debugging Tools for Windows (x86)\), and then executing the following command:cscript adplus.vbs -crash -quiet -o c:\adplus -sc C:\Program Files\WIDCOMM\Bluetooth Software\BTStackServer.exeIf it succeeds, it should spawn the BTStackServer.exe binary, dump it when it crashes, and create a folder structure inside C:\adplus that contains some .txt files, a .dmp file (at least one, maybe more), and a few other things. If it does, we can look at the contents of that folder for clues as to why it's failing.
Sp0iLedBrAt Posted January 10, 2010 Author Posted January 10, 2010 It worked like a charm, and since there were quite a lot of files (over 60MB), I used 7-zip (now app. 7.5MB) and uploaded to THIS LINK.Thank you for your productive ideas.
cluberti Posted January 10, 2010 Posted January 10, 2010 It's definitely failing when interacting with wdmaud.drv - the stack is read from the bottom up, with the lowest line being the oldest command, and the topmost line being the most recent:7c96f07c ntdll!RtlDebugAllocateHeap+0x2817c96e5df ntdll!RtlpValidateHeap+0x207c94b871 ntdll!RtlAllocateHeapSlowly+0xd7c7c91927d ntdll!RtlAllocateHeapSlowly+0xdc17c96f098 ntdll!RtlDebugAllocateHeap+0x2987c91c368 ntdll!`string'+0x3c7c915239 ntdll!bsearch+0x427c91542b ntdll!RtlpLocateActivationContextSection+0x15a7c9157c1 ntdll!RtlpFindUnicodeStringInSection+0x7b7c92218a ntdll!`string'+0x127c9354a8 ntdll!LdrpRunInitializeRoutines+0x4e67c90e9f5 ntdll!_except_handler3+0xd57c9032e3 ntdll!ExecuteHandler2+0x617c92accd ntdll!RtlUnwind+0x12f7c90d06a ntdll!NtContinue+0xc7c92acf6 ntdll!RtlUnwind+0xb800400018 BTStackServer+0x1800720072 BTStackServer+0x320072006e0065 BTStackServer+0x2e006500560074 BTStackServer+0x16007400720065 BTStackServer+0x32006500690073 BTStackServer+0x290073006e006f BTStackServer+0x2e006f0049005c BTStackServer+0x9005c00650067 BTStackServer+0x25006700460020 BTStackServer+0x60020006c0069 BTStackServer+0x2c006900780045 BTStackServer+0x38004500630065 BTStackServer+0x23006500740075 BTStackServer+0x340075006f0069 BTStackServer+0x2f00690070004f BTStackServer+0x30004f00690074 BTStackServer+0x290074006e0000 BTStackServer+0x2e0000005c003b BTStackServer+0x1c003b00700023 BTStackServer+0x300023006c0023 BTStackServer+0x2c00237c916b1e ntdll!LdrpUpdateLoadCount3+0x6f7c97e360 ntdll!DefaultExtension+0x07c916b99 ntdll!LdrpUpdateLoadCount3+0x5177c916ba5 ntdll!LdrpUpdateLoadCount3+0x5237c90eadc ntdll!_NLG_Return2+0x07c914ff1 ntdll!RtlAppendUnicodeStringToString+0x457c90d5da ntdll!ZwOpenKey+0xc7c91cbd0 ntdll!LdrpOpenImageFileOptionsKey+0xf77c91cbda ntdll!LdrpOpenImageFileOptionsKey+0x1010052005c BTStackServer+0x12005c00670065 BTStackServer+0x27006500730069 BTStackServer+0x33006900720074 BTStackServer+0x320074005c0079 BTStackServer+0x1c00790061004d BTStackServer+0x21004d00680063 BTStackServer+0x280063005c0065 BTStackServer+0x1c006500630069 BTStackServer+0x230069006f0072 BTStackServer+0x2f0072006f0073 BTStackServer+0x2f0073006e0069 BTStackServer+0x2e0069006f0064 BTStackServer+0x2f006400730077 BTStackServer+0x330077004e0020 BTStackServer+0xe0020005c0054 BTStackServer+0x1c005400750043 BTStackServer+0x3500437c90d98a ntdll!NtQueryVirtualMemory+0xc7c938392 ntdll!_ValidateEH3RN+0xb67c90ea39 ntdll!_global_unwind2+0x187c90ea41 ntdll!_global_unwind2+0x207c940f3c ntdll!_LdrpInitialize+0x1e67c90e9b3 ntdll!_except_handler3+0x937c90e9c9 ntdll!_except_handler3+0xa97c915fac ntdll!LdrpCheckForLoadedDll+0x60872d202a8 wdmaud!_imp__GetSecurityDescriptorDacl <PERF> +0x07c97e2f0 ntdll!LdrpHashTable+0x907c903400 ntdll!$$VProc_ImageExportDirectory+0x07c90e48a ntdll!KiUserExceptionDispatcher+0xe7c9100e8 ntdll!RtlAllocateHeap+0x247c9158ff ntdll!RtlDecodeSystemPointer+0x45b7c915bf8 ntdll!RtlDosApplyFileIsolationRedirection_Ustr+0x3467c915c5d ntdll!RtlDosApplyFileIsolationRedirection_Ustr+0x3de7c97e214 ntdll!DllExtension+0xc72d21250 wdmaud!`string'+0x07c94b1b0 ntdll!RtlpCoalesceFreeBlocks+0x3ed7c92770a ntdll!RtlFreeHeapSlowly+0x3a07c912d04 ntdll!LdrLockLoaderLock+0x1d27c912d78 ntdll!LdrUnlockLoaderLock+0xb17c9101e0 ntdll!CheckHeapFillPattern+0x54779269f8 setupapi!pSetupMalloc+0x167792adaf setupapi!AllocateDeviceInfoSet+0xe7792ad3a setupapi!SetupDiCreateDeviceInfoListExW+0x2e7792ad90 setupapi!MiniIconXlate+0x1287792b37d setupapi!SetupDiGetClassDevsExW+0xc47c96f8e8 ntdll!RtlDebugFreeHeap+0x2127c96f8f0 ntdll!`string'+0x3c7c96f8cc ntdll!RtlDebugFreeHeap+0x1fb7c94bc4c ntdll!RtlFreeHeapSlowly+0x377c927788 ntdll!CheckHeapFillPattern+0x3c7c927784 ntdll!RtlFreeHeapSlowly+0x5c27c927573 ntdll!RtlFreeHeap+0xf97c9148bb ntdll!RtlQueryEnvironmentVariable_U+0x1637c910435 ntdll!RtlAcquirePebLock+0x287c91043e ntdll!RtlAcquirePebLock+0x317c901000 ntdll!RtlEnterCriticalSection+0x07c914606 ntdll!RtlQueryEnvironmentVariable_U+0x6f7c910460 ntdll!RtlReleasePebLock+0xf7c914679 ntdll!RtlQueryEnvironmentVariable_U+0x3247c917ef3 ntdll!LdrpSnapThunk+0xbd77922074 setupapi!$$VProc_ImageExportDirectory+0x984779229d0 setupapi!$$VProc_ImageExportDirectory+0x12e0779200d8 setupapi!_imp__RegEnumKeyExW <PERF> +0x07c917dba ntdll!LdrpGetProcedureAddress+0x18672d211d8 wdmaud!`string'+0x07c80ae40 kernel32!GetProcAddress+0x07c80e0e8 kernel32!`string'+0x58779216f0 setupapi!$$VProc_ImageExportDirectory+0x077920000 setupapi!_imp__RegEnumKeyExW <PERF> +0x07792b5e9 setupapi!SetupDiGetClassDevsW+0x07c910060 ntdll!CheckHeapFillPattern+0x647c91005d ntdll!RtlFreeHeap+0x6477c801bea kernel32!LoadLibraryExW+0x1e972d2128c wdmaud!KSCATEGORY_WDMAUD+0x107c917e10 ntdll!`string'+0xc7c917e09 ntdll!LdrpGetProcedureAddress+0xa67c917ec0 ntdll!LdrGetProcedureAddress+0x187792fc29 setupapi!_except_handler3+0x07792b5d8 setupapi!MiniIconXlate+0x1c87792b604 setupapi!SetupDiGetClassDevsW+0x1b72d23cbf wdmaud!wdmaGetGlobalDeviceInterfaceViaSetupAPI+0x4772d23dfa wdmaud!wdmaOpenKernelDevice+0x1672d24421 wdmaud!DrvInit+0x1b72d2178f wdmaud!DriverProc+0x072d24f40 wdmaud!_except_handler3+0x072d21270 wdmaud!`string'+0x2072d217ad wdmaud!DriverProc+0x1e76b431e9 winmm!InternalBroadcastDriverMessage+0xc47c9010e0 ntdll!RtlLeaveCriticalSection+0x076b60160 winmm!DriverListCritSec+0x07c80ff22 kernel32!GlobalUnlock+0x076b43138 winmm!DrvSendMessage+0x1876b430cf winmm!InternalLoadDriver+0x1b176b42e87 winmm!InternalOpenDriver+0x3272d20000 wdmaud!_imp__GetSecurityDescriptorDacl <PERF> +0x076b609bc winmm!guTotalMixerDevs+0x076b606c0 winmm!midiindrvZ+0x07c8093b8 kernel32!BaseFormatObjectAttributes+0x227c90d19a ntdll!ZwCreateSemaphore+0xc7c81017b kernel32!CreateSemaphoreW+0x5f40000000 msi!MsiPreviewBillboardA+0x151c5a005a0058 BTStackServer+0x1a005877f65149 shlwapi!SHGlobalCounterCreateNamedA+0x6f77f65160 shlwapi!SHGlobalCounterCreateNamedA+0x987c918f21 ntdll!RtlAllocateHeap+0xe6440000060 msi!MsiPreviewBillboardA+0x151cba76b60220 winmm!ResolutionCritSec+0x07c919318 ntdll!CheckHeapFillPattern+0x247c91930f ntdll!RtlAllocateHeapSlowly+0x113b76b42e4c winmm!DrvOpen+0x1576b43886 winmm!mmDrvOpen+0x460057005c BTStackServer+0x17005c004e0049 BTStackServer+0xe0049004f0044 BTStackServer+0xf004400530057 BTStackServer+0x1300570073005c BTStackServer+0x33005c00730079 BTStackServer+0x33007900650074 BTStackServer+0x2500740033006d btosif+0x6d005c0032 BTStackServer+0x1c003200640077 BTStackServer+0x2400770061006d BTStackServer+0x21006d00640075 BTStackServer+0x2400750064002e BTStackServer+0x24002e00760072 BTStackServer+0x3600727c915f75 ntdll!LdrpCheckForLoadedDll+0xe37c910000 ntdll!RtlFreeHeap+0x1a47c910323 ntdll!RtlpImageNtHeader+0x567c910385 ntdll!RtlImageDirectoryEntryToData+0x577c9000d0 ntdll!RtlDosPathSeperatorsString <PERF> +0x07c92ab21 ntdll!RtlLookupFunctionTable+0xae7c90e959 ntdll!_except_handler3+0x397c9032a8 ntdll!ExecuteHandler2+0x267c9032bc ntdll!ExecuteHandler2+0x3a7c90327a ntdll!ExecuteHandler+0x247c92aa0f ntdll!RtlDispatchException+0xb1006f0053 BTStackServer+0x2f005300740066 BTStackServer+0x34006600610077 BTStackServer+0x21007700650072 BTStackServer+0x250072004d005c BTStackServer+0xd005c7c80bb20 kernel32!lstrcpyW+0x1c76b6067a winmm!wszDrivers+0x127c80aa56 kernel32!lstrcmpiW+0x2076b60668 winmm!wszDrivers+0x076b43582 winmm!mmRegQuerySystemIni+0x1017c90d9ba ntdll!NtRaiseException+0xc7c90e4a5 ntdll!KiUserExceptionDispatcher+0x297c90e514 ntdll!KiFastSystemCallRet+0x07c809430 kernel32!BaseSetLastNTError+0x177c90ff2d ntdll!RtlFreeHeap+0x07c81113a kernel32!CreateFileW+0x3907c810800 kernel32!CreateFileW+0x00050005c BTStackServer+0x10005c77c40017 msvcrt!_vsnwprintf+0x307c9666c6 ntdll!RtlRaiseStatus+0x267c90d9ca ntdll!ZwRaiseHardError+0xc7c952b03 ntdll!LdrpInitializationFailure+0x2d7c940f7e ntdll!_LdrpInitialize+0x2417c919a48 ntdll!__security_init_cookie_ex+0x657c90e900 ntdll!_SEH_prolog+0x357c919a00 ntdll!__security_init_cookie_ex+0x97c90e920 ntdll!_except_handler3+0x07c91b030 ntdll!`string'+0xc87c90e457 ntdll!KiUserApcDispatcher+0x77c900000 ntdll!RtlDosPathSeperatorsString <PERF> +0x0004e703c BTStackServer+0xe703c7c810705 kernel32!BaseProcessStartThunk+0x000540042 BTStackServer+0x14004200540053 BTStackServer+0x14005300430000 BTStackServer+0x300000:000> u eipntdll!RtlRaiseStatus+0x26:7c9666c6 c9 leave7c9666c7 c20400 ret 47c9666ca 90 nop7c9666cb 90 nop7c9666cc 90 nop7c9666cd 90 nop7c9666ce 90 nopntdll!RtlRandom:7c9666cf 8bff mov edi,edi0:000> reax=0012fc54 ebx=00000000 ecx=0012fca8 edx=7c90e514 esi=c0000005 edi=00000000eip=7c9666c6 esp=0012fc54 ebp=0012fca4 iopl=0 nv up ei pl zr na pe nccs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246ntdll!RtlRaiseStatus+0x26:7c9666c6 c9 leave0:000> dc 0012fc54 L40012fc54 c0000005 00000001 00000000 7c9666c6 .............f.|0:000> lmvm wdmaudstart end module name72d20000 72d29000 wdmaud (pdb symbols) C:\Debuggers\sym\wdmdrv.pdb\CC3EC71E05C44E6595271A6773E15AF21\wdmdrv.pdb Loaded symbol image file: wdmaud.drv Image path: C:\WINDOWS\system32\wdmaud.drv Image name: wdmaud.drv Timestamp: Sun Apr 13 20:11:24 2008 (4802A12C) CheckSum: 0000CD88 ImageSize: 00009000 File version: 5.1.2600.5512 Product version: 5.1.2600.5512 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 3.9 Driver File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: WDMAUD.DRV OriginalFilename: WDMAUD.DRV ProductVersion: 5.1.2600.5512 FileVersion: 5.1.2600.5512 (xpsp.080413-2108) FileDescription: WDM Audio driver mapper LegalCopyright: © Microsoft Corporation. All rights reserved.0:000> lmvm BTStackServerstart end module name00400000 00781000 BTStackServer (no symbols) Loaded symbol image file: BTStackServer.exe Image path: C:\Program Files\WIDCOMM\Bluetooth Software\BTStackServer.exe Image name: BTStackServer.exe Timestamp: Thu Dec 11 17:18:23 2008 (494191AF) CheckSum: 0016FB7B ImageSize: 00381000 File version: 5.5.0.5800 Product version: 5.5.0.5800 File flags: 0 (Mask 3F) File OS: 4 Unknown Win32 File type: 1.0 App File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Broadcom Corporation. ProductName: Bluetooth Software InternalName: BTStackServer OriginalFilename: BTStackServer.exe ProductVersion: 5.5.0.5800 FileVersion: 5.5.0.5800 PrivateBuild: 5.5.0.5800 SpecialBuild: 5.5.0.5800 FileDescription: Bluetooth Stack COM Server LegalCopyright: Copyright 2000-2008, Broadcom Corporation. LegalTrademarks: Copyright 2000-2008, Broadcom Corporation. Comments: Copyright 2000-2008, Broadcom Corporation.At this point, it's hard to say what the BlueTooth driver wants with your audio driver, but it would seem there's some sort of access violation from applications attempting to use the audio mapper driver (hence why sndvol32.exe crashed as well, likely). It could be one of three things - if BTStackServer.exe isn't the only app crashing on the box, that could mean you need to run an sfc /scannow to repair something that's gone amok with the Windows files for audio mapping, it could mean you have malware (not likely, but still possible), or there's actually something wrong with your audio driver causing the wdmaud mapper to fail on heap operations. I'd actually start with making sure you remove and reinstall the latest certified audio drivers for your PC, then I'd check sfc /scannow to make sure you're in a supportable configuration. Last, I'd get the latest version of the BTStackServer drivers from Broadcom, here, to be sure.After that, if it still crashes, we can enable pageheap on BTStackServer.exe and get another dump the same way as before. To enable pageheap:1. Open the Debugging Tools for Windows folder from the start menu2. Click "Global Flags"3. Click the "Image File" tab4. Type "BTStackServer.exe" into the box (minus the quotes, of course)5. Press the TAB key6. Click the "Enable page heap" box7. Click the "OK" buttonOnce you've done that, use adplus to spawn and generate new dumps.
Sp0iLedBrAt Posted January 11, 2010 Author Posted January 11, 2010 Well, I un- and re-installed the audio driver (a newer one was not available) and the update app from Broadcom failed miserably as it didn't recognize the Bluetooth device at all. I managed to find and download (from a trusted site) a newer driver, which installed fine. The error repeated again, so I went for a new dump, but Command Prompt came out with a warning: C:\Program Files\Debugging Tools for Windows (x86)\adplus.vbs(3150, 5) (null): The event log file is full. So, how do I clear (or increase) the event log? I found a command !evlog clear, but where do I enforce it?BTW, I can't use SFC, as I'm out of the country and I don't have a Windows CD with me (nor an MSDN account). Will it make any difference if I download SP3 and replace (I guess it can be done in Safe Mode) wdmaud.drv ?I really feel we're getting somewhere, unlike many other people whose posts I read through the web, so I don't want the post to fall into oblivion.
cluberti Posted January 11, 2010 Posted January 11, 2010 If you have access to one, yeah, you can try it. Clearing the event log can be done manually from eventvwr.msc, by the way. If that doesn't help, omit the -quiet in the command line (it'll skip the call to LogEvent) - you'll get a warning prompt, but it's OK to ignore it and continue.
Sp0iLedBrAt Posted January 11, 2010 Author Posted January 11, 2010 I replaced wdmaud.drv in Safe Mode with a fresh one from SP3.cab, but it made no difference.HERE's another dump, this time with page heap enabled.
cluberti Posted January 12, 2010 Posted January 12, 2010 Well, it looks like there is indeed an issue on the system, but have a look at what happens when it goes to load and create a devicemap of audio drivers into memory:0:000> kBChildEBP RetAddr Args to Child 0012f194 779269f8 00000000 00000000 000000d8 ntdll!RtlAllocateHeap+0x240012f1a8 7792adaf 000000d8 00000000 00000000 setupapi!pSetupMalloc+0x160012f1b8 7792ad3a ffffffff 00000000 00000000 setupapi!AllocateDeviceInfoSet+0xe0012f1f0 7792b37d 00000000 00000000 00000000 setupapi!SetupDiCreateDeviceInfoListExW+0x2e0012f48c 7792b604 0012f4f4 00000000 00000000 setupapi!SetupDiGetClassDevsExW+0xc40012f4b0 72d23cbf 0012f4f4 00000000 00000000 setupapi!SetupDiGetClassDevsW+0x1b0012f508 72d23dfa 72d2178f 00000000 72d24421 wdmaud!wdmaGetGlobalDeviceInterfaceViaSetupAPI+0x470012f514 72d24421 72d2178f 00000000 00000000 wdmaud!wdmaOpenKernelDevice+0x160012f540 72d217ad 00000000 0012f578 76b431e9 wdmaud!DrvInit+0x1b0012f54c 76b431e9 00000000 00000001 00000002 wdmaud!DriverProc+0x1e0012f578 76b43138 00000000 00000002 00000000 winmm!InternalBroadcastDriverMessage+0xc40012f594 76b430cf 00000001 00000002 00000000 winmm!DrvSendMessage+0x180012f5c0 76b42e87 0012f990 72d20000 0012f5f0 winmm!InternalLoadDriver+0x1b10012f6f4 76b42e4c 0012f990 00000000 00000000 winmm!InternalOpenDriver+0x320012f70c 76b43886 0012f990 00000000 00000000 winmm!DrvOpen+0x150012f980 76b442d7 0012f990 76b609c0 00750061 winmm!mmDrvOpen+0x460012f9a0 76b44130 00000001 00000000 76b42b61 winmm!AuxInit+0x300012f9b0 76b4403e 00000001 0012fa04 76b42b61 winmm!InitDevices+0xc70012f9e4 76b42b94 76b40000 0012fa10 7c90118a winmm!DllProcessAttach+0xe40012f9f0 7c90118a 76b40000 00000001 0012fd30 winmm!_DllInstanceInit+0xb30012fa10 7c91c4fa 76b42b61 76b40000 00000001 ntdll!LdrpCallInitRoutine+0x140012fb18 7c9211b4 0012fd30 7ffdf000 7ffda000 ntdll!LdrpRunInitializeRoutines+0x3440012fc94 7c9210af 0012fd30 7c900000 0012fce0 ntdll!LdrpInitializeProcess+0x11310012fd1c 7c90e457 0012fd30 7c900000 00000000 ntdll!_LdrpInitialize+0x18300000000 00000000 00000000 00000000 00000000 ntdll!KiUserApcDispatcher+0x70:000> du 0012f9900012f990 "aux"It looks like BTStackServer is attempting to send something to the audio driver (DrvSendMessage), the Device Info list is created for all "aux" audio drivers on the system, and then there's a call to allocate heap with a heap handle of d8 - that handle appears invalid, and since we're calling a heap alloc via a malloc call this is going to fail with heap corruption errors. This could be an audio driver issue still, but it's really hard to tell right now (the audio driver hasn't been called or mapped in yet), so I'm not feeling really good about that angle. It does appear specific to calling the "aux" input though, which is why I'm hesitant to rule it out. I'm wondering if there's something in the BTStackServer code that's causing a race condition with this driver, so I'll pose my next question - it's very possible that the application running here has called a free() on an allocation in memory that's been GlobalAlloc()'ed before the thread using the memory completed, so is it possible to force your XP machine to use the uniprocessor kernel and see if it reproduces with Windows only using one processor?
Sp0iLedBrAt Posted January 12, 2010 Author Posted January 12, 2010 Well, what the heck, I'll try anything at this moment, you just tell me how. And to calm Mr. Jinje's spirits: yes, a new install will solve things and is more efficient than the time spent for diagnostics, but isn't it more fun like this? Cheers
cluberti Posted January 12, 2010 Posted January 12, 2010 Go to device manager, and right-click on the item under Computer (usually ACPI multiprocessor PC) and select "Update" driver. Select "Install from a specific location", "Don't search...", and then select "Standard PC" from the list and click Next and finish. After a reboot, you will be down to one processor (you can use the same steps to go back to the multiprocessor kernel after testing is done).
Sp0iLedBrAt Posted January 12, 2010 Author Posted January 12, 2010 Well, I did it! and WOW, it restarted the whole PC; drivers were installing anew, screen resolution took time to be fixed, but the problem remained. I made a dump with debugging tools HERE and there is something different in Device Manager; it shows two different things under Computer (before it showed only ACPI Multiprocessor PC)
cluberti Posted January 12, 2010 Posted January 12, 2010 OK, your box is using a uniprocessor kernel and the issue is the same, meaning it's not a serialization/threadsafe issue. At this point, I'd be harassing HP or Broadcom to have them look into it, because whatever happened it was inside the BTStackServer.exe module. Again, it *could* be the audio driver or something about it on the system, but it doesn't seem likely.The only time I've *ever* seen pMalloc crashes in setupapi (and they looked JUST like this) were when I had called a free() on a block that I'd GlobalAlloc()'ed, which is a no-no. It's a programming error, plain and simple.
Sp0iLedBrAt Posted January 14, 2010 Author Posted January 14, 2010 cluberti, thank you very much; I don't believe anybody would have provided me with this level of inquiry and help.FYI, Broadcom refers me to the OEM manufacturer, and HP are "very sorry, but this model is not currently supported for on-line assistance".Back to Mr. Jinje's conclusion from post #11.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now