BSOD after booting up, BCCode: 1000007e

ME1960 · 24 Jun 2012

Can anyone tell me what this rubble means? What's wrong, and FYI I've already ruled out RAM maulfunctions as the causal factor. Went and got 2 brand new RAM sticks Corsair Dominator 4GB Kit PC3-12800, 1600MHz, 2x240 DIMM put them in but the BSOD did not stop occuring. For some reason when the BSOD presents and the PC reboots for the 1st time it reboots as its supposed to do, it prompts me to choose from:
1. Boot into safe mode
2. Boot inte safe mode with CMD
3. Boot into safe mode with network access
and
4. Boot windows normal

If i choose boot as normal the system boots up and im able to log in and within say 30-40 seconds it reboots again showing the same BSOD as before. But this time when it reboots and i press nr.4 Bott windows normal it stops when it gets to the "Starting Windows" screen, the blue, green, red and yellow dot never starts to swirl forward. It just stops at that screen no matter how long you wait.
When I then turn off the computer by a push on the power button it shuts down immidietly and when I turn it on I get a message that says windows was not shut down
correctly and i can choose to start it from the same 4 alternatives as before but when I now press nr.4 it boots up no problem at all. Runs smooth as whenever.

Same story every time I go to turn on the computer.

Down below is the message that windows displays when I log in.
I have also attached the 2 files mentioned in the message.

Problemsignatur:
Problemhändelsens namn: BlueScreen
OS-version: 6.1.7601.2.1.0.768.3
Språkvariant-ID: 1053

Ytterligare information om problemet:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002C64AB3
BCP3: FFFFF88003308968
BCP4: FFFFF880033081C0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Filer som hjälper till att beskriva problemet:
C:\Windows\Minidump\062412-13712-01.dmp
C:\Users\Marcus\AppData\Local\Temp\WER-46971-0.sysdata.xml

Läs vår sekretesspolicy online:
Sekretesspolicyn för Windows 7 - Microsoft Windows

Om sekretesspolicyn online inte är tillgänglig kan du läsa vår sekretesspolicy offline:
C:\Windows\system32\sv-SE\erofflps.txt

FredeGail · 24 Jun 2012

Hello and welcome to Sevenforums.

BSOD Report

Drivers to be aware of

The provided information doesn't give a full review of what's going on, but looking at it, you'll know that a Western Digital SCSI Arcitecture Model (SAM) WDM driver has been acting a bit up.

Update this driver. WD Support / Downloads / Select Product

Have a look at https://www.sevenforums.com/crashes-d...tructions.html, from there, we can assure more detailed conclusions and solutions to your problem.

Memory, known bugcheck

Code:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002c64ab3, The address that the exception occurred at
Arg3: fffff88003308968, Exception Record Address
Arg4: fffff880033081c0, Context Record Address

This code appeared. Please download a copy of Memtest86+ and leave it for 7-8 passes. You mentioned you had problems booting your computer, Memtest86+ is a great place to start.

Memtest86+

Greetings from Denmark!
Frederik.