• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

BSOD- bad_pool_caller then memory dump Win XP Pro

L

LeRNeR

Junior Member
Current setup:
Motherboard: Asus A7M266-D rev103 bios 1004
Processors: 2x - AMD MP1600's
HeatsinkFan: 2x - Thermaltake volcano 7's HSF .40-42 idle and 43-46full load. (Arctic Silver II _w/Cool Shims)
Memory: 2x- 512MB Mushkin High Perf Non-ECC Unbuffered
Case: Lian-Li PC-65 (w/ see-through side and blue cathode lights)
Power: Enermax 550w (650w peak model# EG651P-VE works great, quiet too.)
Hard drives: 1x - Atlas 10K II 36Gig 10,000RPM Ultra160 SCSI, 2x - IBM-DTLA-307075 ATA100 UltraDMA5 - RAIDO @ 143Gig Z: Drive.
CD-Roms: IDE Pioneer Slot load DVD 16/40, IDE Plextor 24/10/40 burner.
Monitor: Nokia 21"
Display adapter: Leadtek Winfast Geforce 3 TI500
Audio: Creative Audigy w/ firewire
SCSI: Adaptec 39160 Ultra160 64-bit dual channel
USB: NEC PCI USB 2.0 4-port. Woohoo thanks Asus. Hey it's better than 1.0 & firewire!!!
Windows XP Pro

This blue screen primarily occurs during Winamp, changing songs, and occasionally happens when I overclock the TI500, during the "test settings" where your screen is adjusted/tested 3 times before finally closing out of "Display Properties".

I was told in a few forums that due to my CL Audigy, adjust my Motheboard bios settings "PCI Latency" from default "32" to "0". Or at least these guys have done it and it seemed to make that specific blue screen with their CL Audigy go away.

But I'm not fully conivced yet this is totally the fault of the CL Audigy.

Anyone else get this BSOD with similar hardware? Or is this maybe a software/driver problem?

 
Could you give more info on the STOP error? There are some articles out at Microsoft that feature the bad_pool_caller. You might want to check those out, but you will need to write down some of the numbers from the memory dump.

Ryan
 
In the case of a BAD_POOL_CALLER bugcheck, only the first number inside parentheses is likely to be of much help.

Given the symptoms, it sounds like either the sound card or the video card drivers are the likely culprit.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top