BSOD pops up every time when i start my system someone help pls!!!

rankxx said:

I have installed my Graphics driver ATI HD 5670.After which i have been getting BSOD.

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.

It is needed to see that file before we suggest anything.
_____________________________________________

Code:

Unable to load image \SystemRoot\system32\DRIVERS\igdkmd32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 9548f554, 921e07cc, 0}

Probably caused by : igdkmd32.sys ( igdkmd32+82554 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 9548f554, The address that the exception occurred at
Arg3: 921e07cc, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
igdkmd32+82554
9548f554 8b11            mov     edx,dword ptr [ecx]

TRAP_FRAME:  921e07cc -- (.trap 0xffffffff921e07cc)
ErrCode = 00000000
eax=8769c3b8 ebx=86d330d8 ecx=00000000 edx=00000000 esi=86d3349c edi=86d334a0
eip=9548f554 esp=921e0840 ebp=921e08c8 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
igdkmd32+0x82554:
9548f554 8b11            mov     edx,dword ptr [ecx]  ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from 95512916 to 9548f554

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
921e08c8 95512916 86d41000 86d3349c 955138ad igdkmd32+0x82554
921e0938 954a5abe 86d41000 876a6000 921e095c igdkmd32+0x105916
921e0948 954aeba2 86d41000 00000000 876a6000 igdkmd32+0x98abe
921e095c 954b17c5 86d41000 c000000d 921e0ad8 igdkmd32+0xa1ba2
921e096c 9543ad04 86d41000 87268d48 000000d5 igdkmd32+0xa47c5
921e0ad8 94b14d20 86d41000 921e0c58 921e0b84 igdkmd32+0x2dd04
921e0b00 94b149e0 86d31740 86d41000 921e0c58 dxgkrnl!DpiDxgkDdiStartDevice+0x3a
921e0c70 94b14516 86d33020 00000001 00000000 dxgkrnl!DpiFdoStartAdapter+0x40d
921e0c98 94aff359 00000000 8bdf09c8 00000040 dxgkrnl!DpiFdoStartAdapterThread+0xe8
921e0ca0 8bdf09c8 00000040 00000000 9b415911 dxgkrnl!DpiSessionCreateCallback+0x25
921e0cb8 8bdf0e09 921e0cd0 9b414322 00000001 watchdog!SMgrSessionOpen+0xa4
921e0cc0 9b414322 00000001 ffffbc97 921e0d18 watchdog!SMgrNotifySessionChange+0x19
921e0cd0 9b415e98 00000001 00000000 9b6088d0 win32k!DrvNotifySessionStateChange+0x42
921e0d18 9b415992 001ef708 921e0d34 832516da win32k!InitializeGreCSRSS+0x16
921e0d24 832516da 00000040 00000044 001ef724 win32k!NtUserInitialize+0x81
921e0d24 771b6194 00000040 00000044 001ef724 nt!KiFastCallEntry+0x12a
001ef724 00000000 00000000 00000000 00000000 0x771b6194


STACK_COMMAND:  kb

FOLLOWUP_IP: 
igdkmd32+82554
9548f554 8b11            mov     edx,dword ptr [ecx]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  igdkmd32+82554

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdkmd32

IMAGE_NAME:  igdkmd32.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c0688d2

FAILURE_BUCKET_ID:  0x8E_igdkmd32+82554

BUCKET_ID:  0x8E_igdkmd32+82554

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x8e_igdkmd32+82554

FAILURE_ID_HASH:  {185607b2-53cb-f152-3f8e-b1e142b86ee1}

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

3: kd> lmvm igdkmd32
start    end        module name
9540d000 95ce9000   igdkmd32 T (no symbols)           
    Loaded symbol image file: igdkmd32.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd32.sys
    Image name: igdkmd32.sys
    Timestamp:        Wed Jun 02 22:07:38 2010 (4C0688D2)
    CheckSum:         00867197
    ImageSize:        008DC000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

msinfo32.nfo file is one of the most important places to check what is going on there. This file is an integral part of the DM logs. As it was not present there, I had to ask you for it.

The crash dumps say that the issue is caused by the Intel graphics driver.

You have employed AMD Radeon HD 5670 GPU. the intel graphics driver is rightly disabled as I am seeing.

Code:

igfx    igfx    c:\windows\system32\drivers\igdkmd32.sys    Kernel Driver    No    Manual    Stopped    OK    Ignore    No    No

Then what is the problem? Why it is causing BSODs?

Because it is trying to start automatically whenever windows is starting.

Code:

IgfxTray    c:\windows\system32\igfxtray.exe    Public    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

Then what you need to do to prevent it?

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Hopefully it will stop the issue.



On a precautionary ground .... Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

And Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

Code:

OS Name    Microsoft Windows 7 Ultimate
Version    6.1.7600 Build 7600

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack and Update Center - Microsoft Windows


Let us know the result.