Solved Bluescreen Error BCCode 1e

[EmperorNortonI]

I can't figure out why I randomly keep getting blue screen errors. The error code is not always the same, and it blue screens unexpectedly no matter what I'm doing. I've taken each bit of hardware out one at a time and even reinstalled to factory setting several times, but still get the errors every so often. I sent it to get fixed, but they couldn't figure out what is wrong. I suspect that it's a driver issue or maybe a problem with my power supply. I have a Geforce GTS video card that I replaced through RMA, but I'm still getting the same issue. Lately I've been getting 1e blue screen errors

My last blue screen error was this:

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


Also got this yesterday, no blue screen, just a random restart:

Description
The previous system shutdown at 3:38:28 PM on ‎7/‎27/‎2011 was unexpected.

And also this one on Monday

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: FFFFFFFFC000001D
BCP2: FFFFF80002C9C6A5
BCP3: 0000000000000000
BCP4: 0000000000008000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Bucket ID: X64_MEMORY_CORRUPTION_ONE_BIT
Server information: 0abdc3d4-b887-4fe4-baba-b4a8b3f5f928

7/19, another unexpected restart (This was before I replaced the video card):
Description
The previous system shutdown at 11:08:08 AM on ‎7/‎19/‎2011 was unexpected.

And on 7/8, I had some more unexpected shutdowns:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c000001d, 0xfffff80002e01fa5, 0xfffff88009296f50, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 070811-21871-01.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c000001d, 0xfffff80002c930bd, 0xfffff88008b72b30, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 070811-24882-01.


I have no data from before this because I did a factory reset on 7/6, but this has been going on since I bought the computer in January.

I've attached my dump with the perfmon report. My system specs are laid out in my profile. I'd be enourmously grateful if someone could figure out the cause of this problem.

 

[yowanvista]

Seems like a RAM problem, you should test your RAM
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff8800bbd1b28 -- (.exr 0xfffff8800bbd1b28)
ExceptionAddress: fffff80002c877f5 (nt!KxSwitchKernelStackCallout+0x0000000000000005)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff8800bbd1bd0 -- (.trap 0xfffff8800bbd1bd0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800bbc0000 rbx=0000000000000000 rcx=fffff88003d3b0c8
rdx=fffff88001266384 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c877f5 rsp=fffff8800bbd1d60 rbp=fffff88003d3b150
 r8=fffff8800bbcc000  r9=0000000000000000 r10=fffff8800bbd1db0
r11=fffff8800bbd1d60 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KxSwitchKernelStackCallout+0x5:
fffff800`02c877f5 4d85c9          test    r9,r9
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c876be to fffff80002c8fcd0

STACK_TEXT:  
fffff880`0bbd0c08 fffff800`02c876be : fffffa80`06f8a700 fffffa80`0acb5180 00000000`00000000 fffff800`02ce70cb : nt!KeBugCheck
fffff880`0bbd0c10 fffff800`02cbb55d : fffff800`02e94a54 fffff800`02dd70d8 fffff800`02c10000 fffff880`0bbd1b28 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`0bbd0c40 fffff800`02cba335 : fffff800`02dd70d0 fffff880`0bbd0cb8 fffff880`0bbd1b28 fffff800`02c10000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0bbd0c70 fffff800`02ccb3b1 : fffff880`0bbd1b28 fffff880`0bbd1380 fffff880`00000000 fffff880`03d3af90 : nt!RtlDispatchException+0x415
fffff880`0bbd1350 fffff800`02c8f382 : fffff880`0bbd1b28 fffffa80`0b644690 fffff880`0bbd1bd0 fffffa80`0b644690 : nt!KiDispatchException+0x135
fffff880`0bbd19f0 fffff800`02c8d4df : fffff880`0bbd1bd0 00000000`00000000 fffffa80`0acd3a00 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0bbd1bd0 fffff800`02c877f5 : fffff880`03d3a260 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInvalidOpcodeFault+0x11f
fffff880`0bbd1d60 fffff800`02c877d1 : 00000000`00000000 00000000`00000000 fffff880`0bbd2000 fffff800`02c9c832 : nt!KxSwitchKernelStackCallout+0x5
fffff880`03d3af90 fffff800`02c9c832 : fffffa80`07046b40 00000000`00000002 fffffa80`072a1e40 fffff8a0`0a3ee140 : nt!KiSwitchKernelStackContinue
fffff880`03d3afb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x2a2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02c876be 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

Followup: MachineOwner
---------

 

[EmperorNortonI]

Seems like a RAM problem, you should test your RAM
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
 
Debugging Details:
------------------
 
 
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
 
FAULTING_IP: 
+0
00000000`00000000 ??              ???
 
EXCEPTION_PARAMETER1:  0000000000000000
 
EXCEPTION_PARAMETER2:  0000000000000000
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
BUGCHECK_STR:  0x1E
 
PROCESS_NAME:  svchost.exe
 
CURRENT_IRQL:  0
 
EXCEPTION_RECORD:  fffff8800bbd1b28 -- (.exr 0xfffff8800bbd1b28)
ExceptionAddress: fffff80002c877f5 (nt!KxSwitchKernelStackCallout+0x0000000000000005)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0
 
TRAP_FRAME:  fffff8800bbd1bd0 -- (.trap 0xfffff8800bbd1bd0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800bbc0000 rbx=0000000000000000 rcx=fffff88003d3b0c8
rdx=fffff88001266384 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c877f5 rsp=fffff8800bbd1d60 rbp=fffff88003d3b150
 r8=fffff8800bbcc000  r9=0000000000000000 r10=fffff8800bbd1db0
r11=fffff8800bbd1d60 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KxSwitchKernelStackCallout+0x5:
fffff800`02c877f5 4d85c9          test    r9,r9
Resetting default scope
 
LAST_CONTROL_TRANSFER:  from fffff80002c876be to fffff80002c8fcd0
 
STACK_TEXT:  
fffff880`0bbd0c08 fffff800`02c876be : fffffa80`06f8a700 fffffa80`0acb5180 00000000`00000000 fffff800`02ce70cb : nt!KeBugCheck
fffff880`0bbd0c10 fffff800`02cbb55d : fffff800`02e94a54 fffff800`02dd70d8 fffff800`02c10000 fffff880`0bbd1b28 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`0bbd0c40 fffff800`02cba335 : fffff800`02dd70d0 fffff880`0bbd0cb8 fffff880`0bbd1b28 fffff800`02c10000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0bbd0c70 fffff800`02ccb3b1 : fffff880`0bbd1b28 fffff880`0bbd1380 fffff880`00000000 fffff880`03d3af90 : nt!RtlDispatchException+0x415
fffff880`0bbd1350 fffff800`02c8f382 : fffff880`0bbd1b28 fffffa80`0b644690 fffff880`0bbd1bd0 fffffa80`0b644690 : nt!KiDispatchException+0x135
fffff880`0bbd19f0 fffff800`02c8d4df : fffff880`0bbd1bd0 00000000`00000000 fffffa80`0acd3a00 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0bbd1bd0 fffff800`02c877f5 : fffff880`03d3a260 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInvalidOpcodeFault+0x11f
fffff880`0bbd1d60 fffff800`02c877d1 : 00000000`00000000 00000000`00000000 fffff880`0bbd2000 fffff800`02c9c832 : nt!KxSwitchKernelStackCallout+0x5
fffff880`03d3af90 fffff800`02c9c832 : fffffa80`07046b40 00000000`00000002 fffffa80`072a1e40 fffff8a0`0a3ee140 : nt!KiSwitchKernelStackContinue
fffff880`03d3afb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x2a2
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02c876be 90              nop
 
SYMBOL_STACK_INDEX:  1
 
SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
IMAGE_NAME:  ntkrnlmp.exe
 
DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b
 
FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
 
BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
 
Followup: MachineOwner
---------

I find that unlikely, simply because I've run several memory checks and have not found any errors. I also sent this computer out to get fixed under the manufacturers warranty 3 times and they were unable to find problems with the memory. I will run memtest86 though, since I haven't tried that memory checker.

Another bit of information: The computer I had before this was also getting random blue screen errors usually something to the effect of The Memory Index could not be read, or something about a nonindexed pagefault exception. I was using the same monitors, video card (the older Nvidia 9800 GT that I recently replaced), two of the same hard drives, the same speaker setup, one extra LG BDROM drive that I transferred to this computer, and a PCI-E HD video capture card that I also transferred to this computer. I've taken all of these bits of hardware out one by one to find out which one was causing the errors between both comptuers, but I still got the error. I did run memtest86 for 8 passes on the old computer (it was suggested by this forum actually) and found no errors.

Could it be a power supply issue? I'm running lots of hardware in this computer. It's a 400Watt power supply so it should be able to handle it. The older didn't have as strong a power supply, don't remember how many Watts though.

 

[yowanvista]

No, a 400W PSU is too weak for your PC. You have at least a 600W one
Nvidia recommends PSU with a minimum of 450W for GTS250

 

[EmperorNortonI]

No, a 400W PSU is too weak for your PC. You have at least a 600W one
Nvidia recommends PSU with a minimum of 450W for GTS250

Okay, I'll look into replacing the power supply. It still bothers me though that I was getting the blue screen error even when I was using just the video card that came preinstalled (wasn't nearly as demanding). Then again, it could be because of all the other hardware plugged in (3 hard drives, 1 DVDRW, 1 BDRW drive, video capture card and I'm usually using 4 or 5 usb ports at a time). So I'm not sure I should go solely by the video card specs for selecting a power supply. Do you have any reccomendations on what power supply I should get?

 

[yowanvista]

No, a 400W PSU is too weak for your PC. You have at least a 600W one
Nvidia recommends PSU with a minimum of 450W for GTS250

Okay, I'll look into replacing the power supply. It still bothers me though that I was getting the blue screen error even when I was using just the video card that came preinstalled (wasn't nearly as demanding). Then again, it could be because of all the other hardware plugged in (3 hard drives, 1 DVDRW, 1 BDRW drive, video capture card and I'm usually using 4 or 5 usb ports at a time). So I'm not sure I should go solely by the video card specs for selecting a power supply. Do you have any reccomendations on what power supply I should get?

The default PSU that comes with your build can only provide the required power for the PC. Additional hardware will require much more power
Any PSU in the 600-800W range should be fine for your PC
Cooler Master PSU calculator

 

[EmperorNortonI]

No, a 400W PSU is too weak for your PC. You have at least a 600W one
Nvidia recommends PSU with a minimum of 450W for GTS250

Okay, I'll look into replacing the power supply. It still bothers me though that I was getting the blue screen error even when I was using just the video card that came preinstalled (wasn't nearly as demanding). Then again, it could be because of all the other hardware plugged in (3 hard drives, 1 DVDRW, 1 BDRW drive, video capture card and I'm usually using 4 or 5 usb ports at a time). So I'm not sure I should go solely by the video card specs for selecting a power supply. Do you have any reccomendations on what power supply I should get?

The default PSU that comes with your build can only provide the required power for the PC. Additional hardware will require much more power
Any PSU in the 600-800W range should be fine for your PC
Cooler Master PSU calculator

Cool thanks, looks like I will need over 450 Watts. Is it common for PSU issues to cause blue screen errors like the ones I've been having?

I've never replaced a power supply before so I could use some tips. Are there any decently priced ones that are of good quality? The ones over 400 Watts are usually quite expensive, and I'd hate to spend a lot of money only to find it didn't fix my problem. Any stores I should shop from? I usually do Newegg, but they don't have a very wide selection. I also want to make sure it fits in this case before I buy it.

 

[yowanvista]

This one should be fine for your build, but test your RAM before replacing the PSU
http://www.newegg.com/Product/Product.aspx?Item=N82E16817139005http://www.newegg.com/Product/Product.aspx?Item=N82E16817139020
You may get BSODs if your hardware is underpowered

 

[EmperorNortonI]

This one should be fine for your build, but test your RAM before replacing the PSU
Newegg.com - CORSAIR Enthusiast Series TX650 V2 650W ATX12V v2.31/ EPS12V v2.92 80 PLUS BRONZE Certified Active PFC High Performance Power Supply
You may get BSODs if your hardware is underpowered

Great, thanks for your all your help, I'm going to run memtest86 now. I'll keep this thread updated with my results.

 

[EmperorNortonI]

No memory problems found. I just ordered that psu. We'll see if that solves it.

 

[EmperorNortonI]

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.

 

[EmperorNortonI]

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.

 

[EmperorNortonI]

I just received two new, completely different BSOD errors today.
The first one was this, I got it right after windows started:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
BCCode D1
NTFTS.SYS -address FFFFF (couldn't get the rest)
Oddly, this one doesn't show up in the maintenance history.

While running the BSOD dump system collection app to report this, I had another, different BSOD.
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: 24
BCP1: 00000000001904FB
BCP2: FFFFF8800E6ECA98
BCP3: FFFFF8800E6EC2F0
BCP4: FFFFF80002D0477D
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Bucket ID: X64_MEMORY_CORRUPTION_ONE_BIT
Server information: 5e514108-ec6d-4a7e-bfc8-9ee456875909

Since I already tested the memory, and replaced the power supply, what does that leave us with? A driver issue? I'd be damned if I knew which driver. The only hardware I changed was the power supply, but like I said I've been getting BSOD errors since I bought the computer, and I've replaced the video card, tested it without my capture card, without the two extra hard drives, and without the BD ROM drive and still was getting various BSODs. I'm at my wits end. Can someone help me?

 

[EmperorNortonI]

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.

 

[yowanvista]

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

*******************************************************************************
*                                                                             *
*                        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
---------

 

[EmperorNortonI]

I ran driver verifier following these steps:

1. Go to Start and type in "verifier" (without the quotes) and press Enter
2. Select "Create custom settings (for code developers)" and click "Next"
3. Select "Select individual settings from a full list" and click "Next"
4. Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
5. Select "Select driver names from a list" and click "Next"
6. Then select all drivers NOT provided by Microsoft and click "Next"
7. Select "Finish" on the next page

As Windows was starting, I got a blue screen error saying it had caught a driver that was causing problems. It disappeared before I could write it down so I restarted, disabled autorestart in safe-mode, and caught the screen shot below.

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: 00000000000000F6
BCP2: 00000000000002F8
BCP3: FFFFFA800B776B30
BCP4: FFFFF88009C16375
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

The driver was KMXAgent.sys. This is used with CA anti-virus. I uninstalled CA anti-virus and it started up properly. I thought the problem was solved but then I got another BSOD:

SYSTEM_SERVICE_EXCEPTION
BCCode 3B, it didn't save all tech details in the maintence history though:
Description
The previous system shutdown at 3:33:42 PM on ‎8/‎2/‎2011 was unexpected


I ran driver verifier again but couldn't recreate the Blue Screen error. I tried running driver verifier again, this time testing all drivers (instead of eliminating microsft drivers from the test). The computer failed to start (it just froze on the Windows logo). I had to reset driver verifier to get back into windows.

I also ran memtest86 again. This time for 10 passes. It found no errors.

It hasn't BSODed with driver verifier off since, so maybe that SYSTEM_SERVICE_EXCEPTION was just bad luck, still the fact that I can't start up when running driver verifier on all drivers (microsoft drivers included) is suspicious.

I also found out the buzzing was coming from my new video card. I'm going to take it out and run driver verifier again, unless one of you can give me tips for something different. It's definitely not memory, since I've tested that to death and found no errors. I also doubt it's a motherboard issue, since I sent this computer three times and they found no hardware problems. Still, any advice is appreciated. Attached is the most recent dump with perfmon. Please let me know if you find anything.

Also can one of you reccomend a good anti-virus software? I used CA because my ISP offered it for free, but since it's causing problems with my PC, I think I need something else.

 

[EmperorNortonI]

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

 

[EmperorNortonI]

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?

 

[EmperorNortonI]

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?

 

[Capt.Jack Sparrow]

Hello and Welcome!

Seems like the crashes is caused by mcdbus.sys which belongs to MagicISO SCSI Host Controller. I would recommend to uninstall it completely and disable driver verifier. See if it crashes again.

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000081, MmMapLockedPages called without MDL_MAPPING_CAN_FAIL
Arg2: fffffa800b184f40, MDL address.
Arg3: 000000000000008a, MDL flags.
Arg4: 0000000000000000, 0.

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


BUGCHECK_STR:  0xc4_81

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800031603dc to fffff80002cd9d00

STACK_TEXT:  
fffff880`0bb56588 fffff800`031603dc : 00000000`000000c4 00000000`00000081 fffffa80`0b184f40 00000000`0000008a : nt!KeBugCheckEx
fffff880`0bb56590 fffff800`031737ea : fffffa80`0b184f40 00000000`00000002 fffffa80`0a5a4c20 fffff880`0bb57000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0bb565d0 fffff880`010f0823 : fffff980`3148aee0 fffff980`2636efc0 fffffa80`0a210670 fffff800`000007ad : nt!VerifierMmMapLockedPages+0x4a
fffff880`0bb56610 fffff980`3148aee0 : fffff980`2636efc0 fffffa80`0a210670 fffff800`000007ad fffff980`3148aee0 : mcdbus+0x36823
fffff880`0bb56618 fffff980`2636efc0 : fffffa80`0a210670 fffff800`000007ad fffff980`3148aee0 fffff980`3148afb0 : 0xfffff980`3148aee0
fffff880`0bb56620 fffffa80`0a210670 : fffff800`000007ad fffff980`3148aee0 fffff980`3148afb0 fffff880`0bb56aa0 : 0xfffff980`2636efc0
fffff880`0bb56628 fffff800`000007ad : fffff980`3148aee0 fffff980`3148afb0 fffff880`0bb56aa0 fffff980`2636efc0 : 0xfffffa80`0a210670
fffff880`0bb56630 fffff980`3148aee0 : fffff980`3148afb0 fffff880`0bb56aa0 fffff980`2636efc0 fffffa80`0a5a4d70 : 0xfffff800`000007ad
fffff880`0bb56638 fffff980`3148afb0 : fffff880`0bb56aa0 fffff980`2636efc0 fffffa80`0a5a4d70 fffff880`0bb56ab0 : 0xfffff980`3148aee0
fffff880`0bb56640 fffff880`0bb56aa0 : fffff980`2636efc0 fffffa80`0a5a4d70 fffff880`0bb56ab0 fffff880`00000000 : 0xfffff980`3148afb0
fffff880`0bb56648 fffff980`2636efc0 : fffffa80`0a5a4d70 fffff880`0bb56ab0 fffff880`00000000 fffff980`2636efe8 : 0xfffff880`0bb56aa0
fffff880`0bb56650 fffffa80`0a5a4d70 : fffff880`0bb56ab0 fffff880`00000000 fffff980`2636efe8 fffffa80`0b09e800 : 0xfffff980`2636efc0
fffff880`0bb56658 fffff880`0bb56ab0 : fffff880`00000000 fffff980`2636efe8 fffffa80`0b09e800 fffff800`03171d3d : 0xfffffa80`0a5a4d70
fffff880`0bb56660 fffff880`00000000 : fffff980`2636efe8 fffffa80`0b09e800 fffff800`03171d3d fffff980`3148aee0 : 0xfffff880`0bb56ab0
fffff880`0bb56668 fffff980`2636efe8 : fffffa80`0b09e800 fffff800`03171d3d fffff980`3148aee0 00000000`00000002 : 0xfffff880`00000000
fffff880`0bb56670 fffffa80`0b09e800 : fffff800`03171d3d fffff980`3148aee0 00000000`00000002 fffffa80`6264636d : 0xfffff980`2636efe8
fffff880`0bb56678 fffff800`03171d3d : fffff980`3148aee0 00000000`00000002 fffffa80`6264636d fffffa80`0a5a4c20 : 0xfffffa80`0b09e800
fffff880`0bb56680 fffff880`010f02db : fffffa80`0a5a4c20 00000000`00000000 fffff880`00c0ed88 00000000`00000000 : nt!VerifierExAllocatePoolWithTag+0x1d
fffff880`0bb566c0 fffffa80`0a5a4c20 : 00000000`00000000 fffff880`00c0ed88 00000000`00000000 00000000`00000000 : mcdbus+0x362db
fffff880`0bb566c8 00000000`00000000 : fffff880`00c0ed88 00000000`00000000 00000000`00000000 fffff880`0bb568e0 : 0xfffffa80`0a5a4c20


STACK_COMMAND:  kb

FOLLOWUP_IP: 
mcdbus+36823
fffff880`010f0823 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  mcdbus+36823

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: mcdbus

IMAGE_NAME:  mcdbus.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49a3cd1f

FAILURE_BUCKET_ID:  X64_0xc4_81_VRF_mcdbus+36823

BUCKET_ID:  X64_0xc4_81_VRF_mcdbus+36823

Followup: MachineOwner
---------