BSOD randomly, sometimes without actual blue screen

Hi, I have a pretty standard problem here, except with a bit of a twist. My laptop crashes fairly regularly--roughly every other day--and a couple of times has showed the BSOD itself. Other times it simply stops working and has to be turned off manually, either freezing with the display still on or turning off the display on its own and not restarting. Earlier today it crashed again, did not show the BSOD, but still came up with the "Windows has recovered from an unexpected error" message when I rebooted. The couple of times I got the blue screen, it went away too fast for me to look at it. I changed the settings so that it wouldn't restart automatically, and while it has crashed a few times since then, I didn't actually get the BSOD but still received the message on startup.

I installed a new internal hard drive about a month or so ago and I checked for updated drivers but Windows claimed they were up to date.

I'm attaching the dump files, thanks in advance for any help.

Welcome

Looks like your onboard gfx driver needs to be updated:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800317f010, fffff88004ccba30, ffffffffc0000001, 3}

*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+1ca30 )

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

1: kd> lmvm igdkmd64
start             end                 module name
fffff880`04caf000 fffff880`056cdb60   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Thu Aug 26 01:35:58 2010 (4C75709E)
    CheckSum:         00A23ACB
    ImageSize:        00A1EB60
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Get it from this link:

• Intel Download Center

Keep us posted, good luck

No problem. Take your time, we'll be here.

The dump is of 101612

What's the age of this computer? All its hardware? Is it under warranty?

Code:

STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR  
Usual causes:  Memory, Paging file corruption, File system, Hard drive, 
Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, 
Missing Service Pack

I'm not sure if this is the bug check you're talking about, but seeing the usual causes take some tests instead of waiting.

Run this tool and delete anything it finds:

• Anti-rootkit utility TDSSKiller

Post a screen shot of your hard disk with crystal disk info

• CrystalDiskInfo - Software - Crystal Dew World
• Screenshots and Files - Upload and Post in Seven Forums

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• Disk Check

Hard drive test both short and long with:

• SeaTools for Windows

Also the DOS version of:

• SeaTools for DOS

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+
• Guide to using Memtest86+ - Geeks to Go Forums

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Let us know the results

No problem. Keep us posted of the results