New
#11
Yes, I did reboot into windows. Upon rebooting though, it actually performed the chkdsk, in a very short time now. I've done as you asked and sfc /scannow is running in an elevated command prompt.
Yes, I did reboot into windows. Upon rebooting though, it actually performed the chkdsk, in a very short time now. I've done as you asked and sfc /scannow is running in an elevated command prompt.
The sfc command has finished running, the only result is a line saying no errors were found.
Well at least that's good news. We need to get your dump files saved though, I'll look further into it.
Last edited by Boozad; 17 Jun 2014 at 10:29. Reason: Typo.
Thanks. I'll leave all of this behind for tonight but I'll get back to it tomorrow.
I did not. Did I miss something from the report BSOD error how-to thread? I'll take a better look.
--
On the other hand I found a minidump file from the 11th of June in my Windows.old directory. I did a system re-installation when I first had my issues so that's why there's a C:\Windows.old; but inside of it, I found a minidump file (MEMORY.DMP). Because I had had the same problems as I have now, I copied it and used DM log collector on it, here's the result in an attached file ->
Yes, I tried all of these methods to configure my windows to create a small memory dump on BSOD.
I have a SF Diagnostic tool ZIP file with a MEMORY.DMP file inside now. It's very large, though (131 megabytes). How should I attach it?
Hi,
I'm "bumping" this, sorry about it. My problems persist.
Main difference since last time: my PC has started generating minidump files on BSOD (still not on the "graphic" crash, when I have to hard reboot, but I have had two BSODs this morning). So here goes in attached files.
Can you help me?
Iphi
Your Intel Graphics driver is being flagged.
Check for updates at the Intel Download Center here.Code:fffff880`0b3afb18 fffff880`068caf38Unable to load image igdkmd64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for igdkmd64.sys *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys igdkmd64+0xc9f38
Code:2: kd> lmvm igdkmd64 start end module name fffff880`06801000 fffff880`06c21000 igdkmd64 T (no symbols) Loaded symbol image file: igdkmd64.sys Image path: igdkmd64.sys Image name: igdkmd64.sys Timestamp: Wed Nov 13 15:26:34 2013 (52839A2A) CheckSum: 00413411 ImageSize: 00420000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4Download and run MemTest86+ to test your RAM. RAM - Test with Memtest86+
NoteRun MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.
Report back with the results.