Constant BSOD with alternating errors.

[Versochi]

Write this once and I actually got a BSOD just before finishing it so don't mind the shortness I'm just frustrated right now.

To keep it short and sweet:

Keep getting BSOD, windows saying its a memory problem, found the faulty RAM an removed it, windows memory diagnostic tool saying no problems found. A day goes by... BSOD, then the diagnostic finds hardware errors.

Various BSOD codes, ill list some.
and my pc specs.

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

Additional information about the problem:
BCCode: c2
BCP1: 0000000000000007
BCP2: 000000000000109B
BCP3: 0000000000150010
BCP4: FFFFFA80025DBAE0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\032713-63196-01.dmp
C:\Users\*********\AppData\Local\Temp\WER-94318-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


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

Additional information about the problem:
BCCode: 109
BCP1: A3A039D8960E9784
BCP2: B3B7465EE88B66DA
BCP3: FFFFF80002C1487F
BCP4: 0000000000000001
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\032713-36176-01.dmp
C:\Users\*********\AppData\Local\Temp\WER-68125-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

SPECS:
Dell OptiPlex 745
Intel chipset Q965
ATI Radeon HD 4550
DDR2 Memory - 3/4 slots occupied (3072mbytes)

Will upload dumps in a second just want to post incase of BSOD

 

[soundguruman]

Many times a driver has been installed or updated which is incompatible.
Try starting in safe mode, and turning the drive back to a previous date (before the driver installed) with system restore.
OR, in safe mode, rolling the drivers back to an older driver.
Turn off automatic updates to prevent the same thing from repeating again. I have actually seen this happen on older computers.
The driver installs, and the unit BSODs. Then you get rid of the driver, and it works again.
Then it automatically updates, and BSODs again...see what I'm saying?

 

[Brillianten]

Hmm, yes it can be the solution, but in my case, this will not work, no drivers to roll back to, so how to obtain and install drivers in safe mode whn u get them fresh, i suppose thold must be removed, first, and then what? Maybe the problem has to do with the installer and not the driver as u hint at? How to solve that in win7?

 

[soundguruman]

Hmm, yes it can be the solution, but in my case, this will not work, no drivers to roll back to, so how to obtain and install drivers in safe mode whn u get them fresh, i suppose thold must be removed, first, and then what? Maybe the problem has to do with the installer and not the driver as u hint at? How to solve that in win7?

You start in safe mode with networking. Then you can download and install drivers. You can also use system restore in safe mode.

 

[Versochi]

Many times a driver has been installed or updated which is incompatible.
Try starting in safe mode, and turning the drive back to a previous date (before the driver installed) with system restore.
OR, in safe mode, rolling the drivers back to an older driver.
Turn off automatic updates to prevent the same thing from repeating again. I have actually seen this happen on older computers.
The driver installs, and the unit BSODs. Then you get rid of the driver, and it works again.
Then it automatically updates, and BSODs again...see what I'm saying?

Which drives should I be rolling back?

Just some extra info:
Removed Catalyst Control Center 13.1 and wasn't using catalyst and PC was running fine, Thursday-Today (just recently) got another BSOD with:

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

Additional information about the problem:
BCCode: 109
BCP1: A3A039D894E92672
BCP2: B3B7465EE765F5D8
BCP3: FFFFF80002C14810
BCP4: 0000000000000001
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\033013-37830-01.dmp
C:\Users\*********\AppData\Local\Temp\WER-53929-0.sysdata.xml

Used WhoCrashed and this is what it's telling me:

On Sat 30/03/2013 10:05:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\033013-37830-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x109 (0xA3A039D894E92672, 0xB3B7465EE765F5D8, 0xFFFFF80002C14810, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I think the problem is with the video card but im not sure how to go about fixing it

 

[0Markz0]

This is graphics card issue, but 13.1 should work properly. Last driver that worked without any issues was 12.3 WHQL.
Try installing 12.3 and remove every ATI/AMD folder and registry setting before installing it and if it works properly after a week or so go for 13.1 or newer and do not go for beta drivers (harder to remove). I've seen (tested) that those will only mess up your windows.

 

[Versochi]

This is graphics card issue, but 13.1 should work properly. Last driver that worked without any issues was 12.3 WHQL.
Try installing 12.3 and remove every ATI/AMD folder and registry setting before installing it and if it works properly after a week or so go for 13.1 or newer and do not go for beta drivers (harder to remove). I've seen (tested) that those will only mess up your windows.

Best way to go about this? I have DriverFusion but it won't delete the registry values

 

[Versochi]

So I'm currently installing 12.3 CCC, pc crashed the first time I tried to after I chse Express and it started installing it crashed but second time its working.

Is there any way to test to see if my video card is working now?

Thanks

---Awaiting the next bsod then I shall be back! ---

 

[0Markz0]

You will see it easily with games or benchmarks that needs GPU processing a lot, but if you know what you're doing you could test your card with Furmark and if you're still getting errors with 12.3 driver, uninstall it, download Treexy Driver Fusion (was driver sweeper before) and remove all that are left from old/newer drivers, reboot, download and install 13.1 drivers and if you're still getting BSOD/errors i would at this point check that my card and ram is properly attached into motherboard and also check wire connections.
If you still get that same crap after all that and memory check/test doesn't give you any issues run repair from windows dvd or re-install windows, because something is locked up in your system files (i do hope driver fusion will fix it before it goes to that).

I had similar issue about 7 months back, but it happened after moving from beta drivers to stable versions (lots of bsods and memory errors) and those were fixed after uninstalling and sweeping all that was left from beta drivers which was pain in the a** to do. Almost sent my card back thinking it was faulty card.

Major Geeks\Driver Fusion info: This program may offer to install third party programs that are not required for the program to run. These may include a toolbar, changing your homepage, default search engine or other third party programs. Please watch the installation carefully to opt out.

 

[Brillianten]

Hmm, yes it can be the solution, but in my case, this will not work, no drivers to roll back to, so how to obtain and install drivers in safe mode whn u get them fresh, i suppose thold must be removed, first, and then what? Maybe the problem has to do with the installer and not the driver as u hint at? How to solve that in win7?

You start in safe mode with networking. Then you can download and install drivers. You can also use system restore in safe mode.

Reply. no not nesseceary, problem solved, it was the Trend int sec that was the culprit in my case, seem like Crysis 3 dislike antivirusprogrammes and alike, in general. unistalled it, played trough, then unistalled crysis, everything else works just fine now. am now playing bioshock inf, and it works as a charm.No more bsods.
To bad if u buy certain games, u need to unistall versions thats to old of antiv/int sec..progr and buy new ones...just saying it..not the first time this has happened, maybe its sorts of unfair compettition that the customer has to pay for? hrmmmh..