Bluescreen Error BCCode 1e

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.

Seems like a RAM problem, you should test your RAM
RAM - Test with Memtest86+

Code:

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

yowanvista said:

Seems like a RAM problem, you should test your RAM
RAM - Test with Memtest86+

Code:

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

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 :)

yowanvista said:

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?

EmperorNortonI said:

yowanvista said:

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

yowanvista said:

EmperorNortonI said:

yowanvista said:

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.

This one should be fine for your build, but test your RAM before replacing the PSU
http://www.newegg.com/Product/Produc...82E16817139020
You may get BSODs if your hardware is underpowered

yowanvista said:

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.

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