New
#11
Okay Archie I ran it again, And it crashed a couple times before I turned it off.
So heres the crash dumps!
Okay Archie I ran it again, And it crashed a couple times before I turned it off.
So heres the crash dumps!
It is not showing any cause there.
Disable verifier, and enable it once again, making it sure that you are following the steps proprly.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {5003, fffff781c0000000, 52, 54000000a0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21ce4 ) Followup: MachineOwner ---------
At the same time, 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, per RAM module per slot.
So after a while I thought the computer just fixed itself, I hadn't had any BDOD's for a while and forgot to mark this thread as solved and inform everyone It had fixed itself.
Unfortunately I was wrong and the computer has started blue screening again with a "IRQL_GT_ZERO_AT_SYSTEM_SERVICE" with a 0x4a error message.
Attached dump files below if anyone would be kind enough to take a look.
Again apologies for abandoning the thread :/
[EDIT] also running driver verifier again and will test my RAM tonight. So I will post the result of that soon hopefully.
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. Post it following the Blue Screen of Death (BSOD) Posting Instructions.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.
Okay so I ran driver verifier for 24 hours, not one crash! Turned it off and restarted and the computer crashed maybe half an hour later! So i'm uploading the latest crashes after driver verifier. But I really think it must be a hardware problem. So going to run memtest when I get the chance Arc!
I'll post back with the memtest results when I can and here is the latest crash dumps.
A search revealed that you are using nForce as the chipset driver, and that includes nvmf6264.sys as the network controller driver. You need to try to update nForce, as it contains not only the network controller, but also storage controller and a lot of other vital drivers.
Go to Drivers - Download NVIDIA Drivers, search for nForce, as per your motherboard's chipset specifications.Code:fffff880`04c69000 fffff880`04cba500 nvmf6264 (deferred) Image path: \SystemRoot\system32\DRIVERS\nvmf6264.sys Image name: nvmf6264.sys Timestamp: Fri Jul 31 05:18:18 2009 (4A723142) CheckSum: 0005B9A8 ImageSize: 00051500 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Or you may update the chipset drivers from ASRock > Products > Motherboard > N68C-S UCC > Download
Ahh those pesky nForce drivers again! I'll try and sort it out then.
Okay Arc I've installed what I believe are the correct nforce drivers. But I'm still getting Blue screens, Would you mind glancing through again to check if its still the nforce drivers? Thanks in advance!
Th3PinkNinj4, sorry to say, but still it is the same, nVidia nForce network driver.
And the driver is really old, despite of any updates.Code:fffff880`0bd07298 fffff880`04c5eb71Unable to load image \SystemRoot\system32\DRIVERS\nvmf6264.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvmf6264.sys *** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys nvmf6264+0x6b71
It is the problem with the nvidia chipset, that the driver updates are not available. If there is no feasible updates, I guess you have to compromise with it.Code:fffff880`04c58000 fffff880`04ca9500 nvmf6264 T (no symbols) Loaded symbol image file: nvmf6264.sys Image path: \SystemRoot\system32\DRIVERS\nvmf6264.sys Image name: nvmf6264.sys Timestamp: Fri Jul 31 05:18:18 2009 (4A723142) CheckSum: 0005B9A8 ImageSize: 00051500 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Still, I will ask Northernsoul55 to have a look, as he has better perception of nvidia chipset. ATM he is out of an ISP, so he may be a little late to reply. Please be patient.
Okay thank you Arc. Do you think the fact that the chipset is so old that it mightn't be able to keep up with the stress I'm putting it under? I play alot of modern games and do alot of video editing which is sure to strain the PC.