Any ideas ...ASrock P4vm8 motherboard ,Intell3.2 gig processor, 512 ddr 400
XP with service pack 2....all current updates...
Getting constant blue screen errors and shutdowns
latest was bad_pool_caller.....
I removed my pci video card and reloaded the drivers for the onboard vid....
No errors yet..10 minutes but I also haven't put any styress on the monster yet... going to run a few music loop programs and copy some files from another computer on my network to see if it will hang up and crash again!
Any Ideas....

Please post the full blue screen errors.

Also: look in your event viewer:
rt. click My Computer then click Manage then Event Viewer.
Open the system as well as the application tabs & look for X errors. Click error line for details.
Post back the source & event id especially of errors that seem to coincide with a crash.

If your comp is rebooting automatically change this setting:

rt. click My Computer then click Properties then Advanced then Startup and Recovery Settings then unclick Automatically restart

Also run check disk:

start > run > cmd
in the new window type chkdsk/f
when prompted to run on boot choose Y & reboot
this will check for & fix any disk errors

will do thanks!

Hey these codes are from today....Lots of problems here thank you for all your knowledge and help



C:\DOCUME~1\PRICET~1\LOCALS~1\Temp\WERb0c1.dir00\M ini031205-07.dmp
C:\DOCUME~1\PRICET~1\LOCALS~1\Temp\WERb0c1.dir00\s ysdata.xml
Faulting application svchost.exe, version 0.0.0.0, faulting module unknown, version 0.0.0.0, fault address 0x00000000.
Windows saved user OPTIMUSPRIME\pricetron registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.

This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

Error code 100000d1, parameter1 00000018, parameter2 00000002, parameter3 00000000, parameter4 f65af550.

The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x00000018, 0x00000002, 0x00000000, 0xf65af550). A dump was saved in: C:\WINDOWS\Minidump\Mini031205-07.dmp.

Error code 000000c2, parameter1 00000007, parameter2 00000cd4, parameter3 01300025, parameter4 8345d688.


Error code 000000c2, parameter1 00000007, parameter2 00000cd4, parameter3 01300025, parameter4 8345d688.

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2 (0x00000007, 0x00000cd4, 0x01300025, 0x8345d688). A dump was saved in: C:\WINDOWS\Minidump\Mini031205-06.dmp.

Error code 000000c2, parameter1 00000007, parameter2 00000cd4, parameter3 024c0003, parameter4 8354b558.

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2 (0x00000007, 0x00000cd4, 0x024c0003, 0x8354b558). A dump was saved in: C:\WINDOWS\Minidump\Mini031205-05.dmp.

Error code 000000c2, parameter1 00000007, parameter2 00000cd4, parameter3 004c004c, parameter4 84e63da8.

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2 (0x00000007, 0x00000cd4, 0x004c004c, 0x84e63da8). A dump was saved in: C:\WINDOWS\Minidump\Mini031205-04.dmp.

Questions:

Do you see any corresponding errors in the Event Viewer?

Any new hardware or software?

What is the make & model of the PCI Video Card?

_________________________________________

General Data:

0x000000C2: BAD_POOL_CALLER
(Click to consult the online Win XP Resource Kit article.)
A kernel-mode process or driver incorrectly attempted to perform memory operations. Typically, a faulty driver or buggy software causes this.

* 0x000000C2 {KB 265879} Win 2000, Win XP
* 0x000000C2: BAD_POOL_CALLER {KB 310527} Win XP (upgrading Compaq Professional Workstation AP550 from Win 2000 to XP)
* Computer with ATI RAGE FURY MAXX Video Adapter Stops Responding After Upgrade to Win XP {KB 307151} Win XP


# A Stop 0xC2 message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
# A Stop 0xC2 message might also be due to failing or defective hardware. If a Stop message points to a category of devices (such as disk controllers, for example), try removing or replacing the hardware to determine if it is causing the problem.

The error code 100000d1 from event viewer is a bit confusing, at least
to me. I suspect that it refers to a STOP 0x000000D1:
DRIVER_IRQL_NOT_LESS_OR_EQUAL

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online Win XP Resource Kit article.)
The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.

* Error Message with RAM Problems or Damaged Virtual Memory Manager {KB 810093} Win XP Home (during restart)
* “STOP:0xD1” Error Message When You Start Your Win XP-Based Computer {KB 316208} Win XP
* Stop 0x000000D1 Error Message When You Turn Your Computer Off {KB 317326} Win XP (with USB device(s) connected)
* “STOP 0x000000D1 IRQL_NOT_LESS_OR_EQUAL Kbdclass.sys” Error Message When You Try to Shut Down the Computer {KB 810980} Win 2000, Win XP (Logitech mouse with outdated MouseWare software)
* STOP 0xD1 error message when you start your Win XP-based computer {KB 839876} Win XP (ACPI issue, a Hotfix is available)
* WRQ AtGuard Program Causes Error Message in Win XP {KB 319870} Win XP (AtGuard version 3.22)

http://aumha.org/win5/kbestop.htm

__________________________________________

If you so desire:

1) Download and install the
Debugging Tools from Microsoft
2) Locate your latest memory.dmp file- C:\WINDOWS\ Minidump\Mini011005-01.dmp or whatever
3) open a CMD prompt and type: cd\program files\debugging tools for windows\
4) then type the following stuff:

c:\program files\debugging tools>kd -z C:\WINDOWS\ Minidump\Mini011005-01.dmp
(it will spew a bunch)
kd> .logopen c:\debuglog.txt
kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
(it will spew)

5) You now have a debuglog.txt in c:\, open it in notepad and post to this thread.

Or to Automate the above cmd's you can also use this little tool:
http://www.d-a-l.com/help/attachment...tachmentid=127

STOP C2 (07,)'s are sometimes hard to troubleshoot. Its a double free, which means that usually, one driver allocated some memory, was done using it, and freed it, then someone else (or the same driver) tried to free it again. Its worthwhile to look at the dump spew, but often these arent that easy to resolve, requiring some voodoo combinations of special pool, pool tracking and debugging creativity. Lets see what you got, and make sure you have updated all the drivers you can.

Welcome to D-A-L Forums joehobart Master Debugger

It is from reading your posts at http://www.windowsbbs.com/
that I first heard of the Microsoft Tool as well as your command app.

Hope it was ok to "borrow" it.

Also via reading your posts that I've learned the little I know of debugging.

Thanks for your knowledge & your visit here

I hope you return when you have time!

hey, i recognize that little debugwiz

Pricetron - post a debug log up and lets see what we got.

Originally Posted by joehobart

STOP C2 (07,)'s are sometimes hard to troubleshoot. Its a double free, which means that usually, one driver allocated some memory, was done using it, and freed it, then someone else (or the same driver) tried to free it again. Its worthwhile to look at the dump spew, but often these arent that easy to resolve, requiring some voodoo combinations of special pool, pool tracking and debugging creativity. Lets see what you got, and make sure you have updated all the drivers you can.

Welcome to D_A_L You seem very knowledgable...........