BSOD randomly, sometimes without actual blue screen

[krustster]

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.

 

[koolkat77]

Welcome

Looks like your onboard gfx driver needs to be updated:

*******************************************************************************
*                                                                             *
*                        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

 

[krustster]

Thanks for replying! I'll go do that now. I will check back in later to let you know how it went.

 

[koolkat77]

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

 

[krustster]

Well, I updated the driver successfully, but I got the blue screen again today. I was able to actually read it this time and it claimed to be a "KERNEL_INPAGE_ERROR"... I've attached the new crash dumps if you'd be so kind

 

[koolkat77]

The dump is of 101612

 

[krustster]

Well that's not very helpful then, is it? I don't know what went wrong, the folder was created today (or yesterday, technically) but the file it grabbed is indeed from the 16th. There must have been some kind of stupid problem preventing the system from creating a new one, or something. I have a vague recollection that the blue screen said something about the dump not being completed, at the time I didn't think anything of it but apparently it was in reference to that file? I guess I'll wait and see if it happens again, and try to get more info when it does. Thanks for your patience.

 

[koolkat77]

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

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
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

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

• http://www.sevenforums.com/tutorials/433-disk-check.html

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.

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
• 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

 

[krustster]

Oh my. Well my computer is an HP laptop probably about 2 years old, I've had it for about 6 months but it's a refurb. I put in a new hard drive and new RAM (maybe the culprit?) in the last two months Good thing I came here rather than trying to figure it out on my own. I'll start running the tests immediately! Thanks again for helping.

 

[koolkat77]

No problem. Keep us posted of the results

 

[krustster]

Well, CHKDSK and TDSSkiller both came back clean, Crystal Disk shows no apparent problems(it gives a rating of "Good") but I tried to run the RAM test on two different occasions and left it while I went to do other things, and my laptop shut down because it was overheating. I had consulted with a friend before I upgraded the RAM and he revealed that 8GB was the max that my system could use, so I went ahead and got 8GB for a bargain price and stuck it in there. I have to wonder if maybe that's the major issue here, possibly overextending my comp's abilities, because the times when it had crashed before, I was running a lot of streaming videos and applications and whatnot. I never got the overheating note until I did the RAM test though.

Additionally, since the last crash I reported, it hasn't happened again. I wonder if it's possible that the graphics driver update hadn't been finalized since I didn't restart my computer after doing it--the updater never actually said that I should restart, but I wonder if perhaps I was simply expected to do so anyway. Obviously I'm just throwing stuff out there, probably wrong, but oh well. I'll check out the other tests and I may try testing a single RAM stick instead of both at once and see what happens.

View attachment 238248

 

[koolkat77]

Good idea about testing single sticks, go ahead. Does the laptop have a cooler? Is any part of the hardware overclocked? Did you check if the ram clock/speeds are all the same? For monitoring heat, use Speccy or HWinfo.

• Speccy - System Information - Free Download
• CPUID - System & hardware benchmark, monitoring, reporting