Many BSOD and restarts for 2 months

I have been getting random restarts and BSOD for 2 months, but in the last 2 weeks it has been fine. It just started again today and this time i decided to post it up. I have run memory diognostics tools and so problems there.

It restarts very randomly so i cant even be specific, however i have deleted previous(very old) dump files but i do have some of the recent ones.

Laptop:
toshiba satellite A500-17X

• Processor - Intel Core 2 Duo P7450 - 2.13 GHz
• 2nd level cache : 3 MB

• RAM - 4 GB (DDR3 RAM)
• Hard Drive - 500 GB
• Operating System - Microsoft Windows 7 Home Premium 64-bit Edition
• Optical Drive - DVD±RW (±R DL) / DVD-RAM
• Graphics - NVIDIA GeForce GT 230M

Additional info: I have bought it 1 year ago

Thanks for any help

Hi,
Your dumps bugcheck:

• 0x50 = This indicates that invalid system memory has been referenced.
• 0x3b = This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
• 0xa = This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
• 0x7f_8 = indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.

Start with remove Avast and replace it with MSE.
Reinstall your VLC player since there are lot errors reported on WER. (update to newer version if any).

Update these drivers:
adfs.SYS --> adobe software
nvhda64v.sys --> nVidia HDMI Audio Device (nForce chipset driver)
Rt64win7.sys --> Realtek NIC

If the problem persist , test your RAM with memtest86 at least 7 passes.
RAM - Test with Memtest86+

Log

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80004773b1f, fffff8800886cc70, 0}

Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )

Followup: MachineOwner
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffff800049b5715, fffff8800a156f90, 0}

Probably caused by : hardware ( nt!ObpQueryNameString+301 )

Followup: MachineOwner
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800049b5863, fffff8800abbd060, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObpAllocateObject+1d3 )

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

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

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 406f8, fffff800046bb6d0}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000406f8
Arg4: fffff800046bb6d0

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  sidebar.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800937bfa0 -- (.trap 0xfffff8800937bfa0)
Unable to read trap frame at fffff880`0937bfa0

LAST_CONTROL_TRANSFER:  from fffff800046bcca9 to fffff800046bd740

STACK_TEXT:  
fffff800`05b51d28 fffff800`046bcca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx
fffff800`05b51d30 fffff800`046bb172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`05b51e70 fffff800`046bb6d0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0937bfa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x10


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`046bb172 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

Followup: MachineOwner

thanks, Ill try it out and tell you if the problem still happens

ok i have updated the drivers except the adobe one as i cant find out how to do it. I find their website
I have also reinstalled vlc and I am about to switch to MSE from avast and hopefully everything is fine.
i will test this tommorow, and will just playing a game to see if no crashes happens

blade001 said:

ok i have updated the drivers except the adobe one as i cant find out how to do it. I find their website
I have also reinstalled vlc and I am about to switch to MSE from avast and hopefully everything is fine.
i will test this tommorow, and will just playing a game to see if no crashes happens

Thanks for report back.
About the adobe, it's better to use latest Adobe software (ex: Photoshop CS5)

Today i installed MSE but when it was updating i got another bsod and i got IRQL_NOT_LESS_OR_EQUAL and it mentioned ndis.sys . However i still installed MSE again and so for it was ok.
I still need to do the memory test as you said above.
Oh and about the adobe driver, i have photoshop cs4 and aftereffects cs5. I dont want to update photoshop to cs5 because it looks nasty compared to cs4.

extra:I got a bsod yesterday but it was before i started updating drivers and trying to fix the problem.

Ill keep you updated

i sent the laptop to toshiba 3days before warranty ran out, but before i did i tried reformating(to factory settings). after i did it kept restarting without even starting up fully. Then i did send it and its fine now.
thanks for trying to help

Sorry I didn't help much, but glad you have solved the problems