Jump to content

Build Theme!
  •  
  • Infected?

Welcome to What the Tech - Register now for FREE

A community of volunteers who share their knowledge, and answer your tech questions. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message, and all ads will be removed once you have signed in.

Create an Account Login to Account


Photo

Blue Screen error BCCode 1e


  • Please log in to reply
3 replies to this topic

#1 Pirus504

Pirus504

    Authentic Member

  • Authentic Member
  • PipPip
  • 59 posts

Posted 03 August 2012 - 12:20 AM

so for the past two weeks, every now and again at random times, my computer goes to a blue screen and shuts itself down. after much research the only thing i've found is that it either is my drivers, my memory, or my processor. when i checked my drivers everything appeared to be up to date and working fine which leads me to think its either memory or my processor but i don't know. i'm leaving for college in about 3 weeks and i'd like to get this resolved before i leave. here's the info from the latest crash.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional 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

Files that help describe the problem:
C:\Windows\Minidump\080312-15974-01.dmp
C:\Users\Jeffrey\AppData\Local\Temp\WER-38391-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft....mp;clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

i got some great help here getting a nasty virus removed and i'm hoping you guys can help me again. i'd really appreciate it ^.^

Advertisement


#2 paws

paws

    Tech Team

  • Administrator
  • 5,260 posts

Posted 03 August 2012 - 01:38 AM

Hi Pirus504,
Sorry to hear about the blue screen issue...must be very annoying.
Please go here:
http://www.resplendence.com/downloads

Scroll down to Crash Analysis Tool
and download:
WhoCrashed.

Now run WhoCrashed. Click the Analyze button and follow the instructions in the report..... and copy and paste the output into your reply and one of us here will try to help.
Regards
paws
.

#3 Pirus504

Pirus504

    Authentic Member

  • Authentic Member
  • PipPip
  • 59 posts

Posted 03 August 2012 - 04:35 AM

so i launched whocrashed and i have this info, if this is what your looking for. System Information (local) -------------------------------------------------------------------------------- computer name: JEFFREY-PC windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: GenuineIntel Intel® Core™ i7 CPU 860 @ 2.80GHz Intel586, level: 6 8 logical processors, active mask: 255 RAM: 8580620288 total VM: 2147352576, free: 1978494976 -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Fri 8/3/2012 5:09:18 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\080312-15974-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190) Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Fri 8/3/2012 5:09:18 AM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheck+0x0) Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sun 7/29/2012 7:48:14 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\072912-17456-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0xFFFFF3000FDA7290, 0x2, 0x0, 0xFFFFF800030B185D) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Thu 6/28/2012 9:36:52 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\062812-17472-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0x44 (0xFFFFFA8008798760, 0xEAE, 0x0, 0x0) Error: MULTIPLE_IRP_COMPLETE_REQUESTS file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Thu 4/26/2012 4:29:05 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\042612-16395-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009C33750, 0xFFFFFA8009C33A30, 0xFFFFF80003192240) Error: CRITICAL_OBJECT_TERMINATION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 5 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.

#4 Pirus504

Pirus504

    Authentic Member

  • Authentic Member
  • PipPip
  • 59 posts

Posted 07 August 2012 - 08:17 PM

was that the right info?

Advertisement




Similar Topics: Blue Screen error BCCode 1e     x


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users