BSOD-RAM Issues?

chromium · 01 May 2013

So my HP laptop running Windows 7 32 bit has started to have lots of BSOD's. Usually with an error saying something like "Dumping Physical Memory to Disk". I think its some sort of ram faillure. Whenever my ram usage increases the BSOD occurs. So far ive used a win7 repair disc to run the memory diagnostic, which told me that it had identified a hardware problem. I also used memtest86 which said that there were errors (i ran it until about 3 passes).

Its gotten to a point where it crashes immediately after logging in, and the only way to get in without it crashing is safe boot. From there i managed to copy the zip that the sf diagnostic tool generated (attached).

Basically, i would like to know if anyone can confirm that its ram failure, or if if its something that can be fixed (without replacing ram).

Any help would be appreciated, thanks.

VistaKing · 01 May 2013

Use memtest86+

Test the memory one at a time on every slot

If a memory stick passes on one slot . Test it on another slot

chromium · 02 May 2013

VistaKing said:

Use memtest86+

Test the memory one at a time on every slot

If a memory stick passes on one slot . Test it on another slot

Thanks, I'll try that out when I have some time.
What about the minidump files I attached? Do they say anything interesting?

VistaKing · 02 May 2013

Code:

BugCheck D1, {87f0, 7, 0, 8ee7c756}

Unable to load image \SystemRoot\system32\DRIVERS\igdkmd32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
Probably caused by : igdkmd32.sys ( igdkmd32+41756 )

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


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  igdkmd32+41756

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdkmd32

IMAGE_NAME:  igdkmd32.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a01d354

FAILURE_BUCKET_ID:  0xD1_igdkmd32+41756

BUCKET_ID:  0xD1_igdkmd32+41756

Followup: MachineOwner

---------

igdkmd32.sys - Intel Graphic Driver

Update your Graphic Card Driver

Update :

No code has to be inserted here.

Run SFC /SCANNOW

Click on

type CMD inside Search programs and files. Once CMD comes up under Programs(1) right click CMD choose Run as administrator . On the User Access Control window click on the Yes button . Command Prompt should open up to this path C:\Windows\System32>_

type the command below and press <ENTER>

SFC /SCANNOW

If it finds any corrupted files . Run it a few more times. If it still finds corrupted files upload the CBS.LOG

Path of log : C:\Windows\Logs\CBS\CBS.log

Note

Copy the log to the desktop then upload it from there

Once that is done run CHKDSK

Open up the Command Prompt the same way as you did above. Then type in the command below

chkdsk /F /R

Press <ENTER>

It will tell you that it will run on the next scheduled restart. Press the Y key on your keyboard and press <ENTER> . Manually restart . When it restarts it will run the check disk .

Note

Might take a while

chromium · 02 May 2013

Thanks for the extremely thorough instructions

I cant update the driver since almost everything i do crashes the pc. The only thing i can do is open windows explorer and browse/copy files.

Ive attached the cbs.log, and im going to run the checkdisk in a bit.

VistaKing · 02 May 2013

chromium

I asked if someone could take a look at the log file for you. It will be later cause they're out of United States.

chromium · 02 May 2013

VistaKing said:

chromium

I asked if someone could take a look at the log file for you. It will be later cause they're out of United States.

Alright thanks :)

tom982 · 03 May 2013

Hi chromium,

I've got to be up for work in 6 hours so I've really got to hit the sack now, but I'll post as soon as I finish tomorrow :) Should be around 2pm BST.

Just posting this here so I don't lose it:

Code:

2013-05-02 15:42:53, Info                  CSI    000001c0 [SR] Cannot commit interactively, there are boot critical components being repaired
2013-05-02 15:42:53, Info                  CSI    000001c1 [SR] Repairing 1 components
2013-05-02 15:42:53, Info                  CSI    000001c2 [SR] Beginning Verify and Repair transaction
2013-05-02 15:42:53, Info                  CSI    000001c3 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-bootres_31bf3856ad364e35_6.1.7601.17514_none_41242b0ee032edaf\bootres.dll do not match actual file [l:22{11}]"bootres.dll" :
  Found: {l:32 b:fYXkd05kYqMyfQXS9VPcNhr0kDySaCCSVb0lewbk50U=} Expected: {l:32 b:6e4SSFZ0nrFiOPuv8qitg+vOElHAsJA0yMxfZgGPrgQ=}
2013-05-02 15:42:53, Info                  CSI    000001c4 [SR] Cannot repair member file [l:22{11}]"bootres.dll" of Microsoft-Windows-BootRes, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-05-02 15:42:53, Info                  CSI    000001c5 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-bootres_31bf3856ad364e35_6.1.7601.17514_none_41242b0ee032edaf\bootres.dll do not match actual file [l:22{11}]"bootres.dll" :
  Found: {l:32 b:fYXkd05kYqMyfQXS9VPcNhr0kDySaCCSVb0lewbk50U=} Expected: {l:32 b:6e4SSFZ0nrFiOPuv8qitg+vOElHAsJA0yMxfZgGPrgQ=}
2013-05-02 15:42:53, Info                  CSI    000001c6 [SR] Cannot repair member file [l:22{11}]"bootres.dll" of Microsoft-Windows-BootRes, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2013-05-02 15:42:53, Info                  CSI    000001c7 [SR] This component was referenced by [l:238{119}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~x86~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
2013-05-02 15:42:53, Info                  CSI    000001c8 Hashes for file member \??\C:\Windows\System32\bootres.dll do not match actual file [l:22{11}]"bootres.dll" :
  Found: {l:32 b:fYXkd05kYqMyfQXS9VPcNhr0kDySaCCSVb0lewbk50U=} Expected: {l:32 b:6e4SSFZ0nrFiOPuv8qitg+vOElHAsJA0yMxfZgGPrgQ=}
2013-05-02 15:42:53, Info                  CSI    000001c9 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-bootres_31bf3856ad364e35_6.1.7601.17514_none_41242b0ee032edaf\bootres.dll do not match actual file [l:22{11}]"bootres.dll" :
  Found: {l:32 b:fYXkd05kYqMyfQXS9VPcNhr0kDySaCCSVb0lewbk50U=} Expected: {l:32 b:6e4SSFZ0nrFiOPuv8qitg+vOElHAsJA0yMxfZgGPrgQ=}
2013-05-02 15:42:53, Info                  CSI    000001ca [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"bootres.dll"; source file in store is also corrupted

Tom

chromium · 04 May 2013

I think ive managed to fix it. I removed the 2 sticks of ram, and switched their positions. (put ram stick 1 into slot 2, and ram stick 2 into slot 1). I then ran memtest again, this time i got no errors after 4 passes. (Before i was getting errors within the first minute of testing). I also ran a blend stress test using prime95 and it ran fine for about 3 hours until i manually stopped it. (Before it would cause a BSOD after a couple minutes).

Not sure if theres still a point in checking the log, but its up to you guys.

Thanks.

VistaKing · 04 May 2013

4 passes is nothing . You want at least 8 Passes . If you got an error when you were running a memtest then run a memtest once more with one memory stick inside each memory slot to find what memory stick is the culprit . If you have a dual channel memory kit replace both memory sticks even if one of the sticks is bad .