Multiple BSOD erros (0x0000003b, 0x0000007f, 0x0000001a, 0x0000001e) &

As said above in the title, I have been getting multiple BSODs on this new build. The build is using mostly old parts except for the motherboard, CPU, PSU, and card reader. The HDD, ODD, and RAM are all reused from previous computers.

It's been almost every day that I would get a BSOD on this machine. The major driver files seem to be ntoskrnl.exe and Ntfs.sys. A few other ones have shown up as well, such as dxgmms1.sys and win32k.sys.

The BSODs seem to occur at random times, however most recently they have occurred when watching .avi videos in full screen.

I have attached below all the minidumps that I have along with the last few events in event viewer. There are tons of errors in event viewer.

The specs of the computer are as follows:
AMD Athlon II X2 250
WD 80GB HDD
Motherboard is part of the Shuttle SA76G2 V2
2x 2GB OCZ2P8002G PC2-6400
Windows 7 SP1 X64
Onboard HD Radeon 3000

Please let me know if you need anymore information.

Anyone?

Can someone please help?

I tried deleting the newest video drivers and installed the ones that are on the Shuttle website (basically older AMD drivers)

I also tried using driver verifier, and it took about 2 or more days until it finally crashed with another BSOD, however, this time it did not create a dump file for some reason. I'm not sure why it didn't create one this time while it did all the other times.

koolkat77 said:

Welcome and sorry for the late response

If you are overclocking any hardware, please stop.

None of your dumps show a probable cause but one of them shows memory corruption. Run memtest86+ on each stick for 8 passes preferably overnight:

RAM - Test with Memtest86+

Please upload your msinfo32.nfo file. To get this:

• Click on the Start
• Type msinfo32 into the Search programs and files box
• When it opens, go to File, Save
• Save as msinfo32.nfo and save in a place you will remember
• Let it finish the process of gathering and saving the system info
• Right click the .nfo file, click send to compressed (zipped) folder
• Upload the .zip file here.

Also let us know how your computer performs in Safe mode.

Post back results

No hardware is overclocked. I thought it might be the RAM so I took one module out and left the other in there. I will test each module individually in each slot to test out this possibility. So far I did one stick in the top slot and it BSOD, so now I'm trying the same stick in the bottom slot. I will report back if it BSOD again.

Also, I should mention that I did not get a new dump file in this recent BSOD. I checked the setting and made sure that the option to create the dump files is checked. Is this normal? Does this mean something else?

As for the msinfo32 file, it is attached, but please bear in mind that I am running off of only one stick atm.

As for the safe mode thing, it's hard to test that because the BSOD doesn't always happen in a short amount of time. Sometimes it takes a day or two for it to occur. Using safe mode for a day or two is hard as most of the computer functionality is disabled in safe mode.

koolkat77 said:

We have to try allot of different things to solve it.
Can you tell what antivirus you use? Cause I can't see any on the msinfo file.
Will be waiting for the memory test results.

Some information on verifier for you:

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

• Driver Verifier - Enable and Disable

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Capt.Jack Sparrow said:

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

I have MSE installed. I have already tried Driver Verifier. I got a BSOD about 2 days later (more than 36 hours), but no dump files were made. I double checked the settings to make sure the option to create dump files is checked, and it is.

koolkat77 said:

Okay, see the causes below for the bug checks you are getting

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION:-
Usual causes: System service, Device driver, graphics driver, memory

STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP:-
Usual causes: Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack

STOP 0x0000001A: MEMORY_MANAGEMENT:-
Usual causes: Device driver, memory, kernel

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED:-
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.

How many sticks of ram do you have exactly? Your msinfo shows 2 GB only.

Do a video card stress test with Video Card - Stress Test with Furmark and monitor your temps with Speccy - System Information - Free Download during the test.

I guess you didn't do the memtest yet, so before you start do the video card stress and let me know the feedback.

I have 2x 2GB of RAM total. I mentioned that I took one of the modules out when I did the msinfo32 report. Both modules are the EXACT same model number.

I am trying to run this with only 1 stick at a time to rule out the possibility of one of the sticks being bad and the other being good. The reason is I had these same sticks running in another computer for a few weeks, but I can't recall having any problems in that other computer. I am not 100%, though.

As for the video card test, it is an onboard HD Radeon 3000. Is that ok?