BSOD & PC freezing issues - required .zip attached

[Arc]

To report the results of driver verifier, just follow Blue Screen of Death (BSOD) Posting Instructions and attach the data with your reply post.

 

[swam]

Hi Arc,

Please find a new BSOD report .zip attached.

cheers

Sam

 

[Arc]

There is no new crash dump.

View attachment 363068
​

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Then try driver verifier again.

 

[swam]

Hi Arc,

Sorry for the delay in getting back to your recent post, I have been away a few days.

It's odd that the bluescreen I had on the 17th of June isn't showing, as it's definitely showing in Bluescreenview. (please see image attached)

Can you think of any reason it wouldn't show when I create the .zip?

I had previously stopped everything loading on startup bar Microsoft Security Essentials.

thanks

Sam

 

[Arc]

The zip catches the minidump. If the dump of 17.06 is a full memory dump by any chance, then it will not be included in the zip.

 

[swam]

Hi Arc,

Is there a known cause of a full memory dump? or is it a case of using the PC until it causes a bluescreen which can be read?

cheers

Sam

 

[Arc]

The size of the recorded crash dump depends on some user settings. You may force your system to record a small minidump.

Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any disc cleanup tool before you upload another zip.

 

[swam]

Hi Arc,

I'll do it now and wait for a BSOD.

cheers

Sam

 

[swam]

Hi Arc,

Had a couple more crashes, but they didn't seem to show a BSOD when they occured. They are listed in bluescreenview but don't show up in the .zip at all (please see screenshot and .zip attached).

Any idea as to what might be happening?

thanks again for your time.

cheers

Sam

 

[Arc]

Hi swam.

Please check the attached image ....

View attachment 363983
​

This is the zip you uploaded, untouched ... opened using compressed folder tools with windows explorer, grouped by date modified. See, no crash dumps after 01/06.

I wonder why the other dumps are not included in the zip. Can you search them in C:\Windows\Minidump, collect them from that location and upload them?

 

[swam]

Hi Arc,

Looks like the pc is recording the dumps. I checked the Minidump folder and they are all in there. I zipped up all the dumps which were missing from the previous .zip. Please find them attached.

cheers

Sam

 

[Arc]

Run memtest86+ once again, with all your memory modules attached.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result, by taking a camera snap of the memtest86+ screen before closing it.

And, there are four RAM sticks. Are they all came in a single KIT? If not, let us know about those in details.

_____________________________________________________

BugCheck C1, {fffff98005ae6c10, 3c8, 3f0, 22}

Probably caused by : memory_corruption ( nt!MmFreeSpecialPool+1bb )

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

 

[swam]

Hi Arc,

I set memtest running and after 10 minutes it reported an error. Please see a photo of the error attached.

cheers

Sam

 

[swam]

Hi Arc,

If I remember correctly, the 4 sticks of ram (2gb each) were bought in two batches. e.g I had 4gb originally, then purchased another 4gb later.

cheers

Sam

 

[Arc]

Hi Arc,

If I remember correctly, the 4 sticks of ram (2gb each) were bought in two batches. e.g I had 4gb originally, then purchased another 4gb later.

cheers

Sam

That is a bad idea. RAM is to purchase only in KITS, two or more RAM modules tested to work together.

Hi Arc,

I set memtest running and after 10 minutes it reported an error. Please see a photo of the error attached.

cheers

Sam

My first suggestion to you was to test the RAM, you reported no issue and then all those headbangings! I really doubt what you have done that time which took that much effort, time and energy to get back to the first place.

Anyway, now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

If it is a bad RAM, you need to change the RAM. Take the other existing (good) RAM to the shop and get one of the exactly same specification. The best is, get a totally new RAM KIT.

If it is a bad slot, it is a motherboard issue. But changing the motherboard needs a preparation for most of us; so dont populate that slot for the time being.

 

[swam]

Hi Arc,

On the very original MEMTEST tests, I ran them for a very long time (longer than recommended) and nothing occured. It just must be the case that some memory or the slot itself has finally decided to properly fail.

When I originally purchased my 4gb (years ago) I had no need for 8gb, but of course over time I needed more for graphics programs etc. So I only purchased them in 4gb batches. 4 + 4 = the 8gb I now have.

I'll run the next memtest tests as you mentioned.

Thanks again for your help.

cheers

Sam

 

[swam]

Hi Arc,

I ran Memtest (9 passes) on each stick of ram in their respective slot, but received no errors. So I thought I would try all 4 sticks again, and Memtest reported an error.

It's odd that with all 4 sticks I get an error, but with each stick in their respective slot it reports no error?

I'm going to go ahead and test stick 1 in slots 2 3 4 etc.

thanks

Sam

 

[swam]

Hi Arc,

Is it worth checking the ram voltage in my BIOS? I read around that Memtest can produce false positives when running a test on all sticks at once, and ram issues can be caused by issues with the voltage.

cheers

Sam

 

[Arc]

If you are worried about the voltages, set the BIOS to default.

How To Clear CMOS (Reset BIOS)
​

But that is not a fact actually.

If the RAM modules are not from a single KIT, then this situation may occur. Modules will work nice individually, but will fail to work together.

There is one more possibility seen in a few cases that some boards that they cannot run properly with all the DIMM slots occupied. That is a corruption from the part of the motherboard. Use only one channel (two slots), leave the other two free. See if it causes any more memory corruption or not.

 

[swam]

Hi Arc,

I'll run the pc with the one channel and see how it goes.

cheers

Sam