Hi there

I just formatted my pc and added some new parts. I was playing oblivion and went in the menu to exit the game. It like jammed and few sec after a bsod popped up. Bad Pool Header with 0x00000019. Attached is the dump file with your steps. jope you can help me cpc or someone else :'(

Cheers

Attached Files

BSOD.txt (4.9 KB, 11 views)

Thanks. Willstart learning to read minidumps....

Thanks. Am going to try it!

I have been having the same issue too. I will go ahead and try using the debugging tools again. I basically changed HD, PSU, RAM, FAN and Video Card, still I'm getting a lot of BSODs.

This thread needs to be a sticky!

I have at least 2 BSOD's in a week. Attached is my windbg log, can somebody help me here please ?

Thanks

Attached Files

	DEBUGLOG.TXT (16.0 KB, 6 views)
	Bugcheck.txt (200 Bytes, 2 views)

I bought this new asus motherboard and a new dual core cpu... since i started using it, it keeps rebooting... thought it was the RAM but i checked by replacing the sticks with new ones but its the same...

got this on the event viewer:
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 17/10/2007
Time: 12:22:10 PM
User: N/A
Computer: THE-MATRIX
Description:
Error code 0000009c, parameter1 00000000, parameter2 f7795050, parameter3 b2000000, parameter4 1040080f.


Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 39 0000009
0020: 63 20 20 50 61 72 61 6d c Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 30 2c 20 000000,
0038: 66 37 37 39 35 30 35 30 f7795050
0040: 2c 20 62 32 30 30 30 30 , b20000
0048: 30 30 2c 20 31 30 34 30 00, 1040
0050: 30 38 30 66 080f



can someone plis help me... got the minidump but how do i attach it in here...

cheers
Nicky

Howard pointed out some were having difficulty with the previous link on minidumps and has suggested this one as a tutorial. http://forums.majorgeeks.com/showthread.php?t=35246

enjoy!

Hello,

As i saw you read dump as a guru I have mine in a thread under Windows OS:

What is issue? It is happening on all Windows 2000 workstations when I try to connect remotely and if the user trying to login does not have already a profile created locally....

Thank you,
Dominique

pls can any1 help with read my minidump n tell me y my computer keeps showing dat blue screen

Attached Files

Mini060808-03.dmp (88.0 KB, 4 views)

Inside the 1 MiniDump:
Probably caused by "Daemon Tools"
Try uninstalling it in Add/Remove programs

Also in future you should create your own thread

And what do I need to do? PLEASE HELP!

It's too long to post here. Can someone provide me with an email so I can send it so that you may look it over and help?

Sincerely,

Steven
stevengfowler (at) yahoo.com

1. First, start your own post. You will find that you will get quicker responses than attaching to an old thread.

2. Put your system specs in your profile including power supply and operating system.

3. Read the sticky in this forum ebtitled "Before posting your minidumps..." by Julio. Do the advice given there and see if those steps help you rectify your issues. And let us know.

4. Do make a public post. Just give the highlights. We don't need all the details. Someone will definitely come along and help.

Lastly, welcome to the forums.

I've gone through the steps as listed, but I'm getting the following:
Anyone knows how to rectify this?

Perhaps another link

Here you can learn how to read your own Minidump
http://forums.majorgeeks.com/showthread.php?t=35246

Here's some info, before attaching MiniDumps (for new members)
http://www.techspot.com/vb/topic51365.html

ok try this go to windbg(within debugging tools for windows) then go file>symbol fiel path and then input the location of the symbols folder you created (if you havent done this, just go to c: and create a folder with the name 'symbols', then input it in windbg)

Hope this helps

Can anyone tell what could be provoking this?

*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000002c, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 805418fb, address which referenced memory

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


WRITE_ADDRESS: 0000002c

CURRENT_IRQL: ff

FAULTING_IP:
nt!KiServiceExit2+117
805418fb 897308 mov dword ptr [ebx+8],esi

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0xA

PROCESS_NAME: OUTLOOK.EXE

LAST_CONTROL_TRANSFER: from 988dbde0 to 805418fb

STACK_TEXT:
988dbd64 988dbde0 badb0d00 7c8024b7 033c2310 nt!KiServiceExit2+0x117
WARNING: Frame IP not in any known module. Following frames may be wrong.
988dbddc 805460ee b9ca8b85 87520700 00000000 0x988dbde0
988dbde0 b9ca8b84 87520700 00000000 4020027f nt!KiThreadStartup+0x16
988dbde4 87520700 00000000 4020027f 015f0000 NDIS!___PchSym_+0xc
988dbde8 00000000 4020027f 015f0000 02436b42 0x87520700


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
!chkimg -lo 50 -d !nt
80541461-80541465 5 bytes - nt!KiSystemService

[ 6a 00 55 53 56:e9 aa 6c 73 39 ]
80541547-8054154b 5 bytes - nt!KiFastCallEntry+17 (+0xe6)

[ 6a 23 52 9c 6a:e9 84 6c 73 39 ]
10 errors : !nt (80541461-8054154b)

MODULE_NAME: SysPlant

IMAGE_NAME: SysPlant.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45a4b4e9

FOLLOWUP_NAME: MachineOwner

MEMORY_CORRUPTOR: PATCH_SysPlant

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_PATCH_SysPlant

BUCKET_ID: MEMORY_CORRUPTION_PATCH_SysPlant

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

This is an old thread. In the future you really need to start your own posting so that you can receive help all the quicker.

0xA errors are due to hardware or faulty drivers. In your case it is the Symantec CMC Firewall driver SysPlant.sys. You could update the software but we are recommending people to uninstall Symantec/Norton and go with better offerings. If you do decide to uninstall then make sure you go to their website, find the removal tool for your particular version and use it. This software is notorious for leaving remanants of itself behind.