BSOD on boot after Windows logo. Cause: ntoskrnl.exe ( nt+371610 )

[stuckkie]

Hello. I'm getting a BSOD on boot, immediately after the flying Windows logo (before login screen). The BSOD flashes on the screen for a second, and then the computer reboots. I'm running Windows 7 64 bit.
This problem came out of nowhere as I've been running my PC flawlessly for years.

Possible causes:
* Earlier today, the power cut out whilst Windows was booting up (before the BSOD problem).
* Yesterday, I installed a few games and apps (emulators), but I doubt that is the cause of this.

I am able to boot into safe mode without issue, but I cannot boot into normal Windows.

Steps I've taken to try and solve this:
* Windows Startup Repair - It failed (It was unable to fix the problem)
* System Restore to a few days prior, no effect.
* Unplugged all USB/peripherals from my PC (including keyboard).
* Removed and reinserted the RAM
* Restored BIOS to factory defaults
* Opened the Windows/Minidump file, it says fault was "Probably caused by ntoskrnl.exe ( nt+371610 )"
* Ran memtest86 for a while to check memory. 1 Pass, 0 errors.
* In safe mode, ran MSconfig and disabled all non-Microsoft entries from "Services" and "Startup" tabs

None of the above has fixed the problem, and I don't know what else to try. Any help is much appreciated.
(I have attached the minidumps).

 

[centaur78]

Hi

The SYSTEM_EXIT_OWNED_MUTEX is more of a bugcheck error... and since its caused by ntoskrnl .... i have a feeling it more of a device driver related error....

try to enable boot logging at the F8 screen and start the system normally and post the bootlog in here..

Also try the last known good configuration at the F8 screen.... see if that solves the problem.

 

[stuckkie]

Hi

The SYSTEM_EXIT_OWNED_MUTEX is more of a bugcheck error... and since its caused by ntoskrnl .... i have a feeling it more of a device driver related error....

try to enable boot logging at the F8 screen and start the system normally and post the bootlog in here..

Also try the last known good configuration at the F8 screen.... see if that solves the problem.

Thanks for taking the time to help. I tried the last known good configuration and it didn't work. I still got the same BSOD with the "SYSTEM_EXIT_OWNED_MUTEX" message.

I have attached the boot log, if you can find anything that doesn't look right.

 

[centaur78]

Hmmm

The last file that is loaded is the FastFat.sys.....

i would suggest you do a Diagnostic startup.... by going into SAFEMODE first, and then @ the run command type msconfig and select the Diagnostic Statup.... apply and reboot.... this will load only the basic drivers and services...

In that case if you do get to the desktop without a hitch.... then it would most probably be a problem with Thridparty drivers and rule out windows issue ...

 

[stuckkie]

i would suggest you do a Diagnostic startup.... by going into SAFEMODE first, and then @ the run command type msconfig and select the Diagnostic Statup.... apply and reboot.... this will load only the basic drivers and services...

In that case if you do get to the desktop without a hitch.... then it would most probably be a problem with Thridparty drivers and rule out windows issue ...

When I click apply, it automatically moves the selection to "Selective startup" with "Load system services" and "use original boot configuration" selected. Is this correct? (I cant get it to stay on Diagnostic startup).
Even with selective startup, I still get the BSOD.

 

[centaur78]

are u doing this in safemode ?

 

[stuckkie]

Yes I am.

 

[centaur78]

Alright

lets try with Selective Startup... with everything deactivated. apply and reboot..

 

[stuckkie]

I cannot uncheck "use original boot configuration", it wont let me (its grayed out). I can uncheck "load system services", but when I hit apply, it re-checks it again.
Is this supposed to be happening?

 

[centaur78]

yes that is normal..

Try and reboot now...

 

[stuckkie]

I tried and I still get the BSOD.

 

[centaur78]

alright

first of i only have the minidumps and nbtlogs .... i would like you to go ahead and fill up you system specs on your profile.

Secondly use the Blue Screen of Death (BSOD) Posting Instructions to post the complete list of files needed for trouble shooting...