PC randomly stalling, dmp etc included.

[Hemanse]

On the 15th and now again today my pc just randomly freezes, seems to be a bsod, but without the actually bluescreen

 

.dmp: http://i.imgur.com/lZYGJwv.png

 

debug: http://i.imgur.com/avrrwPJ.png

 

Looks like a processor/cpu error of some sort, but im really not not 100% sure, would love some help figuring out whats actually wrong.

 

thanks in advance.

[Michael McAllister]

Have you tested your RAM?  Might be RAM or graphics card.

[Hemanse]

Have you tested your RAM?  Might be RAM or graphics card.

 

ran memtest after the one on the 15th and got 0 errors, my graphics card runs just fine, max out at around 75 degrees celcius running kombustor or aida, the included dmp file should be able to help locate the problem, but im not 100% sure how to decipher it.

[Michael McAllister]

ran memtest after the one on the 15th and got 0 errors, my graphics card runs just fine, max out at around 75 degrees celcius running kombustor or aida, the included dmp file should be able to help locate the problem, but im not 100% sure how to decipher it.

 

I had a blue screen that was memory-related.  The test came back fine, but after replacing my RAM, everything ran fine.  Do you have other RAM that you can test/use?  The issue, as you have stated, seems to be hardware related.  Is your S.M.A.R.T. data for your hard drive showing any errors?

[Hemanse]

Did you look at the dmp and debug screenshots i posted? Its nice enough that someone tries to help, but you do seem to throw out a lot of random things to check.

[Michael McAllister]

You can analyze the dump file further by using the Windows Debugger tool.  When you install the program, you should be greeted with a relatively blank screen with some options on top.

SRV*http://msdl.microsoft.com/download/symbols

Choose Symbol File Path from the File menu or press CTRL+S and type the above.

 

If you attempt to exit the program now after this step, it should ask you if you want to save the debug environment or something similar.  Go ahead and choose Yes or OK.

Your dump files should be located in your C://Windows/Minidump.  To be sure, I would open C://Windows and navigate to it with your mouse.  Make sure that your hidden files are shown in your folder options.

Once you locate these, make sure that your particular user account has file permissions.  In my experience, you have to manually add your user account to this file in order for it to be opened with the debugger tool.

To give file permissions, you'll have to right-click the file you wish to debug, and go into the Properties.  There should be a Security tab which will show you who has permissions for that file.  Even if your Administrator, your particular profile is associated with a name that you gave it when you set up your PC.  Type this information in and it should give you the option to verify the profile.  After you do that, you should have permissions.

The browsing section should be located in the debugger's file menu.  Locate that same folder you were just in and double-click the file.  If done successfully, you should see a partial report with a command link with the word Analyze.  Go ahead and click that to receive the full report. Copy and paste that into the thread.

[Hemanse]

You can analyze the dump file further by using the Windows Debugger tool.  When you install the program, you should be greeted with a relatively blank screen with some options on top.

SRV*http://msdl.microsoft.com/download/symbols

Choose Symbol File Path from the File menu or press CTRL+S and type the above.

 

If you attempt to exit the program now after this step, it should ask you if you want to save the debug environment or something similar.  Go ahead and choose Yes or OK.

Your dump files should be located in your C://Windows/Minidump.  To be sure, I would open C://Windows and navigate to it with your mouse.  Make sure that your hidden files are shown in your folder options.

Once you locate these, make sure that your particular user account has file permissions.  In my experience, you have to manually add your user account to this file in order for it to be opened with the debugger tool.

To give file permissions, you'll have to right-click the file you wish to debug, and go into the Properties.  There should be a Security tab which will show you who has permissions for that file.  Even if your Administrator, your particular profile is associated with a name that you gave it when you set up your PC.  Type this information in and it should give you the option to verify the profile.  After you do that, you should have permissions.

The browsing section should be located in the debugger's file menu.  Locate that same folder you were just in and double-click the file.  If done successfully, you should see a partial report with a command link with the word Analyze.  Go ahead and click that to receive the full report. Copy and paste that into the thread.

 

http://i.imgur.com/avrrwPJ.png, i already linked to that in the first post, i analyzed it with WinDbg  :huh:

[Michael McAllister]

I apologize for the delay.  Been out sick and just recently ran into a BSOD issue of my own.  It's tough to say.  By looking at the screenshot you provided, it almost looks like some sort of processor issue.  Are you running at stock speeds?

I have heard of very few problems being directly related to the CPU unless it has been overclocked.  How are your temperatures when using the system?