Few different BSOD at random times

I get random different BSOD errors

Hello, MirkovicTNT. I will try to help you with this. First please add the manufacturer and model of you PSU to your system specs. You did very well filling those out. Also, most of the files were missing from the uploaded files. Please re run the www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html#option2 and upload all of the files.

You had 6 dump files, 5 today and one Yesterday. They all give different stop codes and several different reasons. Here is what they said.

Code:

fffff880`083176a8  fffff880`048cb67aUnable to load image atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
atikmdag+0xb067a

Code:

 atikmdag
start             end                 module name
fffff880`0481b000 fffff880`053ce000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Mon Apr 29 21:07:09 2013 (517F274D)
    CheckSum:         00B6397D
    ImageSize:        00BB3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

That is your graphics driver and as you can see, needs to be updated. Please do it this way.

I am going to give you some links that will help you get a good clean install and not have any drivers you don't need that will conflict with other drivers. Download a WHQL driver from https://www.sevenforums.com/graphic-c...ndows-7-a.html . Once you have them downloaded, uninstall you current driver from control panel. next clean up any left over drivers from following this tutorial Drivers - Clean Left over Files after Uninstalling and select only ATI Display Drivers. After you have done that and rebooted, install the new driver, only select custom install and install only what you have to. Very few people need most of what they include. You do not need the audio/HDMI drivers as you already have that in your Motherboard drivers. Unless there is some reason you need them, the only thing you really need is the Display Driver.

Also was

Code:

fffff800`00b99b38  fffff880`0406f337Unable to load image Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
 Rt64win7+0x5337

Code:

 Rt64win7
start             end                 module name
fffff880`0406a000 fffff880`0409c000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Thu Feb 26 03:04:13 2009 (49A65B0D)
    CheckSum:         0002EB30
    ImageSize:        00032000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

That is your Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC, and needs to be updated. You should be able to update it from your motherboard site for your motherboard.

This is the one which concerns me most.

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, 347c8, 2, 6a5ee}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
Followup: MachineOwner

That is your ram and if this is true it could make every dump file give wrong information. Also, all of your dump files listed different error and bug codes which is a sign of faulty ram.

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes, all run at the same time, to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask.

I would download it and see if there s a newer version. The version you have is 2009, so a newer one shouldn't be too hard. Let me know how memtest86+ comes out.

MirkovicTNT, Again you have 3 different dumps with different stop codes and reasons.

Code:

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffffa80018372b0, the pool entry being checked.
Arg3: fffffa80018372e0, the read back flink freelist value (should be the same as 2).
Arg4: fffffa80018372b0, the read back blink freelist value (should be the same as 2).
 
 
fffff880`084755b8  fffff880`02d2125fUnable to load image atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
 atikmpag+0x625f

That is your video card driver

Code:

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005001, The subtype of the bugcheck.
Arg2: fffff781c0000000
Arg3: 000000000000240b
Arg4: fffff8a0036ad009

Memory again

Code:

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000200000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
 bit 0 : value 0 = read operation, 1 = write operation
 bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800030c6f35, address which referenced memory

Be sure to make a restore point before doing anything. The link is below for how to do it. Please sort thr drivers by provider and enable all drivers not provided by Microsoft.

   Warning

Be sure to create a System Restore point before proceeding further System Restore Point - Create

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

   Information

What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.

What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.

   Warning

Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. 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, do a System Restore to a point you made earlier.

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

Is this the power supply your system has?

http://www.itsvet.com/proizvod/ms-in...upply/163/1051

Please upload the Blue Screen of Death (BSOD) Posting Instructions Again to see if it may provide some further info. By turning the power off and back on made it start, it sounds like a power supply problem.