Solved BSOD after wakeup from sleep

blueelvis · Dec 3, 2014

Freud said:
Still no problems with borrowed dimms.
I'm waiting for return shipment with replaced RMA dimms.

Sure thing. It means that the RAM you were using earlier is bad.

Let me know how it goes ^_^

Freud · Dec 21, 2014

My dimms has arrived yesterday from RMA!
I've tested them over 33hours without any erros!

Great!

Now i will se if computer is stable over the time.

I will be informing about progress.
Thank You for everything.

blueelvis · Dec 22, 2014

Freud said:
My dimms has arrived yesterday from RMA!
I've tested them over 33hours without any erros!

Great!

Now i will se if computer is stable over the time.

I will be informing about progress.
Thank You for everything.

Great ^_^

Keep me posted. Let me know if any problem occurs again.

-Pranav

Freud · Jan 17, 2015

Hello Pranav after three weeks!

I was on holidays so the computer was running but i was not using it.
No any sleeping states was during these last three weeks.

Yesterday I run computer into the sleep mode.
At the night BSOD occured.
Strange because something waked up computer.

Memories are ok. I can test dimms again but i'm just thinking what is going on.

Any idea?

View attachment 56656

Freud · Jan 18, 2015

Next BSOD today :think:

View attachment 56705

Freud · Jan 19, 2015

And.. next one today. I think minidumps is not showing anything.
I've red today some articles and on the internet there is a several causes - also with ssd resuming.

I don't know what next.
I can ofcourse buy new SSD or PSU, but it's not smart - i better want to know what is wrong.

Do you have any idea?

CPU is new
RAM is new and replaced with RMA.
Mobo is new.

PSU, HDD and SSD are old. Anyway benchmarks do not show any errors - they are clean after bench.

Maybe ssd after wake up is not resuming properly?
How to check it? Replace it with normal hdd?

Freud · Jan 19, 2015

Maybe I shouldn't use sleep mode?

.. but i want - there is one big advantage for me!

After sleep all apps are opened as before.

Freud · Jan 20, 2015

Okay - today after sleep no bsods, but I've changed one thing:
View attachment 56794

No I will see if any bsods occurs after wake up

blueelvis · Jan 20, 2015

Hi Freud ^_^,

I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-

Code:

7: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffffd000`3605b5e8 fffff802`e467eee3 nt!KeBugCheckEx
01 ffffd000`3605b5f0 fffff802`e44bef5b nt!MiBadRefCount+0x4f
02 ffffd000`3605b630 fffff800`85188c41 nt!MmUnlockPages+0x7eb
03 ffffd000`3605b6d0 00000000`00000000 [COLOR=#ff0000]vmx86[/COLOR]+0x3c41

In the first dump file, we have the VMWare Virtualization Driver. I would suggest you to remove VMWare till the time we are troubleshooting your system.

Code:

4: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffffd000`377de578 fffff801`98088eec nt!KeBugCheckEx
01 ffffd000`377de580 fffff801`981acc3f Ntfs!NtfsExceptionFilter+0x1e8c0
02 ffffd000`377de740 fffff801`435beb76 N[B][U]tfs!NtfsNetworkOpenCreate$filt$0[/U][/B]+0x18
03 ffffd000`377de770 fffff801`98068486 nt!_C_specific_handler+0x86
04 ffffd000`377de7e0 fffff801`435d6fed Ntfs!_GSHandlerCheck_SEH+0x76
05 ffffd000`377de810 fffff801`43559d35 nt!RtlpExecuteHandlerForException+0xd
06 ffffd000`377de840 fffff801`4355e0ee nt!RtlDispatchException+0x1a5
07 ffffd000`377def10 fffff801`435db6c2 nt!KiDispatchException+0x646
08 ffffd000`377df600 fffff801`435d9e14 nt!KiExceptionDispatch+0xc2
09 ffffd000`377df7e0 fffff801`9814abd3 nt!KiPageFault+0x214
0a ffffd000`377df978 fffff801`43535008 Ntfs!NtfsFcbTableCompare+0x3
0b ffffd000`377df980 fffff801`9815656c nt!RtlLookupElementGenericTableFullAvl+0x3c
0c ffffd000`377df9c0 fffff801`98120e5a Ntfs!NtfsCreateFcb+0x8c
0d ffffd000`377dfab0 fffff801`98127caf Ntfs!NtfsOpenFile+0x22a
0e ffffd000`377dfd00 fffff801`9810c630 Ntfs!NtfsCommonCreate+0x1104
0f ffffd000`377dff30 fffff801`97f98155 [B][U]Ntfs!NtfsNetworkOpenCreate[/U][/B]+0xec
10 ffffd000`377e0290 fffff801`97fbf090 fltmgr!FltpPerformFastIoCall+0x2b5
11 ffffd000`377e02f0 fffff801`438af686 fltmgr!FltpFastIoQueryOpen+0x161
12 ffffd000`377e0390 fffff801`43861219 nt!IopParseDevice+0xa66
13 ffffd000`377e05b0 fffff801`4385f043 nt!ObpLookupObjectName+0x6b9
14 ffffd000`377e0730 fffff801`438e64cd nt!ObOpenObjectByName+0x1e3
15 ffffd000`377e0860 fffff801`435db2b3 nt!NtQueryAttributesFile+0x141
16 ffffd000`377e0b00 00007ffe`d9f4101a nt!KiSystemServiceCopyEnd+0x13
17 00000000`025ce7f8 00000000`00000000 0x00007ffe`d9f4101a

In the second dump file, it seems we are dealing with a Network Share (Most Likely). Are you using any network shares?

Kindly turn on Driver Verifier using the below guide and make sure that you let the system crash a few times before re-running the SF Diagnostic Tool and upload the fresh ZIP File.
Driver Verifier - Enable and Disable - Windows 7 Help Forums

Let me know how it goes ^_^

EDIT - The attachment in your last post is invalid.

-Pranav

Freud · Jan 20, 2015

Yes - I'm using network shares - I have few shared folders.

Ok - I can remove VMWare temporarly to check stability.

I've fixed link above.
Here it is again:
View attachment 56795

I've changed it because bsod is only after wake up and someting tell me that it can be SSD.

I will inform how it goes. Thanks!

blueelvis · Jan 21, 2015

Sure thing. Let me know how it goes ^_^
Can you try disconnecting with the Network Shares and then checking the system for stability?

-Pranav

Freud · Jan 21, 2015

It could be complicated.
Now i'm trying to test computer with VMware and with shared folders but with changed new SSD / HDD power option.

After 2 days and after two sleeps there was no any problems.
Even after 12 hours of sleep.

I think I will be testing machine about 2 weeks all the time with sleeping for night and weekends and if no any bsod occurs then I will think that SSD is not compatible with default power options. Especially because a lot of topics on the internet with sand force ssd's have exactly the same symptom description.

After all I think I had not only one problem with bsod - there was several, but now It looks like only one left - I hope.

I will be informing you. If any bsod occurs I will disable shared folders and VMWare.

Thank You Pranav!

Freud · Jan 22, 2015

Ok. Next day brings me new bsod.

Next step is removing VMWare and shared folders.

I have question with it: what next?
Do you thinnk shared folders makes some network activity and touch vmware network drivers?

View attachment 56847

Freud · Jan 22, 2015

Unofortunately there I dont see ny common subset of issues in all minidumps.
So... looks like very randomed issues, but there is probably only one reason.

blueelvis · Jan 25, 2015

Hi Freud ^_^,

I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.

Code:

7: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffffd001`ec02c418 fffff803`3295c5e9 nt!KeBugCheckEx
01 ffffd001`ec02c420 fffff803`3295befc nt!KiBugCheckDispatch+0x69
02 ffffd001`ec02c560 fffff803`32957fed nt!KiSystemServiceHandler+0x7c
03 ffffd001`ec02c5a0 fffff803`328dad35 nt!RtlpExecuteHandlerForException+0xd
04 ffffd001`ec02c5d0 fffff803`328df0ee nt!RtlDispatchException+0x1a5
05 ffffd001`ec02cca0 fffff803`3295c6c2 nt!KiDispatchException+0x646
06 ffffd001`ec02d390 fffff803`3295abfe nt!KiExceptionDispatch+0xc2
07 ffffd001`ec02d570 fffff960`0013ef8e nt!KiGeneralProtectionFault+0xfe
08 ffffd001`ec02d700 fffff960`002477f7 win32k!PDEVOBJ::bDisabled+0x3e
09 ffffd001`ec02d730 fffff960`001ba201 win32k!DrvEnableDisplay+0x11b
0a ffffd001`ec02d790 fffff960`00247c4b win32k!DrvEnableMDEV+0x1e5
0b ffffd001`ec02d7f0 fffff960`0012d8df win32k!SafeEnableMDEV+0x2b
0c ffffd001`ec02d820 fffff960`0012d1c0 win32k!PowerOnGdi+0x7f
0d ffffd001`ec02d960 fffff960`0012c880 win32k!xxxUserPowerStateCalloutWorker+0x260
0e ffffd001`ec02da70 fffff960`000c7f74 win32k!xxxUserPowerCalloutWorker+0x90
0f ffffd001`ec02dad0 fffff803`3295c2b3 win32k!NtUserCallNoParam+0x44
10 ffffd001`ec02db00 00007ffd`c5ab18aa nt!KiSystemServiceCopyEnd+0x13
11 00000022`6d43fa08 00000000`00000000 0x00007ffd`c5ab18aa

We can see that the Win32K is enabling display and then running into an Exception which ultimately leads to the system crash. Below is a list of 3rd party drivers present on your system -

Code:

**************************Thu Jan 22 14:33:50.081 2015 (UTC + 5:30)**************************
[B][U]MBfilt64.sys                 Fri Jul 31 09:10:32 2009 (4A7267B0)
com0com.sys                  Tue Jan 25 20:16:00 2011 (4D3EE228)
[COLOR=#FF0000]V0700Vid.sys                 Wed Sep  7 11:00:56 2011 (4E670190)
[/COLOR][/U][/B]truecrypt-x64.sys            Tue Feb  7 14:39:36 2012 (4F30EA50)
AcpiCtlDrv.sys               Tue Jul 17 22:37:16 2012 (50059BC4)
vmci.sys                     Sat May 18 06:49:18 2013 (5196D716)
ICCWDT.sys                   Mon Aug 12 23:29:08 2013 (5209226C)
intelppm.sys                 Thu Aug 22 14:16:35 2013 (5215CFEB)
dump_storahci.sys            Thu Aug 22 17:10:39 2013 (5215F8B7)
vstor2-mntapi20-shared.sys   Wed Aug 28 15:55:49 2013 (521DD02D)
e22w8x64.sys                 Wed Mar 26 21:28:37 2014 (5332F92D)
TeeDriverx64.sys             Sat May 10 02:37:35 2014 (536D4397)
RTKVHD64.sys                 Wed May 28 17:47:12 2014 (5385D3C8)
iwdbus.sys                   Wed Jun 18 03:24:22 2014 (53A0B90E)
iocbios2.sys                 Wed Jun 18 12:18:56 2014 (53A13658)
vsock.sys                    Mon Jun 30 06:07:03 2014 (53B0B12F)
VMNET.SYS                    Sun Jul 27 19:00:27 2014 (53D4FEF3)
vmnetadapter.sys             Sun Jul 27 19:00:30 2014 (53D4FEF6)
vmnetbridge.sys              Sun Jul 27 19:00:32 2014 (53D4FEF8)
igdkmd64.sys                 Mon Sep 29 23:21:21 2014 (54299C19)
nvhda64v.sys                 Thu Oct  9 22:32:27 2014 (5436BFA3)
hcmon.sys                    Tue Nov 18 21:34:00 2014 (546B6DF0)
nvvad64v.sys                 Thu Nov 20 21:03:54 2014 (546E09E2)
vmnetuserif.sys              Fri Nov 21 06:29:48 2014 (546E8E84)
vmx86.sys                    Fri Nov 21 08:05:28 2014 (546EA4F0)
[COLOR=#FF0000][B][U]NvStreamKms.sys              Sat Nov 22 13:16:45 2014 (54703F65)
[/U][/B][/COLOR]nvlddmkm.sys                 Sat Dec 13 12:23:17 2014 (548BE25D)

Please physically disconnect your Webcam which you have connected with the system via USB Cable.
Please disable NVIDIA Streaming (NvStreamKMS.sys) as it is known to cause BSODs by following this **POST**.
Update the drivers which are highlighted in BLACK & UNDERLINE.
Please ensure that your system is UP TO DATE by checking and installing (if any) updates from the Windows Update.
If you are still facing crashed, kindly turn on Driver Verifier using this **GUIDE** and make sure that you let the system crash for few times before re-running the SF Diagnostic Tool and uploading the ZIP file.

I wonder why are we seeing entirely different problems after few days with your system. Either there is something else in the lower level of the system or this might be a coincidence. Let's see how it goes and keep me posted ^_^

-Pranav

Freud · Jan 29, 2015

HI!

First of all I did some more investigation about HDD / SSD.
Intuition tells me that something is wrong with SSD and resuming.

So... I've checked divers first and found one strange thing.
This driver was very very old (from 2006):
View attachment 57193

In next step I've updated this driver and installed Intel(R) Driver Update Utility 2.0.
I've decided to make only small steps: only one change and test, only one change and test.

So: now I'm testing machine every day with sleep, with VMWare, with shared folders and everything else but with new AHCI drivers.

6 days with no any BSOD after wake up. Even long sleep (more than 14 hours) ends with proper wake up.
I even slept computer while hardcore disk operation, music playing and so on...
After wake up computer was in the proper state and was continue all operations properly.

So....

First I will test computer for next 1-2 weeks and see if any bsod occur.
I think AHCI microsoft general driver from 2006 year could be a reason.

Especially because minidumps have in stack traces common "ntfs" keyword.
Especially that every mnidump tells that the reason is some driver.

I will let you know how it goes.
If any bsod will occurs I will do all things you recommend.

Thank YOU!

blueelvis · Jan 30, 2015

Hi Freud ^_^,

Those are some awesome troubleshooting steps you have taken. After installing the SSD, did you update your copy of Windows using Windows Update? I have a feeling that the Microsoft AHCI Driver won't be that old (2006). Thanks for sharing with us these steps as they help the future visitors a lot

Let me know how it goes ^_^

-Pranav

Freud · Jan 31, 2015

Hi Pranav,

Yes I did update my copy of Windows. I always doing it.
AHCI Driver was from 2006 based on the driver information in the device manager.
It was really strange.

Of course I will let you know!

Thank YOU!

blueelvis · Feb 7, 2015

Freud said:
Hi Pranav,

Yes I did update my copy of Windows. I always doing it.
AHCI Driver was from 2006 based on the driver information in the device manager.
It was really strange.

Of course I will let you know!

Thank YOU!

Hi Freud ^_^,

Sorry for the delayed response. I really needed to take a break

Sure thing. Kindly keep me updated ^_^

-Pranav

Freud · Feb 28, 2015

Hi Pranav!

Everything works like a charm.
I uninstalled VMWare and now using HyperV.
VMWare had problems two times with system closing (some drivers glitch).
HyperV is native, so everything works okay.

I removed also a lot of warnings from event viewer by system reconfiguration.
Now there is no any not controlled event viewer warning.

No any BSOD.

Everything looks OKAY!

In summary of all there was problems with not only one thing: there was few simultaneous problems and that's why diagnostics was very hard.

Thank You for all help!

Solved BSOD after wakeup from sleep

OMG Debugger!

Member

OMG Debugger!

Member

Member

Member

Member

Member

OMG Debugger!

Member

OMG Debugger!

Member

Member

Member

OMG Debugger!

Member

OMG Debugger!

Member

OMG Debugger!

Member

Similar threads