Multiple BSOD's with multiple errors occuring randomly

[Th3PinkNinj4]

[EDIT]
Just realized I uploaded the wrong zip folder, It doesn't have everything in it. Fixed that now though! Sorry about the hassle!

So I built my own PC a a good few months back, and within a month I experienced a BSOD, and now they are very frequent. They can happen three or four times a day, or none for a few days. They don't seem to happen because of any application either. They seem to occur randomly.

The error's that appear to be the most common is the 'driver_irql_not_less_or_equal' and the 'memory_managment' error. Others have occurred I just can't remember them. Another problem I've noticed is that my graphics driver would crash occasionally even though it is up to date.

I use my computer as a gaming pc and for video editing so its under some heavy pressure I would presume. Any help would be much appreciated! I attached the event files aswell.

 

[Arc]

Hello Andy!

► Uninstall the following programs.

• Start Menu\Programs\AVG : Replace with Microsoft Security Essentials - Microsoft Windows
• Start Menu\Programs\DAEMON Tools Pro
• Start Menu\Programs\MagicDisc
• Start Menu\Programs\MagicISO

► Free up the startup.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept the restart.

► Enable Driver Verifier

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck C5[/COLOR], {0, 2, 0, fffff800033fc6fb}
[COLOR=Red]
Probably caused by : Pool_Corruption[/COLOR] ( nt!ExDeferredFreePool+ca7 )

Followup: Pool_corruption
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
[COLOR=Red]
DRIVER_CORRUPTED_EXPOOL (c5)[/COLOR]
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  [COLOR=Red][B]This is
caused by drivers that have corrupted the system pool.  Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.[/B][/COLOR]
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff800033fc6fb, address which referenced memory

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[Th3PinkNinj4]

Hello Arc!

Thank you for your support, I've followed the instructions, been running driver verifier for a while and the computer did BSOD again not too long ago.

So I found what I think is the crash dump file (MEMORY.DMP?) but its around 630mb, how can I compress this down to the seven forums upload limit? I tried using winrar but it came out at 100mb!

Im uploading it to mediafire, but im sure there is a way to compress a file to a certain size right? I will upload the mediafire link when it is done uploading if there is no other way around this.

 

[Th3PinkNinj4]

Nevermind! I realized now I should have just used the seven forums program again.
My bad, anywho here is the new crash dumps!

 

[Arc]

Well it is nVidia nForce network driver.

fffff880`02664a40  fffff880`04afc9e8Unable to load image \SystemRoot\system32\DRIVERS\nvmf6264.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
 nvmf6264+0x299e8[/COLOR]

And it is sufficiently old.

lmvm nvmf6264
start             end                 module name
fffff880`04ad3000 fffff880`04b27080   nvmf6264 T (no symbols)           
    Loaded symbol image file: nvmf6264.sys
    Image path: \SystemRoot\system32\DRIVERS\nvmf6264.sys
   [COLOR=Red] Image name: nvmf6264.sys
    Timestamp:        Thu Aug 12 17:16:06 2010[/COLOR] (4C63DEFE)
    CheckSum:         00064419
    ImageSize:        00054080
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Get the update from Drivers - Download NVIDIA Drivers, search for nForce.

Let us know the results.

 

[Th3PinkNinj4]

So I installed the nforce drivers and then a few hours later my computer BSOD'd again. The error message was "system_service_exception"

Im guessing this isn't a driver problem and is a completely new one?

 

[Arc]

Better you upload the crash dump.

 

[Th3PinkNinj4]

opps, forgot to upload them. I BSOD'd again there with "multiple_irp_complete_requests" so heres the latest crash dumps.

 

[Th3PinkNinj4]

anyone provide any sort of light on this? any input would be much appreciated guys

 

[Arc]

kd> !irp fffffa800ab6b410
Irp is active with 1 stacks 1 is current (= 0xfffffa800ab6b4e0)
 No Mdl: No System Buffer: Thread fffffa80072c6b50:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
>[  e, 0]   0  0 fffffa80087e1890 fffffa800adf3c70 00000000-00000000    
          fffffa80087e1890: Could not read device object or _DEVICE_OBJECT not found

            Args: 00000038 00000038 0012000f 03b2f634

I guess you need to enable DV for one more time.

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[Th3PinkNinj4]

Okay Archie I ran it again, And it crashed a couple times before I turned it off.

So heres the crash dumps!

 

[Arc]

It is not showing any cause there.

*******************************************************************************
*                                                                             *
*                        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
---------

Disable verifier, and enable it once again, making it sure that you are following the steps proprly.
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.

 

[Th3PinkNinj4]

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.

 

[Arc]

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.

   Information

Why 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.

   Warning

Before 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.

   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.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[Th3PinkNinj4]

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.

 

[Arc]

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.

fffff880`04c69000 fffff880`04cba500   nvmf6264   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\nvmf6264.sys
[COLOR=Red]    Image name: nvmf6264.sys
    Timestamp:        Fri Jul 31 05:18:18 2009 [/COLOR](4A723142)
    CheckSum:         0005B9A8
    ImageSize:        00051500
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Go to Drivers - Download NVIDIA Drivers, search for nForce, as per your motherboard's chipset specifications.

Or you may update the chipset drivers from ASRock > Products > Motherboard > N68C-S UCC > Download

 

[Th3PinkNinj4]

Ahh those pesky nForce drivers again! I'll try and sort it out then.

 

[Th3PinkNinj4]

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!

 

[Arc]

Th3PinkNinj4, sorry to say, but still it is the same, nVidia nForce network driver.

fffff880`0bd07298  fffff880`04c5eb71Unable to load image \SystemRoot\system32\DRIVERS\[URL="http://www.carrona.org/drivers/driver.php?id=nvmf6264.sys"]nvmf6264.sys[/URL], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=nvmf6264.sys"]nvmf6264.sys[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=nvmf6264.sys"]nvmf6264.sys[/URL]
 nvmf6264+0x6b71

And the driver is really old, despite of any updates.

fffff880`04c58000 fffff880`04ca9500   nvmf6264 T (no symbols)           
    Loaded symbol image file: nvmf6264.sys
    Image path: \SystemRoot\system32\DRIVERS\nvmf6264.sys
[COLOR=Red]    Image name: nvmf6264.sys
    Timestamp:        Fri Jul 31 05:18:18 2009[/COLOR] (4A723142)
    CheckSum:         0005B9A8
    ImageSize:        00051500
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

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.

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.

 

[Th3PinkNinj4]

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.