Semi frequent BSOD problem

[terabytetim]

So I had some BSOD problems back at the beginning of the year, but managed to resolve them. But lately I've been getting crashes again, about 5 in May alone. I'm not sure what's causing them, it doesn't happen when any particular program is running, sometimes it happens when I'm not even on the computer.

I've attached my a dump file from one I just had, and an msinfo32 file.

Any help or guidance is appreciated.

 

[Arc]

Please mark your previous thread as solved as you continued with a new one.

And, click on button below ....

​

It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip with your reply post.

http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html​

 

[terabytetim]

Yeah, I tried using that tool in my last thread as well. When I run it it opens up the blue window saying it's going to collect data, and too press any key to continue. I press enter, and it switches to a black command line, some text flies by so fast that I can't read it, and then it closes. Same problem I had before.

 

[Arc]

OK, try SF Diag Tool then.

 

[terabytetim]

It crashed when running the DXDIAG step, it said it couldn't find "C:/Windows/DxDiag.txt", so I ran all the modules except for DXDIAG manually.

 

[Arc]

If you conceal information, that you cause a loss to you only.

BugCheck A, {1100000c, f, 1, fffff80003b0a7e7}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a272 )

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

BugCheck 51, {1, fffff8a0037ae010, 7d6000, 374}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+9dba )

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

Perform these four tests ......

1. Test your RAM modules for possible errors.

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.

2. Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

3. Stress test the CPU.

Hardware - Stress Test With Prime95
​

It saves the result as a .txt file in the prime95's folder. Upload the file for us.

4. Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Let us know the results. If problems are found, we have to take actions. But if no problem is found, then we have to consider it as a corrupt windows install (chances are there) and a full format and clean install will be needed.

 

[terabytetim]

I'm not trying to conceal information, it legitimately said that. I've attached a screen shot below. I'll run the rest of the tests listed above and post the results this evening.

 

[terabytetim]

Attached the stuff for prime95 and furmark, everything seemed ok. Memtest didn't show any errors, and I'll be scanning for viruses now.

 

[terabytetim]

Neither of the virus tools found any viruses on my computer.

 

[Arc]

Next step is here.... post #6.

But if no problem is found, then we have to consider it as a corrupt windows install (chances are there) and a full format and clean install will be needed.

 

[terabytetim]

So I left the thread as not answered because all the below steps didn't reveal anything, but it also was a long time since my last blue screen.

I just now had my first one in a while. However I just recently installed windows 10. Not only did I do that, but this install is on an entirely new ssd, so there's no chance of old corrupt files having been transferred over.

Any more suggestions as to what could be causing this? I've done all the steps you requested so far. I've attached my most recent msinfo32 and dump file from just now.

As a side note, I'm now running Windows 10 64 bit, instead of the original Windows 7 64 bit.