need help with bsod error

while i playing games my com suddenly pop up bsod dump file uploaded

If you follow the instructions given here, one of our members will be glad to help solve your BSOD problem

richc46 said:

If you follow the instructions given here, one of our members will be glad to help solve your BSOD problem

Click to expand...

thanks for reminding=)

attachments updated

Your reports are all corrupt. Try again. Have you validiated your copy of Windows?

richc46 said:

Your reports are all corrupt. Try again. Have you validiated your copy of Windows?

Click to expand...

yes i have, i have been using for 4mths since last formated and files reuploaded

OK sorry to put you through all this trouble, but can you send the dump reports again?

richc46 said:

OK sorry to put you through all this trouble, but can you send the dump reports again?

Click to expand...

its ok=) how do i send to u and i have reuploaded the files

richc46 said:

http://www.vistax64.com/crashes-debugging/282419-blue-screen-death-bsod-posting-instructions.html

Click to expand...

i have done all the steps from your link u gave and attached the files on my post

This is all I can see in your reprot. I can give you this. With BC 124 this is our normal starting point; but in your case I can not give any specific information about the cause
Stop 0x124 - what it means and what to try - Windows 7 Forums

richc46 said:

http://www.vistax64.com/crashes-debugging/282419-blue-screen-death-bsod-posting-instructions.html

Click to expand...

richc46 said:

This is all I can see in your reprot. I can give you this. With BC 124 this is our normal starting point; but in your case I can not give any specific information about the cause
Stop 0x124 - what it means and what to try - Windows 7 Forums

Code:

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

Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp4_Windows_NT6_BSOD_jcgriff2[1].zip\Windows_NT6_BSOD_jcgriff2\Mini090410-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: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Machine Name:
Kernel base = 0x8180a000 PsLoadedModuleList = 0x81917930
Debug session time: Sat Sep  4 01:32:33.441 2010 (GMT-4)
System Uptime: 0 days 4:15:55.991
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
...........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, 845a43f0, f2000018, 6000e0f}
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
Probably caused by : hardware
Followup: MachineOwner
---------

Click to expand...

oh ok thanks for helping=)

If you have problems understaning something in that BC124 article or how to do it, just post.

richc46 said:

If you have problems understaning something in that BC124 article or how to do it, just post.

Click to expand...

from the i article i see, it most likely should be related to my overclocked cpu i change the speed to stock temporary hope it stays fine without bsod. my processor temperature is always 70 degree above while gaming is it normal?

60 should be about the highest.
How to Prevent Your Computer from Overheating (and Why It's Important)

Overclocking=Bad