Random BSODs shortly after formatting

[Zarlax]

So, I formatted my PC the other day (Win 7 home premium 64bit), and have been getting a few BSODs, with varying errors, including "DRIVER_POWER_STATE_FAILURE" and "IRQL_NOT_LESS_OR_EQUAL".

Before formatting, I occasionally got the BSOD "MEMORY_MANAGEMENT", but it wasn't regular enough that I looked for help for it.

My PC hardware is 2-3 years old, so shouldn't be kicking the bucket just yet.

I'd like someone to look at the dump file thing and perfmon report (I hope i've done everything correctly as the instructions said )

Thanks for any help in advance

 

[zigzag3143]

Several issues

1-Related to Rt64win7.sys 8101E/8168/8169 NDIS 6.20 64-bit Driver from Realtek Corporation. Yours from before win 7 was released. Update to newest.

2-asacpi.sys (yours from 2005)
Asacpi.sys

The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).

Download and install it.

Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (not before).

If you are still crashing after these please upload you DMPS.

 

[Zarlax]

Thanks!

I've followed these steps and will now hope for the best
If I don't return, assume my PC is cured :>

 

[zigzag3143]

Thanks!

I've followed these steps and will now hope for the best
If I don't return, assume my PC is cured :>

No news is good news.

 

[Zarlax]

Unfortunately, I just had another BSOD. (Although the PC just crashed and restarted without actually showing the screen)

I'm attaching the mini-dump for this one and the little error message it came up with when I logged back in.

Thanks in advance

 

[Zarlax]

Edit: it would help if i actually attached it

 

[zigzag3143]

Edit: it would help if i actually attached it

You appear to have two malware apps installed. Avast and SBAMSvc.exe Software Anti Malware Service from Sunbelt Software

This crash was fairly inconclusive but points to memory management.


I would remove both the above and replace with MSE

Avast can be a contributing cause of BSOD'S . Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST


http://files.avast.com/files/eng/aswclear5.exe

Microsoft Security Essentials - Free Antivirus for Windows

 

[Zarlax]

Okay i've done the above steps for now!

Thanks zigzag :>

 

[Zarlax]

Noooooooo!

Ahhhhhh! It was going so well!

I just had another crash. The bluescreen didn't actually appear but here is the error message I got when I rebooted:

--------------------------------------

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA8005161010
BCP2: FFFFF88003F6EAE4
BCP3: 0000000000000000
BCP4: 000000000000000D
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\041612-20919-01.dmp
C:\Users\CHRIS\AppData\Local\Temp\WER-56768-0.sysdata.xml

--------------------------------------

I've also attached new reports just in case

Thanks!

 

[writhziden]

These are all stop 0x116 VIDEO_TDR_FAILURE conditions.

It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash. As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds. If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating. Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU. Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference. If so, it might be as simple as dust buildup and subsequently inadequate cooling.

The above quote was taken from http://www.sevenforums.com/crashes-debugging/25912-bsod.html#post280172, which is linked to in usasma's thread about this error. Closely follow the first three posts of usasma's thread outlining http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html and proceed through each step. Let us know if you need further help.


You also have this problem device:

SBRE	ROOT\LEGACY_SBRE\0000	This device is not present, is not working properly, or does not have all its drivers installed.

SBRE, is reporting "tv_ConfigMgrErr24". - Microsoft Answers