Solved Random 0x0000000A BSODs

[eddman]

I've been running my PC with Windows 7 for about a month, and 2 months before that with Windows XP. Everything was fine until about ten days ago when I started getting random BSODs.

They usually happen once every 1-2 days and can happen in any situation, except for when PC is idle, e.g. when I'm not behind it. They can happen anytime; right after boot, or after 8 hours of usage.
I checked system logs but they don't point at anything specific, only a 0x0000000A stop error.

Things I've done so far:

1. Checked HDDs with SeaTools utility boot disc. No disc errors.
2. Ran memtest86 for 6 passes and 52%. No errors. See post #4.
3. Ran OCCT on CPU for 12 minutes, on GPU for 20 minutes. No errors, but I think I should run them for a longer period.
4. Refitted SATA cables and also wiggled them while PC was running. No crashing, but I still can't rule them out. Can a bad SATA cable cause such random BSODs? Shouldn't the errors be happening all the time if they are indeed faulty?
5. Ran TDSSKiller. All clean, except for unsigned creative drivers, but they couldn't really be the problem, because all was fine for about a month.
6. Scanned for malware with NOD32 and malwarebytes' anti-malware. No threats detected.
7. Ran sfc /verifyonly. This too didn't find any problems.

I know that it could also be corrupted windows files or drivers, but I really don't want to re-install windows, not until I've made sure it's not a hardware problem, and I don't know how to test drivers.

I really don't know what else to do.

EDIT: I just took a look at event viewer and there are tons of the same error over and over, and they keep happening:

"Session "Microsoft-Windows-Setup" stopped due to the following error: 0xC000000D"

They haven't always led to a BSOD, but still might be related somehow.

 

[zigzag3143]

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP


We could also use some system information, which you can get easily by running msinfo32.
To do that go to start>run>type msinfo32>enter

When it is finished running go to file>save>name it and upload to us here.


You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[eddman]

If you are overclocking STOP

I've never overclocked my computer.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Small dump wasn't enabled. I enabled it. Will post the dump file next time I encounter a crash.

We could also use some system information, which you can get easily by running msinfo32.

 

[eddman]

I haven't got a bsod yet, but I ran memtest again, this time for 11 passes, and it found 1 error in pass 10.

Could just one faulty address space cause such Intermittent BSODs?

I've got 2 memory modules. Guess I should now run the test on each one seperately. It might also be a slot problem.

EDIT: Funny, I found some minidumps, but small memory dump was disabled, so I don't know how they got there. Anyway, here they are, named "minidumps1".

EDIT 2: OK, just got a bsod a few minutes ago. Here is its dump, named "minidump2".

 

[zigzag3143]

Most recent DMP/BSOD still related to memory corruption, so I guess testing the slots is a good idea.

 

[eddman]

Update:

My motherboard has 4 memory slots. I had two memory modules in slots 1 and 3, running in dual-channel mode.

I ran memtest a few times on them and got errors. Then I tried each module individually in their own slots; no errors, which means slots are fine.
Then I tried both modules together, this time one in slot 2, the other one in slot 3. Got errors.

Now I have them set in slots 2 and 4, which is channel two. Ran memtest, no errors. About 5-6 days have past and haven't got a BSOD so far, so I suppose I can mark this thread as solved, sort of.

I guess channel-one has gone bad, or maybe the RAM modules are wearing out and can't work together properly in channel one anymore. I don't know exactly.

I'll try to hold on to my current hardware until I can get a new mainboard-CPU-RAM package. No point in wasting more money on this old socket 775 board.

Thank you zigzag3143. You helped me learn new things.