BSOD Randomely Happening on Laptop

Running a Toshiba laptop approx 2 years old. It's a 2ghz dual core with 2gb ram. Was running Win XP Pro which came pre installed from factory but BSOD was happening at random times and regularly.

Updated with a fresh install of Windows 7 Ultimate 32 bit and installed AVG AV and Office 2007. However after updating Win 7 with all current MS updates BSOD started again and is happening regularly once more.

Have posted stats in zip folder as required and hoping someone can lead me down the path to solving this as I am at my wits end.

Thanks

Please remove AVG and use MSE
AVG is causing these BSODs
Virus, Spyware & Malware Protection | Microsoft Security Essentials

Code:

avgfwd6x.sys        0x8d87e000    0x8d88f000    0x00011000    0x4c3a71d5    12/07/2010 05:37:25                
AVGIDSEH.Sys        0x88600000    0x88609000    0x00009000    0x4c8ea9cb    14/09/2010 02:46:35                
avgldx86.sys        0x8dd23000    0x8dd5e400    0x0003b400    0x4c858bc7    07/09/2010 04:48:07                
avgmfx86.sys        0x82e00000    0x82e0c000    0x0000c000    0x4c858bc1    07/09/2010 04:48:01                
avgrkx86.sys        0x887f6000    0x887fab80    0x00004b80    0x4c858bd0    07/09/2010 04:48:16                
avgtdix.sys        0x8d8b2000    0x8d8f9380    0x00047380    0x4c858c64    07/09/2010 04:50:44

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffc2, 1, 95f37ea5, 0}

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffc2, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 95f37ea5, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 829b7848
Unable to read MiSystemVaType memory at 82996e40
 ffffffc2 

FAULTING_IP: 
AVGIDSDriver+eea5
95f37ea5 c05ec20c        rcr     byte ptr [esi-3Eh],0Ch

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  msiexec.exe

CURRENT_IRQL:  0

TRAP_FRAME:  821f8b78 -- (.trap 0xffffffff821f8b78)
ErrCode = 00000002
eax=00000000 ebx=a92d0d30 ecx=00000008 edx=00000000 esi=00000000 edi=00000008
eip=95f37ea5 esp=821f8bec ebp=821f8c64 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
AVGIDSDriver+0xeea5:
95f37ea5 c05ec20c        rcr     byte ptr [esi-3Eh],0Ch     ds:0023:ffffffc2=??
Resetting default scope

MISALIGNED_IP: 
AVGIDSDriver+eea5
95f37ea5 c05ec20c        rcr     byte ptr [esi-3Eh],0Ch

LAST_CONTROL_TRANSFER:  from 8288f3e8 to 828dc3db

STACK_TEXT:  
821f8b60 8288f3e8 00000001 ffffffc2 00000000 nt!MmAccessFault+0x106
821f8b60 95f37ea5 00000001 ffffffc2 00000000 nt!KiTrap0E+0xdc
WARNING: Stack unwind information not available. Following frames may be wrong.
821f8c64 82a99748 00000008 821f8c94 00000001 AVGIDSDriver+0xeea5
821f8d14 8288c1fa 00000244 0081e7b8 00000002 nt!NtQueryValueKey+0x29c
821f8d14 77c470b4 00000244 0081e7b8 00000002 nt!KiFastCallEntry+0x12a
0081e788 00000000 00000000 00000000 00000000 0x77c470b4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
AVGIDSDriver+eea5
95f37ea5 c05ec20c        rcr     byte ptr [esi-3Eh],0Ch

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  AVGIDSDriver+eea5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  IP_MISALIGNED_AVGIDSDriver.Sys

BUCKET_ID:  IP_MISALIGNED_AVGIDSDriver.Sys

Followup: MachineOwner

yowanvista said:

Please remove AVG and use MSE
AVG is causing these BSODs
Virus, Spyware & Malware Protection | Microsoft Security Essentials

Code:

avgfwd6x.sys        0x8d87e000    0x8d88f000    0x00011000    0x4c3a71d5    12/07/2010 05:37:25                
AVGIDSEH.Sys        0x88600000    0x88609000    0x00009000    0x4c8ea9cb    14/09/2010 02:46:35                
avgldx86.sys        0x8dd23000    0x8dd5e400    0x0003b400    0x4c858bc7    07/09/2010 04:48:07                
avgmfx86.sys        0x82e00000    0x82e0c000    0x0000c000    0x4c858bc1    07/09/2010 04:48:01                
avgrkx86.sys        0x887f6000    0x887fab80    0x00004b80    0x4c858bd0    07/09/2010 04:48:16                
avgtdix.sys        0x8d8b2000    0x8d8f9380    0x00047380    0x4c858c64    07/09/2010 04:50:44

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 50, {ffffffc2, 1, 95f37ea5, 0}
 
Unable to load image \SystemRoot\system32\DRIVERS\AVGIDSDriver.Sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AVGIDSDriver.Sys
*** ERROR: Module load completed but symbols could not be loaded for AVGIDSDriver.Sys
 
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffc2, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 95f37ea5, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000000, (reserved)
 
Debugging Details:
------------------
 
 
Could not read faulting driver name
 
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 829b7848
Unable to read MiSystemVaType memory at 82996e40
 ffffffc2 
 
FAULTING_IP: 
AVGIDSDriver+eea5
95f37ea5 c05ec20c        rcr     byte ptr [esi-3Eh],0Ch
 
MM_INTERNAL_CODE:  0
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
BUGCHECK_STR:  0x50
 
PROCESS_NAME:  msiexec.exe
 
CURRENT_IRQL:  0
 
TRAP_FRAME:  821f8b78 -- (.trap 0xffffffff821f8b78)
ErrCode = 00000002
eax=00000000 ebx=a92d0d30 ecx=00000008 edx=00000000 esi=00000000 edi=00000008
eip=95f37ea5 esp=821f8bec ebp=821f8c64 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
AVGIDSDriver+0xeea5:
95f37ea5 c05ec20c        rcr     byte ptr [esi-3Eh],0Ch     ds:0023:ffffffc2=??
Resetting default scope
 
MISALIGNED_IP: 
AVGIDSDriver+eea5
95f37ea5 c05ec20c        rcr     byte ptr [esi-3Eh],0Ch
 
LAST_CONTROL_TRANSFER:  from 8288f3e8 to 828dc3db
 
STACK_TEXT:  
821f8b60 8288f3e8 00000001 ffffffc2 00000000 nt!MmAccessFault+0x106
821f8b60 95f37ea5 00000001 ffffffc2 00000000 nt!KiTrap0E+0xdc
WARNING: Stack unwind information not available. Following frames may be wrong.
821f8c64 82a99748 00000008 821f8c94 00000001 AVGIDSDriver+0xeea5
821f8d14 8288c1fa 00000244 0081e7b8 00000002 nt!NtQueryValueKey+0x29c
821f8d14 77c470b4 00000244 0081e7b8 00000002 nt!KiFastCallEntry+0x12a
0081e788 00000000 00000000 00000000 00000000 0x77c470b4
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
AVGIDSDriver+eea5
95f37ea5 c05ec20c        rcr     byte ptr [esi-3Eh],0Ch
 
SYMBOL_STACK_INDEX:  2
 
SYMBOL_NAME:  AVGIDSDriver+eea5
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: hardware
 
IMAGE_NAME:  hardware
 
DEBUG_FLR_IMAGE_TIMESTAMP:  0
 
FAILURE_BUCKET_ID:  IP_MISALIGNED_AVGIDSDriver.Sys
 
BUCKET_ID:  IP_MISALIGNED_AVGIDSDriver.Sys
 
Followup: MachineOwner

Thanks for your interest. I uninstalled AVG as you suggested and installed MSE, then I ran a full scan and half way through it crashed again. I have attached the minidump file showing the latest crash and also another which occurred after my first post and before I had uninstalled AVG.

Any further help would be appreciated please.

and here's the latest minidump file after several more crashes. I can't even get through a full MSE scan without crashing.

Please post a new complete attachment :)

OK here are the new files you requested. Looking forward to your advice.

mildew said:

OK here are the new files you requested. Looking forward to your advice.

New dumps point to the Intel Display Driver, igdkmd32.sys
A fault in your RAM might trigger the crash, test your RAM
RAM - Test with Memtest86+
Update the Intel driver
Intel® Driver Update Utility

Code:

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: cb141845, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8e81cb85, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82b79848
Unable to read MiSystemVaType memory at 82b58e40
 cb141845 

CURRENT_IRQL:  2

FAULTING_IP: 
igdkmd32+1cb85
8e81cb85 108b45088945    adc     byte ptr [ebx+45890845h],cl

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  8a4b4a20 -- (.trap 0xffffffff8a4b4a20)
ErrCode = 00000002
eax=858cd502 ebx=858b1000 ecx=85880008 edx=84a55798 esi=8a4b4af0 edi=82e276ee
eip=8e81cb85 esp=8a4b4a94 ebp=8a4b4a94 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
igdkmd32+0x1cb85:
8e81cb85 108b45088945    adc     byte ptr [ebx+45890845h],cl ds:0023:cb141845=??
Resetting default scope

MISALIGNED_IP: 
igdkmd32+1cb85
8e81cb85 108b45088945    adc     byte ptr [ebx+45890845h],cl

LAST_CONTROL_TRANSFER:  from 8e81cb85 to 82a515db

STACK_TEXT:  
8a4b4a20 8e81cb85 badb0d00 84a55798 0020358b nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
8a4b4a94 8f1220db 85969000 8a4b4af0 858b48d8 igdkmd32+0x1cb85
8a4b4abc 8f121f9b 8a4b4af0 8a4b4ad8 8dd420d5 dxgkrnl!DXGADAPTER::DdiSubmitCommand+0x49
8a4b4ac8 8dd420d5 858b1000 8a4b4af0 8a4b4b64 dxgkrnl!DXGADAPTER_DdiSubmitCommand+0x10
8a4b4ad8 8dd4b4ea 8a4b4af0 858b4b80 858b4000 dxgmms1!DXGADAPTER::DdiSubmitCommand+0x11
8a4b4b64 8dd72529 00000000 87048820 858b4b80 dxgmms1!VidSchiSendToExecutionQueue+0x7d6
8a4b4bdc 8dd72e99 85880008 00000001 87048820 dxgmms1!VidSchiSendToExecutionQueueWithWait+0x115
8a4b4d18 8dd73141 00048820 85005008 8a4b4d3c dxgmms1!VidSchiSubmitRenderCommand+0x809
8a4b4d28 8dd733de 87048820 82a47509 85880008 dxgmms1!VidSchiSubmitQueueCommand+0x61
8a4b4d3c 8dd73485 85880008 00000000 858cd510 dxgmms1!VidSchiRun_PriorityTable+0x24
8a4b4d50 82c18fda 85880008 aa554466 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8a4b4d90 82ac11d9 8dd73406 85880008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
igdkmd32+1cb85
8e81cb85 108b45088945    adc     byte ptr [ebx+45890845h],cl

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  igdkmd32+1cb85

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  IP_MISALIGNED_igdkmd32.sys

BUCKET_ID:  IP_MISALIGNED_igdkmd32.sys

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

yowanvista said:

mildew said:

OK here are the new files you requested. Looking forward to your advice.

New dumps point to the Intel Display Driver, igdkmd32.sys
A fault in your RAM might trigger the crash, test your RAM
www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Update the Intel driver
Intel® Driver Update Utility

Code:

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: cb141845, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8e81cb85, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82b79848
Unable to read MiSystemVaType memory at 82b58e40
 cb141845 

CURRENT_IRQL:  2

FAULTING_IP: 
igdkmd32+1cb85
8e81cb85 108b45088945    adc     byte ptr [ebx+45890845h],cl

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  8a4b4a20 -- (.trap 0xffffffff8a4b4a20)
ErrCode = 00000002
eax=858cd502 ebx=858b1000 ecx=85880008 edx=84a55798 esi=8a4b4af0 edi=82e276ee
eip=8e81cb85 esp=8a4b4a94 ebp=8a4b4a94 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
igdkmd32+0x1cb85:
8e81cb85 108b45088945    adc     byte ptr [ebx+45890845h],cl ds:0023:cb141845=??
Resetting default scope

MISALIGNED_IP: 
igdkmd32+1cb85
8e81cb85 108b45088945    adc     byte ptr [ebx+45890845h],cl

LAST_CONTROL_TRANSFER:  from 8e81cb85 to 82a515db

STACK_TEXT:  
8a4b4a20 8e81cb85 badb0d00 84a55798 0020358b nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
8a4b4a94 8f1220db 85969000 8a4b4af0 858b48d8 igdkmd32+0x1cb85
8a4b4abc 8f121f9b 8a4b4af0 8a4b4ad8 8dd420d5 dxgkrnl!DXGADAPTER::DdiSubmitCommand+0x49
8a4b4ac8 8dd420d5 858b1000 8a4b4af0 8a4b4b64 dxgkrnl!DXGADAPTER_DdiSubmitCommand+0x10
8a4b4ad8 8dd4b4ea 8a4b4af0 858b4b80 858b4000 dxgmms1!DXGADAPTER::DdiSubmitCommand+0x11
8a4b4b64 8dd72529 00000000 87048820 858b4b80 dxgmms1!VidSchiSendToExecutionQueue+0x7d6
8a4b4bdc 8dd72e99 85880008 00000001 87048820 dxgmms1!VidSchiSendToExecutionQueueWithWait+0x115
8a4b4d18 8dd73141 00048820 85005008 8a4b4d3c dxgmms1!VidSchiSubmitRenderCommand+0x809
8a4b4d28 8dd733de 87048820 82a47509 85880008 dxgmms1!VidSchiSubmitQueueCommand+0x61
8a4b4d3c 8dd73485 85880008 00000000 858cd510 dxgmms1!VidSchiRun_PriorityTable+0x24
8a4b4d50 82c18fda 85880008 aa554466 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8a4b4d90 82ac11d9 8dd73406 85880008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
igdkmd32+1cb85
8e81cb85 108b45088945    adc     byte ptr [ebx+45890845h],cl

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  igdkmd32+1cb85

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  IP_MISALIGNED_igdkmd32.sys

BUCKET_ID:  IP_MISALIGNED_igdkmd32.sys

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

I ran Memtest86 for about 4 hours earlier today without any errors showing up.
Although I had already updated all the drivers using Driver Genius I ran the Intel page you suggested and you will see in the attached word a transcript of the findings, showing no issues.
Other files are included incorporating latest crash about 40 minutes ago.
Starting to think it might be faulty RAM.

Cheers

Driver Genius and other Drivers updaters should never be used, they tend to cause system issues
Was the same BSOD occurring while you were using XP?

Yes it was. Am going to remove one of the 2 1gb sticks of RAM and see what happens.