need help in finding out the problem

Status
Not open for further replies.

ubergeek

Forerunner
hey guys recently when i was working with ms word suddenly i got a bsod the comp restarted and when i examined the dump file the error was with the process csrss.exe so after that i did a chkdsk on my windows partition errors were found after that i ran the recovery console from xp cd and repaired it using the comand chkdsk /p the computer has been running for an hour now with no bsods please help me and tell what might be the problem

here is he analyzed dump file

Code:
PROCESS_OBJECT: 8a558530

IMAGE_NAME:  csrss.exe

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

BUGCHECK_STR:  0xF4

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
b908a520 805d02e9 000000f4 00000003 8a558530 nt+0x22c37
b908a544 805d11ed 805d1142 8a558530 8a5586a4 nt+0xf92e9
b908a574 8054060c 8a558778 c0000006 b908a9b0 nt+0xfa1ed
b908a584 805004c5 badb0d00 b908a5fc a5a3f2f6 nt+0x6960c
b908a9b0 80501c03 b908a9d8 00000000 b908ad64 nt+0x294c5
b908ad34 80543ed7 0069fbe8 0069fc08 00000000 nt+0x2ac03
b908ad50 8054060c 0069fbe8 0069fc08 00000000 nt+0x6ced7
b908ad64 7c90eb94 badb0d00 0069fbdc ffffffff nt+0x6960c
b908ad68 badb0d00 0069fbdc ffffffff 00000000 0x7c90eb94
b908ad6c 0069fbdc ffffffff 00000000 00000000 0xbadb0d00
b908ad70 ffffffff 00000000 00000000 00000000 0x69fbdc
b908ad74 00000000 00000000 00000000 00000000 0xffffffff
STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

BUCKET_ID:  WRONG_SYMBOLS

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

and

Code:
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                   *
* The Symbol Path can be set by:                                    *
*   using the _NT_SYMBOL_PATH environment variable.                 *
*   using the -y <symbol_path> argument when starting the debugger. *
*   using .sympath and .sympath+                                    *
*********************************************************************
Probably caused by : csrss.exe

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

please help :(
 
1. I wud suggest a Clean Install after formatting ur OS partition.

2. Do a RAM Test

3. Check airflow in cabinet (SPecially over the RAM)
 
hmmmmm so a ram test is neede huh ?

rite now the comp has been going fore more that 2 hours rock solid but still that sudden bsod is very discerning will do a ram test ann will keep you guys posted :D
 
Status
Not open for further replies.