I have just spent the worse 3 hours of my life. Well it was probably half an hour but felt like 3. The day before yesterday I got the blue screen of death with the error message....

stop: 0x000000C2 (0x00000007, 0x00000CD4,0x81F92670, 0x81F09B98) beginning dump of physical memory.

I put it down to the scanner and tried to update the drivers but couldn't find them when they installed on the pc. I kept rebooting and in the end it got there.

Tonight however I tried to reinstall the scanner with the disc that came with it. I had to reboot and got the blue screen constantly with the message
"multiple_IRP_ complete_requests"

I couldn't get into safe mode as for some reason no keyboards that we have seem to recognise F8. Luckily I found an xp boot floppy disk, the only reason I am here now. I did a system restore to yesterday when things were running ok then took the floppy out but got the same error message.

BTW I installed netscape 8 today. I don't know if that has any bearing on the last error message.
I am never rebooting ever again.

I think it must be a software issue as windows starts to load, then just as it's supposed to reach the log in screen it throws up the blue screen of suicide.

Seeing the dump logs might help:

Go to start | search (type in) .dmp
Note the location of your latest .dmp file.

Then:

1) Download and install the
Debugging Tools from Microsoft
2) Download and install this
debugwiz
3) Open the Wiz & Browse to, or paste in the path to, your latest .dmp file.
4) After the Wiz creates a Text document attach it back to this thread.

Also: Did chkdsk run after the dump?
If not you might want to run it. Although you need to reboot to do so.
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.

Just some further research while we await .dmp logs.

stop: 0x000000C2 (0x00000007, 0x00000CD4

http://www.google.co.uk/search?q=sto...-8&hl=en&meta=

multiple_IRP_ complete_requests

http://www.google.co.uk/search?hl=en...quests&spell=1

Perhaps also the effect of a multiple installation.

Also you can set the computer to boot into Safe Mode via
start/run/ msconfig
BOOT.INI
/SAFEBOOT


_________________________

Thanks jephree I hope I have done this right.
I have just done a chkdsk.

Code:

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger  Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini051705-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Tue May 17 22:25:26.326 2005 (GMT+1)
System Uptime: 7 days 1:11:50.415
Loading Kernel Symbols
................................................................................................................................
Loading unloaded module list
........................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, cd4, 81f92670, 81f09b98}

*** ERROR: Module load completed but symbols could not be loaded for cmaudio.sys
Probably caused by : cmaudio.sys ( cmaudio+1f67b )

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

kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 81f92670, Memory contents of the pool block
Arg4: 81f09b98, Address of the block of pool being deallocated

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


POOL_ADDRESS:  81f09b98 

FREED_POOL_TAG:  Thre

BUGCHECK_STR:  0xc2_7_Thre

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

LAST_CONTROL_TRANSFER:  from 8054b741 to 8053331e

STACK_TEXT:  
f5577d20 8054b741 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b
f5577d70 8054b0b9 81f09b98 00000000 f5577ddc nt!ExFreePoolWithTag+0x2be
f5577d80 f928167b 81f09b98 f927e9bd 81f09b98 nt!ExFreePool+0xf
WARNING: Stack unwind information not available. Following frames may be wrong.
f5577ddc 804fa4da f92bab40 82059850 00000000 cmaudio+0x1f67b
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP: 
cmaudio+1f67b
f928167b c20400           ret     0x4

SYMBOL_STACK_INDEX:  3

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  cmaudio+1f67b

MODULE_NAME:  cmaudio

IMAGE_NAME:  cmaudio.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  3dd89c0b

STACK_COMMAND:  kb

FAILURE_BUCKET_ID:  0xc2_7_Thre_cmaudio+1f67b

BUCKET_ID:  0xc2_7_Thre_cmaudio+1f67b

Followup: MachineOwner

That particular crash was triggered by your sound card/device driver:
IMAGE_NAME: cmaudio.sys

Check for a new driver at the manufacturer's web site.
http://www.cmedia.com.tw/e_download_01.htm

There are two modes to install. Either onboard or a PCI card.
Also check BIOS for Audio. If you use a PCI card the onboard should be disabled.

Also for the future please change your dump log setting via:
Right click My Computer then click Properties then Advanced then Startup and Recovery/ Settings
Write debugging information: change to Complete memory dump

Also I am wondering if your keyboard as well as scanner were/ are USB devices?
Also the scanner: did you uninstall old drivers before attempting to reinstall?
I am wondering if these various drivers were creating the IRQ conflict.

Have there been any changes in your problem? Are things running ok now? Any more blue screens? Have you rebooted?

Thanks Jephree,
I have checked for drivers and it looks like they are up to date.
I have changed the dump log settings to complete memory dump.
I did uninstall the scanner drivers before reinstalling it. At the time of the problem the keyboard I was using stopped working so I had to change to a USB one, the scanner is USB as well.
I have just taken the floppy boot disc out and rebooted and it actually got to the welcome screen.

*ignore, clicked wrong button*

Let us know if we can help further in the future!

This thread has been Resolved and Locked to prevent other users hijacking the thread and to help others know which threads have been Resolved and which are still being worked on.

If you started this thread and the problem returns or the case has not been properly Resolved, please send a Private Message to a Moderator of this forum to have the thread opened again. If you have a different problem, please start a new thread.