Frequent BSOD even with fresh install and hardware check...

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002ad193c, fffff8800a8e6020, 0}
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : klif.sys ( klif+1cd1f )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002ad193c, Address of the instruction which caused the bugcheck
Arg3: fffff8800a8e6020, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
nt!KeWaitForSingleObject+13c
fffff800`02ad193c f00fba2e07      lock bts dword ptr [rsi],7
CONTEXT:  fffff8800a8e6020 -- (.cxr 0xfffff8800a8e6020)
rax=b41699a106dc3d90 rbx=0000000642ea8568 rcx=0000000000000011
rdx=0000000000000062 rsi=94fffa80055cb090 rdi=fffffa8007918060
rip=fffff80002ad193c rsp=fffff8800a8e6a00 rbp=0000000000000000
 r8=fffff78000000008  r9=0000000000000000 r10=0000000000000000
r11=fffff88003763180 r12=0000000000000000 r13=fffff88003763180
r14=fffff8800a8e6b10 r15=fffffa8007918168
iopl=0         nv up ei pl nz ac pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210213
nt!KeWaitForSingleObject+0x13c:
fffff800`02ad193c f00fba2e07      lock bts dword ptr [rsi],7 ds:002b:94fffa80`055cb090=????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff80002aaab4e to fffff80002ad193c
STACK_TEXT:  
fffff880`0a8e6a00 fffff800`02aaab4e : fffffa80`0570ad00 00000000`0000001b 00000000`00000000 fffff880`03763100 : nt!KeWaitForSingleObject+0x13c
fffff880`0a8e6aa0 fffff800`02acfdbc : ffffffff`ffb3b4c0 94fffa80`055cb090 fffffa80`0570adf0 fffff880`0186e76f : nt!ExpWaitForResource+0xae
fffff880`0a8e6b10 fffff800`02ad3a53 : 00000000`0013fd20 fffffa80`07918060 fffff880`0a8e6ca0 fffff880`0a8e6bb8 : nt!ExAcquireResourceExclusiveLite+0x14f
fffff880`0a8e6b80 fffff960`001a617d : fffff880`00000023 fffffa80`058a7d30 fffff880`021461f0 00000000`745b2450 : nt!ExEnterPriorityRegionAndAcquireResourceExclusive+0x23
fffff880`0a8e6bb0 fffff880`02100d1f : 00000000`00000000 fffff960`001a5fd6 00000000`00041cff fffff880`0a8e6ca0 : win32k!NtUserCallNoParam+0x19
fffff880`0a8e6be0 00000000`00000000 : fffff960`001a5fd6 00000000`00041cff fffff880`0a8e6ca0 00000000`fffdb000 : klif+0x1cd1f

FOLLOWUP_IP: 
klif+1cd1f
fffff880`02100d1f ??              ???
SYMBOL_STACK_INDEX:  5
SYMBOL_NAME:  klif+1cd1f
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: klif
IMAGE_NAME:  klif.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  522decfc
STACK_COMMAND:  .cxr 0xfffff8800a8e6020 ; kb
FAILURE_BUCKET_ID:  X64_0x3B_klif+1cd1f
BUCKET_ID:  X64_0x3B_klif+1cd1f
Followup: MachineOwner
---------

It looks like Kaspersky is responsible for the BSOD's.
Please remove it for testing purpose. Use Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

Microsoft Security Essentials - Free Antivirus for Windows

Malwarebytes - Free

Good and Free system security combination.

Reduce items at start-up: Startup Programs - Change

Perform a clean boot: Troubleshoot Application Conflicts by Performing a Clean Startup

Run a System file check (SFC): SFC /SCANNOW Command - System File Checker

Run Disk Check on your Hard Drive(s): Disk Check

Check for heating issues using Speccy or HWmonitor

Upload a screen shot: Screenshots and Files - Upload and Post in Seven Forums


Post screenshot(s) of your Hard Drive(s) using Crystal Disk Info Software:

• CrystalDiskInfo - Software - Crystal Dew World
• Screenshots and Files - Upload and Post in Seven Forums

Run a Hard Drive test:

• SeaTools for DOS and Windows - How to Use

Hello, thanks a lot for the reply.
I had the time to :
- Uninstall kaspersky
- Install MSE
- Perform a clean boot

Regarding the System file check (SFC), I tried twice to do it, but a BSOD would appear before it finishes...
So I did the next step, a disk check, it was performed before Win 7 boots.
I wanted to do the next steps but even when I'm lunching google chrome, the software would just crash and a BSOD would appear... I'm in safe mode now.

If it might help you, I have attached the new BSOD's since I uninstalled kaspersky...
Thanks for the help (some parts of the logs are in french, if you need a translation tell me)!

Edit: after some further checks, the temps IDLE are correct, no hardware is beyond 50°c, except for a sensor which is at 128°C - 262°F (TMPIN 2)? I think it's a faulty one. I still have a lot of BSOD's, especially with the BCC code 1e ...

Code:

AODDriver2.sys Wed Nov 21 13:44:04 2012 (50AC8644)

AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7
Driver Reference Table - AODDriver2.sys

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center.
Please uninstall the AMD OverDrive program as it can cause BSOD's on your system.
If it's the stand-alone app, uninstall it via Control Panel...Programs...Uninstall a program
If it's in the AMD VISION Engine Control Center, you can uninstall it using the AMD uninstall tool (or uninstall the entire AMD VISION Engine Control Center application through Control Panel

If the device remains a problem in perfmon /report, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect.

Code:

ASACPI.sys Thu Jul 16 09:31:29 2009 (4A5E9F11)

Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities (Win8 versions available from Windows Update as an Optional Update - but check Asus first!)
Driver Reference Table - ASACPI.sys

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Ok , I've uninstalled AMD overdrive via the device manager, as I could not find it in the catalyst install manager...
And for the Asus utility, I've erased all entry from the registry, I will tell you if there are further bsod's...
Another question, should I install the driver for the USB 3.0 or is it a cause for bsod's ? I would download it from here : ASUSTeK Computer Inc. -Support- Drivers and Download M4A88TD-V EVO/USB3 , it is from the Nec electronic corp

Edit : apologies but new bsods occured ..... here are the dmp files.
I am also attaching the data regarding the main HDD ( the Western Digital) and the second one, a Seagate.
It's quite insane though, I have a BSOD almost every hours... I've installed java to run minecraft and I had two bsods in a row... it's seems that I cannot install a thing without causing trouble, it may be an hardware issue ??

Attachment 298435

Attachment 298436

We need to see some more info here.

upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

Upload the list of all the third party drivers Using NirSoft DriverView :

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

Let us know.

You need to try to update the BIOS and chipset.

Get it from ASUSTeK Computer Inc. -Support- Drivers and Download M4A88TD-V EVO/USB3

Let us know after applying those.

** If you are unaware of the procedure of BIOS updating, take the help of somebody who can do it. Iven if a PC technician. A wrong attempt to update the BIOS may be fatal; but the update is needed.

I have successfully updated the bios using the asus ez flash 2 utility in the bios, and regarding the chipset, I used the driver 13.4 downloaded on the official website : AMD Chipset Drivers

Should I install the usb 3.0 driver or not??

I'll let you know if the update of the bios changed something, thanks

Edit: I did not had to wait to see new BSOD's.... here are the dmp files...

Yes, update the USB3 driver too.

But this BSOD is showing some absurd result.

Code:

BugCheck 3B, {c000001d, fffff88003a30bbf, fffff880093b7430, 0}

Unable to load image \SystemRoot\system32\drivers\peauth.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for peauth.sys
*** ERROR: Module load completed but symbols could not be loaded for peauth.sys
Probably caused by : peauth.sys ( peauth+30bbf )

Followup: MachineOwner
---------

This driver cannot be the real cause of a BSOD.

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.

Ef memtest86+ does not show any error, 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.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

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: Speccy - Publish Snapshot of your System Specs .

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