BSOD few moments after startup, but works in safe mode.

LewiiG · 09 Mar 2014

So I posted here before about my laptop having BSOD problems whilst playing games (Multiple BSODs caused by ntoskrnl.exe (apparently) when playing games) and with help came to the conclusion that after 5 good years of use it is simply just dying and can no longer run games or anything strenuous. I just used it for browsing and other non gaming tasks since then fine.

However it's now gotten to the point where I can't even start the computer for more than a minute without crashing into a BSOD. It logs in and gets to the desktop, but will soon show the error screen. Since then I have had to use safe mode to do work or do whatever I am doing which is a bit handicapped and awkward. I found it interesting though that I was able to run games that were previously unable to even start in normal mode in safe mode (with some somewhat unplayable lag but it ran). Isn't this supposed to indicate some sort of software error? I don't know much if anything about BSOD errors and I am probably being too hopeful that my laptop could be restored to its pre 2014 state of glory, but maybe if someone could see what's going on and perhaps at least make normal mode functional again I would be very grateful. Even if just to say the laptop is screwed again.

Here is the SF file: Attachment 309635

It may contain errors from games and the previous thread's problem but at a certain point after that they should all be shortly after booting errors. I hope that it's obvious which ones are which but if not I'll single them out if needed.

What I tried to solve the problem previously can be found in the other thread linked.

Thanks.

Gandalf · 11 Mar 2014

Hi Mr. G - it would be most helpful if you provided a zip file of only the .dmp files pertaining to your current issue. To the best of my understanding, when a computer runs in the Safe mode but not in the normal mode, that is an indication of either one or more bad drivers and/or bad third party software. As soon as you can post the pertaining .dmp files, I hope to be able to isolate down the most likely cause of your current inconvenience.

To save some time, please post an image of your Device Manager.

LewiiG · 11 Mar 2014

Gandalf said:

Hi Mr. G - it would be most helpful if you provided a zip file of only the .dmp files pertaining to your current issue.

Attachment 309910

Gandalf said:

To save some time, please post an image of your Device Manager.

Attachment 309911

Gandalf said:

To the best of my understanding, when a computer runs in the Safe mode but not in the normal mode, that is an indication of either one or more bad drivers and/or bad third party software. As soon as you can post the pertaining .dmp files, I hope to be able to isolate down the most likely cause of your current inconvenience.

Hi Gandalf and thanks for the reply! the dmp files should all now be of the current problem though there is a possibility that the first two or so aren't. Yeah that's interesting. I updated my drivers using Driver Booster. I recently read somewhere though that it's better for me to do it manually than use automatic software for whatever reason.

Thanks for the help.

Gandalf · 11 Mar 2014

While your DM looks good, suggest you boot into the Safe mode.
If the Safe mode creates a new BSOD, please post that dmp file.

LewiiG · 12 Mar 2014

Gandalf said:

While your DM looks good, suggest you boot into the Safe mode.
If the Safe mode creates a new BSOD, please post that dmp file.

I have been in safe mode the whole time and I have been starting it using F8. I believe driver verifier is on with correct settings and even now safe mode has not had any BSOD errors. With Driver verifier on if I try to start in normal mode it just crashes straight away not even showing a blue screen and not even creating a dmp file. I really have no idea what to do with this. Why must these errors have impossible to find sources ><

I'm still open to any suggestions if there are more.

Thanks.

Gandalf · 12 Mar 2014

Boot into the Safe mode and open the Task Manager.
Is your Drive Verifier listed under Applications or Processes?

LewiiG · 13 Mar 2014

Gandalf said:

Boot into the Safe mode and open the Task Manager.
Is your Drive Verifier listed under Applications or Processes?

Hmm...I didn't find it listed on there when I looked just now. Does it turn off automatically at some point? I just tried to set it up again but it said "no settings were changed" so I figure it's on somewhere. I managed to get a dmp file created by driver verifier though which gives fltmgr.sys as the problem which is a first. This is that dump Attachment 310187

I'll see if I can get more driver verifier dmp information in the meantime.

Thanks.

Gandalf · 13 Mar 2014

This dmp identifies:
This was probably caused by the following module: fltmgr.sys (0xFFFFF88001222010)
Bugcheck code: 0xC9 (0x226, 0xFFFFF88001222010, 0x0, 0x0)

This file is associated with ESET.
From the Safe mode suggest you uninstall ESET with
http://download.eset.com/special/ESETUninstaller.exe

Suggest you replace it with
Microsoft Security Essentials - Microsoft Windows

After we resolve these issues, if you wish to reinstall ESET, that is your choice.
If by some chance you do not have ESET, please let us know.

FYI - Driver Verification information
http://msdn.microsoft.com/en-us/libr...(v=vs.85).aspx

LewiiG · 13 Mar 2014

Gandalf said:

This dmp identifies:
This was probably caused by the following module: fltmgr.sys (0xFFFFF88001222010)
Bugcheck code: 0xC9 (0x226, 0xFFFFF88001222010, 0x0, 0x0)

This file is associated with ESET.
From the Safe mode suggest you uninstall ESET with
http://download.eset.com/special/ESETUninstaller.exe

Suggest you replace it with
Microsoft Security Essentials - Microsoft Windows

After we resolve these issues, if you wish to reinstall ESET, that is your choice.
If by some chance you do not have ESET, please let us know.

FYI - Driver Verification information
Driver Verifier (Windows Drivers)

Thanks. Well I don't recall ever having or using ESET but the uninstaller apparently uninstalled it successfully. I was using Microsoft Security Essentials as well. It seems the laptop is able to load into the desktop now...but only until my wallpaper tries to appear at which point BSOD. Not sure if that's related. Could be a different problem or the same but delayed somehow idk. Well I have extra dmps and only those this time if that's okay. Here Attachment 310211

Thanks for the help again.

*Edit* So I decided to uninstall the display drivers and now normal mode works using the standard VGA driver thing. If I try to update to the most recent Intel Mobile Chipset again, the BSOD problem continues. So basically I'm here now in normal mode with games actually running (again with much lag but still) and at a less than desirable resolution. Not sure if this would be considered a fix or is obvious, but at least I have more functionality than safe. Aren't there any other drivers out there that could restore the resolution and game playability? Or does it not work like that?

Gandalf · 13 Mar 2014

Check out #1 and #3 for possible fixes ...

These dmp files indicate:

1. This was probably caused by the following module: storport.sys (storport!RaidUnitCompleteRequest+0x208)
Bugcheck code: 0xA (0x238, 0x2, 0x0, 0xFFFFF800034C8C86)
description: Microsoft Storage Port Driver
Try this...
"0x000000BE" Stop error message when you use the Storport.sys driver to manage some storage devices in Windows Server 2008, in Windows Vista, in Windows 7 or in Windows Server 2008 R2

2. This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x3093B9A0E6, 0x2, 0x0, 0xFFFFF800034D71A7)
The CAUSE is a Windows component which means something else drove it into Fault.

3. This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+0x2A)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800477F0AA)
description: DirectX Graphics MMS
Try this...
How to install the latest version of DirectX

4. This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFF7FF8F5EEF12, 0x8, 0xFFFFF7FF8F5EEF12, 0x5)
The CAUSE is a Windows component which means something else drove it into Fault.