Hey all,

There i was, sat watching the telly, my laptop sat there, lid open, looking inconspicuious, at the windows xp home login screen. when my little brother ran in, pressed loads of the keys at the top of the keyboard and turned it off with the power button. he pressed the power button so it started to shutdown, and then held it, so it forced shutdown. and now whenever i turn it on, it says windows xp loading thingy with the load bar, and then goes to a blue screen with white writing that says

'A porblem has been detected and windows has been shut down to prevent damage to your computer.

BAD_POOL_CALLER'

followed by 'if this is the first time you have seen this stop error screen, restart your computer' and all that stuff.

need urgent help!!

Much apreciated

Tom

Dani AI

Generated

Quick, practical plan that builds on what has already tried and on ’s recovery-console suggestion — focused on ruling out hardware first, because the crash happens even from external boot media when a tool touches the disk.

Start by testing RAM and seating. Faulty or marginal memory commonly causes pool corruption at kernel level; a dedicated bootable memory tester (not a WinPE/UBCD image) will prove or rule that out. Reseat modules and test each stick in isolation; if the tester reports errors, replace the bad stick. Bug Check 0xC2: BAD_POOL_CALLER. (learn.microsoft.com) . ()

If RAM looks clean, collect crash dumps and inspect the offending module. From your working Linux/live environment copy any minidump files (usually under C:\Windows\Minidump) to a healthy PC, then open them with a dump viewer. That will point to a driver or system file to target (replace, roll back, or remove offline). Tools: BlueScreenView for quick reads or WinDbg for deeper analysis. BlueScreenView (NirSoft). (nirsoft.net) Crash-dump analysis basics (WinDbg/MS docs). (learn.microsoft.com)

Because your boot CDs can browse the disk but crash when running disk/backup utilities, test the drive/controller from outside the laptop. Run SMART/self-tests from a Linux live session (smartctl) or remove the drive and attach it to another PC/USB adapter to run checks and to back up important data before any risky repairs. Also note: Driver Verifier can help locate a bad driver but it deliberately stresses drivers and will cause crashes — only use it if you can analyze dumps or on a test machine. smartctl / smartmontools guidance. (thomas-krenn.com) Driver Verifier notes. (learn.microsoft.com)

Priority order: back up now while Linux can read the disk; run an extended memory test; run SMART/self-tests or move the drive to another machine; collect and analyze minidumps to identify a driver. These steps will separate failing hardware from a bad driver so the next repair (replace memory, replace drive, or remove a problematic driver) is the right one.

Recommended Answers

All 4 Replies

have a look here ,the most important part of the error message is the long number ,0x00000000b2 or what ever yours is.
check out this link= http://aumha.org/a/stop.htm

Thanks, i'll check it out and let you know what happens

have a look here ,the most important part of the error message is the long number ,0x00000000b2 or what ever yours is.
check out this link= http://aumha.org/a/stop.htm

I had tried safe mode, which didnt help, i have even tried WinPE and UBCD4WIN (basically windows live cds) . They boot, but if i try to run a virus scanner from the boot cd or use a hard disk cheking program or even back up the hard disk, i get the BAD_POOL_CALLER screen. The 'technical information is: *** STOP: 0x000000C2 (0x00000043, 0xD3600000, 0x00000000, 0x00000000)

If it were a hard drive problem, would i still have full access to the hard drive on UBCD4WIN through my computer? But it cant be a software problem because i can access the computer ish through live linux cds and DSL on my pen drive. i havnt a clue what the problem is. please help.

boot to the windows cd and go to R for repair and run a chkdsk /r , to check the hdd ,be careful wit UBCD4WIN ,there are programs on it that could wipe the hdd.
search google for how to use the windows recovery console if you don't know how to use it

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.