HELPP ME? i'm not sure my problem same as yours , my pc suddenly automatic reset when i'm using about 2-3 hours, Damnn I hate it,

I had try playing games nfs carbonm it's run okay,
I have check my pc with norton anti-virus 2006, no virus detected
but sometimes i let pc just let in on, after 1-2 hours i came back using it , playing mp3, downloading from bittorent, using msn, internet everything suddenly pc my reset.. No blue sreen came out, no warning.
I change my sata cable , still the problem came again, Everyting i have tried including upgrade the new bios & change my ram and put another slot
the problem still same
My friend said my pc got that problem because of heat problem, but my pc run usually 39-46 degrees.

I'm looking for your advise

E6300 Core2
Gigabyte GA-965P-DS3 <--- still new , why my pc is going weird
Cooler Master Xtreme psU 430Watt
Ram 675ddr2 hyperx
Wester Digital Sata 160GB

This post has been edited by wo0p: Dec 10 2006, 02:36 PM

This is my latest about my pc in debug file

Loading User Symbols
Loading unloaded module list
.......................
Unable to load image gdrv.sys, Win32 error 2
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, f7af76cb, b9ed5b98, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Probably caused by : gdrv.sys ( gdrv+6cb )

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

0: kd> .reload
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe -
Loading Kernel Symbols
....................................................................................................................
Loading User Symbols
Loading unloaded module list
.......................
0: kd> "!analyze -v
^ Syntax error in '"!analyze -v'
0: kd> "!analyze -v
^ Syntax error in '"!analyze -v'
Unable to load image gdrv.sys, Win32 error 2
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys