Bluescreen Error BCCode 1e

I replaced the power supply, but just got another bluescreen error. This one different than the others. It said:

SYSTEM_EXIT_OWNED_MUTEX

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Extra information about the problem
BCCode: 39
BCP1: FFFFF80002D1D7A0
BCP2: FFFFFA8006AD08F0
BCP3: FFFFFA8006AD08F0
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Bucket ID: X64_MEMORY_CORRUPTION_ONE_BIT
Server information: 8ae5fc06-0eaa-499b-86ef-b74bd55e3ca7

Also, before I put in the new power supply, I experienced this bluescreen error:

IRQL_NOT_LESS_OR_EQUAL

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Extra information about the problem
BCCode: a
BCP1: FFFFF6FC42042FB0
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF80002CC9442
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Bucket ID: X64_0xA_nt!MiReplenishBitMap+48
Server information: e7294765-937f-471f-9e68-1a9695bb0535

As well as a few few more 1e stop errors (all before replacing the power supply):

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Extra information about the problem
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002CDE1EA
BCP3: 0000000000000001
BCP4: 0000000000000197
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Extra information about the problem
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Bucket ID: X64_0x1e_0_nt!KySwitchKernelStackCallout+5
Server information: 35ea1674-e1a1-4871-8a8f-6287852005fc


So I've only gotten 1 stop error since I installed the new power supply, and it's different from the 1e errors. I've attached the dump. Please help if you can.

By the way, I was watching a video on one monitor, while browsing the web with the other when I got the SYSTEM_EXIT_OWNED_MUTEX stop error.

Another bit of information. I notice, that when I put the chassis cover on the computer, the fan sometimes buzzes. I can't tell if it's the processor fan or the video card fan that's buzzing, but it only happens when the cover is on or near the computer (I've leaned it next to the computer, but not completely on and it buzzes sometimes). It started doing this a few days before I installed the power supply.

I've checked to make sure there are no cables too close the fans. Strange that it happens when the cover is just near the computer.

Regardles of whether it's buzzing or not, or if the cover is on, near or completely far away, I still get BSODs. Perhaps it's running a little hot? There's no way for me to tell, as I don't think my PC came with any temperature software. In either case, I'm not sure adding a chassis fan will help much, since I'm getting crashes even when the cover is off completely and there's plenty of ventilation. It could be a bad fan. But, this video card is brand new though, and I had sent this computer out to get fixed three times and they found no hardware problems (including the CPU). When I sent it out to get fixed I had to take out my BDRW drive, my two extra hard drives and my video card and capture card. I was still getting BSODs even when all of these were taken out, but they were unable to recreate the issue in shop.

Could someone tell me how to read those crash dump files? I'm guessing the answer's in there, but I don't really know how to read those files.

Same cause, Memory Corruption. This could indicate a bad motherboard/hardware

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 39, {fffff80002d1d7a0, fffffa8006ad08f0, fffffa8006ad08f0, 0}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

SYSTEM_EXIT_OWNED_MUTEX (39)
Arguments:
Arg1: fffff80002d1d7a0
Arg2: fffffa8006ad08f0
Arg3: fffffa8006ad08f0
Arg4: 0000000000000000

Debugging Details:
------------------


FAULTING_IP: 
nt!CcWorkerThread+0
fffff800`02d1d7a0 488bc4          mov     rax,rsp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x39

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002c5e32b to fffff80002cd7d00

STACK_TEXT:  
fffff880`03153ca8 fffff800`02c5e32b : 00000000`00000039 fffff800`02d1d7a0 fffffa80`06ad08f0 fffffa80`06ad08f0 : nt!KeBugCheckEx
fffff880`03153cb0 fffff800`02f7432e : 00000000`00000000 fffffa80`06b08040 00000000`00000080 fffffa80`06a0a040 : nt! ?? ::FNODOBFM::`string'+0x59370
fffff880`03153d40 fffff800`02cc9666 : fffff880`03088180 fffffa80`06b08040 fffff880`03093040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03153d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002d1d7be - nt!CcWorkerThread+1e
    [ b0:f0 ]
1 error : !nt (fffff80002d1d7be)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

Before taking out the video card, I decided to run driver verifier again, this time without checking the microsoft drivers (as described in the steps above). I left the computer idle and left for a few hours. When I came back, there was a lovely BSOD on my screen saying it had caught a driver attempting to corrupt my computer. The problem is that the driver was not listed on the blue screen. I took a photo of it, maybe you can figure which driver is the culprit. I've also attached a new BSOD and Perfmon report.

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Files that help describe the problem
080311-21730-01.dmp
sysdata.xml
WERInternalMetadata.xml
View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.
Extra information about the problem
BCCode: c4
BCP1: 0000000000000081
BCP2: FFFFFA800A481750
BCP3: 000000000000008A
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

I uninstalled the nvidia drivers and software, and I took out the video card that was buzzing, and put the one that came with my computer back in. I restarted and windows installed the ati drivers and software for this video card automatically. I restarted again to complete the installation, and I ran driver cleaner pro to remove any remnants of the previous video card.

I decided to run driver verifier again to see if it would BSOD again. Sure enough, after browsing the internet for about 30 mins, it shut down and showed me the same BSOD as before.


Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Extra information about the problem
BCCode: c4
BCP1: 0000000000000081
BCP2: FFFFFA800B184F40
BCP3: 000000000000008A
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1


So I'm guessing the problem isn't the video card, despite the buzzing noise the fan was making. Here's the list of drivers I checked off when running verifier:

asacpi.sys
asinshelp64.sys
asio.sys
asupio.sys
dump_dumpata.sys
dump_sumpfve.sys
amdxata.sys
atipcie.sys
atikmpag.sys
atikmdag.sys
avertm62_x64.sys
gearaspiwdm.sys
secdrv.sys
mcdbus.sys
rt64win7.sys
viahduaa.sys

There are a ton of Microsoft drivers that I didn't check off this time around. Last time I checked them all off windows froze starting up. Perhaps there is a problem with the microsft drivers. I don't know, but there's so many it'd take forever to test them all individually.

I'm not really sure where to go from here. I guess I could check my hard drives for errors. Any ideas?

yowanvista said:

Same cause, Memory Corruption. This could indicate a bad motherboard/hardware

Can you give me more info? As I said before I had the computer sent out to be fixed a few times but they found no hardware errors. If it's the hardware, I want to be sure before I send it out again. If it's my hardware (the video card, the two extra hard drives, the capture card, or the dvd rom drive), then I obviously won't send it out, since they don't support it. Is there any way I can narrow this down?