lots of BSOD, one problem to the next

Greebz · 26 Jul 2011

Hello, I have been experiencing a lot of BSOD over the past 2 weeks. My old video card fried itself, and since installing the new one after about a week it has been problem after problem. I have tried everything I can think of to resolve the issue, from reseating the video card to uninstalling and then reinstalling different versions of the video driver. Any help would be GREATLY appreciated.

Windows 7 Home Premium (x64) Service Pack 1 (build 7601) OEM
Originally Windows XP Pro
age of system is about 3-4 years cannot remember exactly
last reformat and install of Win 7 was on feb 15th 2011

zigzag3143 · 26 Jul 2011

Greebz said:

Hello, I have been experiencing a lot of BSOD over the past 2 weeks. My old video card fried itself, and since installing the new one after about a week it has been problem after problem. I have tried everything I can think of to resolve the issue, from reseating the video card to uninstalling and then reinstalling different versions of the video driver. Any help would be GREATLY appreciated.

Windows 7 Home Premium (x64) Service Pack 1 (build 7601) OEM
Originally Windows XP Pro
age of system is about 3-4 years cannot remember exactly
last reformat and install of Win 7 was on feb 15th 2011

Most if not all were Related to ad-aware security program from Lavasoft. I would remove it.

Greebz · 26 Jul 2011

already has been removed, did that in week 1 of debugging the issue, yet it still persists, can happen randomly, and always happens while running video games, even older ones such as knights of the old republic

Greebz · 26 Jul 2011

thank you for the quick reply though zigzag

MvdB · 26 Jul 2011

Hello Greebz, welcome to SF!

If you've already followed Zigzags advice, next thing is to update your ATI graphics drivers. Your latest dump blames one of the ATI files

HTML Code:

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000020e, A PNP IRP has an invalid status. Any PNP IRP must have its status initialized
    to STATUS_NOT_SUPPORTED.
Arg2: fffff88005363432, The address in the driver's code where the error was detected.
Arg3: fffff9801004cea0, IRP address.
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0xc9_20e

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  20e

FAULTING_IP: 
atdcm64a+2432
fffff880`05363432 89442478        mov     dword ptr [rsp+78h],eax

FOLLOWUP_IP: 
atdcm64a+2432
fffff880`05363432 89442478        mov     dword ptr [rsp+78h],eax

IRP_ADDRESS:  fffff9801004cea0

DEVICE_OBJECT: 0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  InstallManager

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f6e3dc to fffff80002ae7d00

STACK_TEXT:  
fffff880`05e62208 fffff800`02f6e3dc : 00000000`000000c9 00000000`0000020e fffff880`05363432 fffff980`1004cea0 : nt!KeBugCheckEx
fffff880`05e62210 fffff800`02f7847a : fffff800`02f6c9f0 fffff880`05363432 fffff980`1004cea0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`05e62250 fffff800`02f79483 : 00000000`0000020e 00000000`00000000 fffff980`1004cea0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`05e622a0 fffff800`02f7a115 : 00000000`00000000 fffffa80`06239402 fffff980`1004cea0 fffff800`02f6fe56 : nt!VfErrorReport1+0x63
fffff880`05e62340 fffff800`02f6e1e0 : fffff980`1004cfb8 fffffa80`050689b0 00000000`00000000 fffff800`02f7ce3f : nt!VfPnpVerifyNewRequest+0x45
fffff880`05e62370 fffff800`02f86b33 : fffffa80`062394b0 fffffa80`050689b0 fffff980`1004cea0 fffffa80`0683a530 : nt!VfMajorVerifyNewRequest+0x70
fffff880`05e623c0 fffff800`02f86d86 : 005f0056`00000001 fffffa80`00000001 fffffa80`00000001 fffff880`05363432 : nt!IovpCallDriver1+0x483
fffff880`05e62470 fffff800`02f8abb2 : fffff980`1004cea0 00000000`00000002 fffff980`1004cea0 fffff800`02d52adc : nt!VfBeforeCallDriver+0x186
fffff880`05e624d0 fffff880`05363432 : fffff980`0e180ee0 00000000`00000002 fffffa80`054a0640 fffffa80`07359010 : nt!IovCallDriver+0x502
fffff880`05e62530 fffff980`0e180ee0 : 00000000`00000002 fffffa80`054a0640 fffffa80`07359010 00000000`00000000 : atdcm64a+0x2432
fffff880`05e62538 00000000`00000002 : fffffa80`054a0640 fffffa80`07359010 00000000`00000000 fffff880`05e62590 : 0xfffff980`0e180ee0
fffff880`05e62540 fffffa80`054a0640 : fffffa80`07359010 00000000`00000000 fffff880`05e62590 fffff880`05e62580 : 0x2
fffff880`05e62548 fffffa80`07359010 : 00000000`00000000 fffff880`05e62590 fffff880`05e62580 00000000`00000000 : 0xfffffa80`054a0640
fffff880`05e62550 00000000`00000000 : fffff880`05e62590 fffff880`05e62580 00000000`00000000 fffff980`1004cea0 : 0xfffffa80`07359010


STACK_COMMAND:  kb

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  atdcm64a+2432

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atdcm64a

IMAGE_NAME:  atdcm64a.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b4e8192

FAILURE_BUCKET_ID:  X64_0xc9_20e_VRF_atdcm64a+2432

BUCKET_ID:  X64_0xc9_20e_VRF_atdcm64a+2432

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

Please try: Latest AMD Catalyst Video Driver for Windows 7

Greebz · 26 Jul 2011

Sorry, I guess I did not post enough information, I've only been running on a few hours of sleep a night so I guess that could be the culprit.

So I have the latest driver, does not work. I believe this all started because the old video card had been overclocked(I did not order this on the PC from IBUYPOWER but apparantly they did it anyways). So when that fried and I installed the new video card, I did not reset the overclocking and that cause several crashes followed by the screen on startup that said the previous attempt at overclocking has failed(or something close to that). I reset the bios and that problem is now gone. The adaware driver problem I fixed awhile ago as well, and then I kept getting dxgkrnl.sys, dxgmm1s.sys and now the last one was acdm64a.sys(or something close to that my notes are at home and I am at work I will post that this afternoon as needed). I have reseated the video card several times, as well as the RAM. I have tested all RAM and each stick works fine. I have fixed it enough so that I can run most applications and browsing without any bsods, however I still get them while gaming. Sometimes after the BSOD, when I power on the computer, everything turns on and everything starts running except the HDD. Could this be a HDD error? Or could it possibly be PWS related? I was hoping it was just software related so I do not have to spend anymore money.

Any insight would be fantastic. Thanks again in advance and sorry for the lack of information in the first post.

MvdB · 26 Jul 2011

Could you specify, also timewise, exactly what sequence you followed? have you been able to set OC back to default?
What were the settings when this dump was created? etc...

Greebz · 26 Jul 2011

I fixed the overclocking issue about 2 or 3 days ago. So the most recent dumps of the atdcm64a.sys should be after that. I just stumbled upon that issue and reset it to defaults.

So first was the old video card failure. I didnt do much with the PC until the new card arrived, and then I uninstalled the old video card drivers, installed the new card, and then ran the driver installation cd. Then I was gettign various BSODs still, even if I just left the PC on overnight without running anything, I thought it might be overheating but I found that to not be the case. now it seems to mostly be the video drivers that are causing problems, I have tried the CD driver version and the latest driver from the amd website, neither of which solves the problem.

Im starting to think it may be hardware related which is a huge dissapointment. Hopefully it is not though.

Any ideas on what else I can try?

MvdB · 26 Jul 2011

If I understand correctly, you get random BSOD's, mostly, but not only when gaming?
If so, though it is a drag, please try running in Safe mode for a relatively long amount of time. Such that you would normally get another BSOD? If you don't... then it still looks like drivers.

Greebz · 26 Jul 2011

It looks like it may just be gaming now. I left the computer on all last night and it had zero problems this morning. I will check when I get home from work and see if that is still the case. Its just hard to believe its hardware related when I get the BSOD in old and new games.

If it is the driver, and I have tried the CD version of the driver that came with the card and the latest driver as downloaded from amd, where do I turn to next?