Random BSOD New build 0x800... event id 1001

It was the right file, and couldn't find any problems with it.

Code:

BugCheck 7F, {8, 80050031, 406f8, fffff88001217529}

Probably caused by : memory_corruption

Code:

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

A trap which was excepted happened in the Kernel, a trap is a type of exception, a interrupt occurs to enable the operating system to perform some functions before returning to the previous process, a trap can be caused by an invalid memory address which seems to be happening in this case.

Code:

CHKIMG_EXTENSION: !chkimg -lo 50 -d !Ntfs
    fffff8800121751c - Ntfs!NtfsCleanupIrpContext+287
	[ 83:a3 ]
1 error : !Ntfs (fffff8800121751c)

• RAM - Test with Memtest86+

Run Memtest86+ for least 10-15 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Arc said:

No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

There has been some cases, whereby errors have been found at 20 passes.

x BlueRobot said:

It was the right file, and couldn't find any problems with it.

Code:

BugCheck 7F, {8, 80050031, 406f8, fffff88001217529}

Probably caused by : memory_corruption

Code:

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

A trap which was excepted happened in the Kernel, a trap is a type of exception, a interrupt occurs to enable the operating system to perform some functions before returning to the previous process, a trap can be caused by an invalid memory address which seems to be happening in this case.

Code:

CHKIMG_EXTENSION: !chkimg -lo 50 -d !Ntfs
    fffff8800121751c - Ntfs!NtfsCleanupIrpContext+287
	[ 83:a3 ]
1 error : !Ntfs (fffff8800121751c)

• RAM - Test with Memtest86+

Run Memtest86+ for least 10-15 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Arc said:

No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

There has been some cases, whereby errors have been found at 20 passes.

Okay so I need to run MemTest again. I'm assuming that I run the test with both sticks installed and if I get an error then I start testing individual sticks. Last time I had both RAM sticks in. I guess this time I am going to let it run for about 24 hours, or until 20 passes completes, to be sure. Ill get back to you after I have done this.

Okay thanks, there does seem to quite a few clues pointing to bad RAM, or other memory issues.

x BlueRobot said:

Okay thanks, there does seem to quite a few clues pointing to bad RAM, or other memory issues.

About 9 passes in. But I was thinking, since it is a memory problem and I was getting weird video errors, could it be a problem with the gddr5 memory on the graphics card?

VistaKing said:

Take a look at the link below . It has a video memory test like memtest

HOME PAGE OF MISHA CHERKES

Ok thanks. Ill check that out once Memtest finishes.. going to take more than 24 hrs, 14 passes in.

Okay, and bad video memory can be a possibility with the memory_corruption, the RAM is either corrupted or the !ntfs image within the RAM is corrupted itself.

Okay I ran memtest for 46 hours and it ran 24 passes with no errors. I started the Video memory test and it has ran 6 passes with no errors so far. I didn't configure any of the settings for the test because there wasn't any instructions that I saw but I figured it was like memtest just let it run itself.

I was reading some stuff online and I am pretty sure I messed up installing drivers (which might be what caused this). I thought I was supposed to install ALL of the motherboard drivers from Gigabytes' site and I downloaded every file listed for my mobo and installed them, instead of just going into device manager and getting the ones I needed... Is this a big problem and can I fix it?

Yes, it's possible you can fix this problem, personally I would backup all your personal files using Backup User and System Files, and then perform a Clean Reinstall - Factory OEM Windows 7.

By doing this, we can make sure you have the exact drivers, and eliminate any possible software cause for the BSODs.

Remember to download your Ethernet driver before clean install.