blue screening on a new build

So i built my first computer last week and have been getting blue screens. Two have happened while gaming and one happened while streaming a movie. Thought it was the video drivers so I installed an older nvidia driver but got the third blue screen last night. I ran memtest thinking it was bad memory but got no errors. This is the first minidump log. Any suggestions?

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a

BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 2

FAULTING_IP:
nt+74168
8054b168 893b mov dword ptr [ebx],edi

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 8054b75f to 8054b168

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b850bcdc 8054b75f 00000001 00000000 897c1870 nt+0x74168
b850bd1c 805c105f 897c1870 e5726854 8a538e70 nt+0x7475f
b850bd3c 805bb46e 00000000 897c1870 897c1888 nt+0xea05f
b850bd54 805266ca 897c1888 00000000 806e6a3c nt+0xe446e
b850bdac 805cff64 00000000 00000000 00000000 nt+0x4f6ca
b850bddc 805460de 8053867e 00000002 00000000 nt+0xf8f64
00000000 00000000 00000000 00000000 00000000 nt+0x6f0de


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+74168
8054b168 893b mov dword ptr [ebx],edi

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+74168

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

Let's try this.

Download/install BlueScreenView,http://www.nirsoft.net/utils/blue_screen_view.html.

Double-click BlueScreenView.exe file.

When scanning is done, Edit/Select All...then File/Save Selected Items.

Save the report as BSOD.txt.

Open BSOD.txt in Notepad, copy all content and paste it into your next reply.

Louis

Here is all three.


==================================================
Dump File : Mini122110-01.dmp
Crash Time : 12/21/2010 1:23:23 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x52276316
Parameter 3 : 0xb0380be0
Parameter 4 : 0x00000000
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini122110-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================


==================================================
Dump File : Mini121710-02.dmp
Crash Time : 12/17/2010 4:01:08 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x00000002
Parameter 2 : 0x00000002
Parameter 3 : 0x00000008
Parameter 4 : 0x00000002
Caused By Driver : NDIS.sys
Caused By Address : NDIS.sys+493
File Description : NDIS 5.1 wrapper driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-0852)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini121710-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================


==================================================
Dump File : Mini121710-01.dmp
Crash Time : 12/17/2010 2:32:45 AM
Bug Check String : DRIVER_CORRUPTED_EXPOOL
Bug Check Code : 0x100000c5
Parameter 1 : 0x09799610
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x8054b168
Caused By Driver : portcls.sys
Caused By Address : portcls.sys+500
File Description : Port Class (Class Driver for Port/Miniport Devices)
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini121710-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
==================================================

I did a search and found out the third one may be related to the audio drivers but the other two I'm not too sure about.

I'd run either a repair install or sfc /scannow...ndis.sys is a Windows file. From what I've seen...errors reflecting ndis.sys as the scene of the crime...can originate with various other system drivers, including firewall and networking.

As for the apparent driver issues...I'd run the system without installing the audio drivers...and see if the errors continue. If not, then I would reinstall the audio drivers.

Louis

NDIS is networking - you can try reinstalling your network drivers.

You said this was a fresh build, and it seems to be happening under stress. I would think possible thermal or power issues are at work here. What are the system's specs?