It has been a while since I posted. I received a BSOD yesterday. While running SF Diag. Tool I also received an error. I have attached a screenshot of it. It seemed like it still collected all the files even with the error showing up.
Any help would be appreciated.
It is almost 4 months passed
So it is something to do with the display. Apply the latest version of nVidia display driver.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff880053e047f, fffff88005be38b8, fffff88005be3110} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DEVICE::RemoveCommitment+8f ) Followup: MachineOwner ---------
You may download it directly, from our forum link Latest NVIDIA ForceWare Video Drivers Windows 7; or you may opt for the Option 2 of Drivers- Download NVIDIA Drivers for “Automatically find drivers for my NVIDIA products” (it requires java installed).
Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.
Clean up the dust accumulated inside the computer, specially around the air vents and fan grills.
Also, the BIOS may be a good reason of it .....
Plan to update it.Code:BiosVendor = American Megatrends Inc. BiosVersion = 0801 BiosReleaseDate = 08/20/2010
Thank you for the fast reply.
A few questions;
So I ran the Stress Test with Fumark and closed it (pressed Esc.) when the temperature hit around 90 celcius. That's what I was supposed to do correct?
Also, the BIOS version I have is the latest according to the manufacturer's website (ASUS - - ASUS M4A78L-M)
I have Speccy running at the moment and will take a screenshot in a few hours. As well, I will be running the memtest overnight tonight.
Edit: I already have the latest display driver; updated it a couple days ago.
As per the last dump, your display driver is not latest, that one is released on 18th of this month.
If furmark goes upto 90 degrees, there is overheating, and you must need additional cooling mechanism.
About the BIOS, I am not sure.
Received another one yesterday.
The screenshot of Speccy from the other day is attached as well. I haven't run memtest yet because I was busy with some things on the PC but plan to do it real soon.
We need the results of the memtest. Also, your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
InformationWhy Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.
How Can we know that DV is enabled:
It will make the system bit of slow, laggy.
WarningBefore enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.
If there is no points, make a System Restore Point manually before enabling DV.
Let us know the results, with the subsequent crash dumps, if any.Tip
- If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
- If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.
Received a BSOD with DV enabled. I have attached the .rar file. The memtest results will be posted soon. Apologies for not getting them in quicker. Thank you.
No apologies are needed ... you will do it only when you have time to do it.
Anyway, your latest (verifier enabled) crash dump is also kinda weird ...
It comes with a bugcheck code 19, that means it is a bad pool header, should be caused by a device driver; but it says tht it is caused by memory corruption.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 19, {20, fffffa80071f4760, fffffa80071f4760, 4000016} GetPointerFromAddress: unable to read from fffff800030b9100 GetUlongFromAddress: unable to read from fffff800030b91c0 fffffa80071f4760 doesn't look like a valid small pool allocation, checking to see if the entire page is actually part of a large page allocation... GetUlongFromAddress: unable to read from fffff80003027a38 Probably caused by : memory_corruption ( nt!MiDeleteControlArea+44 ) Followup: MachineOwner ---------
I guess in this point that yours in a hardware issue, and the memtest will help us to decide the further steps.
Ran memtest overnight. Went for at least a dozen passes, can't remember exactly. At the bottom it stated 'No Errors'.
What should I try next?
Thank you.
Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Stress test the CPU.
Hardware - Stress Test With Prime95
Disc Check:
- Update your SSD's Firmware (skip it, if you are not using a SSD)
- Reseat the sata and power.
- Run chkdsk /f/r, following the option two of the tutorial Disk Check
- Seatool for dos: SeaTools | Seagate download
Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
Also, you may need to try with another PSU .... as a test.
Quote
