Hi M1kep.
Every single crash dump is of different nature, and there is one driver verifier enabled crash dump too, which did not catch anything. So apparently we can place the falling device drivers and driver verifier at a lower order of priority. But we may need to do a lot of jobs to identify the issue.
Have you recently installed any fonts or any programs containing fonts? Can you access to the fonts folder in C:\Windows\Fonts without any hassles?
Upload the list of all the third party drivers Using
NirSoft DriverView : I want to see if any font driver is present there.
- Download and execute Driverview
- View > Hide Microsoft Drivers
- Edit > Select all
- File > Save Selected Items
- In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
- Zip the .txt file and upload it.
You said you ran Memtest86+. For how many passes?
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.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Uninstall Virtual Clone Drive.
Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
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. Alternatively, you can publish a Speccy snapshot too:
http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .
It seems to be an old branded computer. Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
http://www.extreme.outervision.com/psucalculatorlite.jsp
Also let us know the wattage of the PSU.
Scan the system for possible virus infection with the following programs.
Also, if possible, search for any possible BIOS update in HP.
Code:
BiosMajorRelease = 5
BiosMinorRelease = 7
BiosVendor = Phoenix Technologies, LTD
[COLOR=Red]BiosVersion = 5.07
BiosReleaseDate = 11/27/2008[/COLOR]
SystemManufacturer = HP-Pavilion
SystemProductName = FQ562AA-ABA m9500f
SystemFamily = 103C_53316J
SystemVersion =
SystemSKU = FQ562AA#ABA
BaseBoardManufacturer = MSI
BaseBoardProduct = Aspen
BaseBoardVersion = 1.0
Let us know the results. If all fails, we have to look at the storage controllers.
_________________________________________________________________________________________
Code:
BugCheck 3B, {c0000005, fffff800024e1cc4, fffff88009bb3350, 0}
Probably caused by : win32k.sys ( win32k!GreAcquireSemaphore+1c )
Followup: MachineOwner
-----------------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff800030e3601, fffff88003eb1930, 0}
Probably caused by : ntkrnlmp.exe ( nt!SeAccessCheckWithHint+2c1 )
Followup: MachineOwner
-----------------------------------------------------------------------------------
BugCheck A, {fffffffffff8aa0d, 2, 0, fffff80003083f04}
Probably caused by : ntkrnlmp.exe ( nt!KeAcquireInStackQueuedSpinLock+44 )
Followup: MachineOwner
------------------------------------------------------------------------------------
BugCheck 1A, {41287, 0, 0, 0}
Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+454f5 )
Followup: MachineOwner
-------------------------------------------------------------------------------------
BugCheck D3, {fffff8800113f2b9, 2, 0, fffff800030f8242} [[B]VERIFIER_ENABLED_VISTA_MINIDUMP[/B]]
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )
Followup: MachineOwner
---------------------------------------------------------------------------------------
BugCheck A, {fffffa81038bff88, 2, 0, fffff800030d8458}
Probably caused by : memory_corruption ( nt!MiCheckProtoPtePageState+c8 )
Followup: MachineOwner
---------