Sign in with
Sign up | Sign in
Your question
Solved

How to fix blue screen of death

Last response: in Windows 7
Share
February 17, 2014 11:53:40 AM


So I got this blue screen of death like a week ago. I can use my laptop for about 15 min to 2 hrs then it comes up and restarts. I tried a system restore and stuff and none of it is working.

There is a very slight chance water damage might have something to do with it, but i barely spilled any water on my laptop, think i wiped it up before any got in, and did that a few weeks before the blue screen came up.

I have windows 7 by the way.

If anyone knows what I can do to possibly fix this, I'd be so grateful. I'm a broke college student and don't really want to have to spend a bunch of money to take it somewhere to get fixed.

More about : fix blue screen death

a b D Laptop
a b $ Windows 7
February 17, 2014 12:43:18 PM

use bluescreenview or whocrashed those programs will read the dump files and give you an idea
m
0
l
Related resources
February 17, 2014 3:02:26 PM

I got this from bluescreenview:
Filename Address In Stack From Address To Address Size Time Stamp Time String Product Name File Description File Version Company Full Path
iaStor.sys iaStor.sys+7dbc8 fffff880`01801000 fffff880`01ba5000 0x003a4000 0x4ed5a567 11/29/2011 10:39:19 PM

Trying to figure out what that means. anyone able to lend a hand?
m
0
l

Best solution

a b D Laptop
a b $ Windows 7
February 17, 2014 3:09:13 PM

yes, it is the intel storage dirver getting a access violation because it attempted to read from a bad address
that is why i would first start by updating your intel storage driver. (see my note above)

I know that does not help in why it did the bad read but your fix will be the same. Update the driver and hope that it was the cause and not another driver that corrupted the stroage drivers memory addresses. Intel tends to have very good drivers, and the actual cause of a problem like this is actually another driver that overwrites into another drivers memory spaces. These tend to be hard to find, and you get different bluescreens each time because current versions of windows will load the drivers in memory in a different order on each boot. The driver that corrupts the data tends to be the driver that owns the data next to the corrupted data. The second driver is just a victim that might crash when it goes to use the data. Generally windows will not bugcheck on the initial corruption unless it gets one if its key structures modified then it shuts down with a bluescreen and names the driver.


npalmer51 said:
I got this from bluescreenview:
Filename Address In Stack From Address To Address Size Time Stamp Time String Product Name File Description File Version Company Full Path
iaStor.sys iaStor.sys+7dbc8 fffff880`01801000 fffff880`01ba5000 0x003a4000 0x4ed5a567 11/29/2011 10:39:19 PM

Trying to figure out what that means. anyone able to lend a hand?


Share
!