Windows 7: Graphics Card problem

ohjimbo · 05 Jun 2010

Okay I have an interesting problem that I cant seem to figure out at all. Whenever I restart my computer, I seem to get a blue screen, the only way to prevent is to remove/insert the VGA switch card, and then it will start fine.

I am currently using my Radeon HD 4650 Graphics card, not the integrated one. However, I cant use the integrated one anyways, it isnt showing up in device manager, and there is no signal when i plug the monitor into it.

One more thing, even if i get my computer to start, it will randomy awake from sleep mode with no one near it. And then the resolution settings will be wrong on the monitor (800x600 instead of its normal 1920x1080. This has been so frustrating. I am going to include my dump files if that helps...

And I have already tried updating the Radeon HD 4650 driver

Thanks

Fumz · 05 Jun 2010

I had to look up what an MVP Switch card was. Never heard of such a thing. Is there any reason why you need to have it installed? It's my understanding that the switch card exists to change your pci-e lane from 8x to 16x. However, even at 8x, your card isn't saturating the bus, so "forcing" 16x is pointless. Does the board boot up fine without the switch card installed?

If my (limited) understanding is off, plz lemme know.

ohjimbo · 05 Jun 2010

I wish it was that simple, but I constantly have to rotate between putting it in and taking it out. If it was in already, I have to remove it for it to boot properly. If it was out, then I have to insert it. I really don't understand why this works, but it does...
Its very frustrating

NoN · 05 Jun 2010

You might want to install DirectX again, then uninstall all your graphic card drivers, stop the computer, plug your card then reboot and see if reinstall the drivers works....

ohjimbo · 05 Jun 2010

I just tried all of that, a couple of things though...
-When I tried to reinstall directx, im not sure if its suppose to install super fast, bc
it was instant
-During the first restart I the computer failed to load the welcome screen and restarted, but worked fine then and again during another restart

I included the dump file, I guess only time will tell if this finally solved my problem

CarlTR6 · 05 Jun 2010

I looked at your five most recent dumps. All of them point to hardware errors specifically device drivers and memory.

Quote:

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

BSOD Index

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

BSOD Index

STOP 0x0000001A: MEMORY_MANAGEMENT

Usual causes: Device driver, memory, kernel

BSOD Index

STOP 0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH

Usual causes: Device driver, System DLL corruption, Faulty hardware in I/O path (a disk error, faulty RAM, or a corrupted page file), BIOS

BSOD Index

Code:

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

BugCheck 1E, {ffffffffc0000005, fffff80002afd13c, 0, ffffffffffffffff}

Probably caused by : memory_corruption ( nt!MiAllocatePagedPoolPages+4fc )

Followup: MachineOwner

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  CCC.exe


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

BugCheck A, {2000000, 2, 1, fffff80002a7f14c}

Probably caused by : ntkrnlmp.exe ( nt!KeWaitForSingleObject+13c )

Followup: MachineOwner

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

BugCheck 1A, {41284, fffff9800175a001, 29d, fffff780c0000000}

Probably caused by : CI.dll ( CI!I_ReloadCatalogs+14a )

Followup: MachineOwner

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

Use !analyze -v to get detailed debugging information.

BugCheck C0000221, {fffff8a0001e3010, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5ff )

Followup: MachineOwner

I looked at one of the files listed in your dumps as a possible cause. It is CI.dll.

Quote:

The process Alcohol 120% or ci.dll belongs to the software ci.dll or Alcohol 120% by Alcohol Soft Development Team.

Description: ci.dll is located in the folder C:\Windows\System32.

This .dll file is a Browser Helper Object (BHO) that runs automatically every time you start your Internet browser

Alcohol is a known cause of BDOD's in Win 7. I also found that CI.dll can be a legitimate Windows dll as well as a malware BHO.

Start by uninstalling Alcohol if you have it installed.

Next download and install Malwarebytes and do a thorough scan of your system.

After you have done this, post back and we will take things from there.

ohjimbo · 05 Jun 2010

I don't have Alcohol installed, never used it before. Also I did download Malwarebytes and did a full scan, however it came up clean.

Aphelion · 06 Jun 2010

Does the motherboard have the latest BIOS installed? If not, I would consider flashing to the most recent BIOS.

Also, in the BIOS make sure the onboard video is disabled, doesn't matter if it has drivers loaded or not, it could be causing a problem.

Until you get this resolved, instead of removing/inserting the VGA switch card, try shutting off the power either by using the switch on the back of your power supply (if you have one) or unplugging from wall current for a couple of minutes.

Ap

p.s. I have ci.dll on my PC, related to Microsoft Code Integrity? (Lower case i)

CarlTR6 · 06 Jun 2010

Quote: Originally Posted by ohjimbo

I don't have Alcohol installed, never used it before. Also I did download Malwarebytes and did a full scan, however it came up clean.

It looks like your CI.dll is OK and not malware. Next, let's look at memory.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.

If Memtest checks back clean after 5+ passes, follow these instructions for enabling driver verifier: Using Driver Verifier to identify issues with Drivers
Please follow these instructions in order to run it:

Quote:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Fumz · 06 Jun 2010

Quote: Originally Posted by ohjimbo

I just tried all of that, a couple of things though...
-When I tried to reinstall directx, im not sure if its suppose to install super fast, bc
it was instant

No, it's not instantaneous; it takes a bit. My memory is fuzzy, but anywhere from 20-40 seconds sounds about right.

Did you get the Feb. 2010 redist that updates all versions of DX?

Download details: DirectX Redist (February 2010)

Windows 7: Graphics Card problem

Graphics Card problem problems?