Continuous, daily crashing -- ‘ntoskrnl+80640’

[computerhelp]

Continuous, daily crashing -- ‘ntoskrnl+80640’

I’m running an AMD Phenom II X6 1035T on a Crosshair V motherboard with 2 SSDs, 1 HDD and a few external drives.

Ever since getting the new system together (before I used a different motherboard, PSU and only HDDs) I get daily crashes.

I’ve attached a dump report, a whole bunch of pictures of system specs, and virtually everything I know. There’s also a document that looks at SSD and HDD status – I’m suspecting it’s my OCZ SSDs that may be acting up…

The crash address is ‘ntoskrnl+80640’.

I also get this curious warning from my Crosshair V motherboard software (even though I did not edit the default settings of the motherboard). Please see attached.

Any help would be appreciated.

 

[zigzag3143]

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP


We could also use some system information, which you can get easily by running msinfo32.
To do that go to start>run>type msinfo32>enter

When it is finished running go to file>save>name it and upload to us here.


You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[computerhelp]

crash files

Here are the dmp files.

thanks.

 

[zigzag3143]

Here are the dmp files.

thanks.

Every single one of these are related to a "critical process termination". That just means a process (scrss.sys) has been terminated unexpectedly.

One thing of note., the average uptime (time the computer has been continuously on for) is around 4 days. That in itself can trigger these crashes. It seems since Feb 2012 yu have been getting them about 6-8 times a month and that would help support that idea.

In addition I would run a system file check to verify the OS files

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

 

[computerhelp]

i would tend to disagree that constant uptime is the culprit. unless of course SSDs cant handle the uptime which is a different discussion.

someone had suggested increasing the dram voltage to 1.69 from 1.5v. good idea?

 

[zigzag3143]

i would tend to disagree that constant uptime is the culprit. unless of course SSDs cant handle the uptime which is a different discussion.

someone had suggested increasing the dram voltage to 1.69 from 1.5v. good idea?

I would say it couldn't hurt, but actually it can. There are times when voltage needs to be adjusted but I only recommend them as a last resort.

In the same vein I also don't recommend overclocking.


As I said, your crashes happen about every 4 days and if it were ram voltage it would happen at odd intervals.

 

[zippydooda]

80640 error

Hi
I'd like to continue this thread as I'm getting the 80640 error as well and it is hard to tell if this issue was resolved so far in this thread.

Basically win7 was running flawlessly for me for three years until about April 2014 or so... the bsd's started. Sometimes several times in one day other times once a day. First tried uninstalling firefox perhaps it was a hardware accelaration issue, began using chrome and ie still problems.

I began hardware swaps. Changed the display card still crashed. Changed the powersupply and again. Today I changed the mb to the new one on file and still feezing and crashing.

sfc /scannow would never complete for some reason. I was successful today to finish it through to the end and it repaired the problem. Ran it again and no errors found by sfc yet still crashes.

Still puzzled.

*****

I'll start a new thread with this one ... I guess this thread is too old?