Win 8.1 - freeze after awaking from hibernation or standby

Damn it! :(

I just had a freeze today, so I tried testing "let's see if it's the network thingy" and started enabling the "can wake up device" options in the device manager.

Can wake up - ok - fine.
Can wake up + only magic packet - ok - fine.
Can wake up (remove only magic packet option) - ok - fine.
Disable "can wake up" - ok - driver verifier enabled BSOD.

Here are the minidump and the memory.dmp.

Damn, I am starting to feel that this might be a hardware issue, since I am on the windows network driver (which ran so well for a few days...).

https://mega.co.nz/#!0k5i3S7B!3rYqP8nSpkEW25ITF-KanH0ACA48z7Dpg2q2LOh6ix0
 
Code: 
00 ffffd001`3931afc8 fffff801`28b34487 nt!KeBugCheckEx
01 ffffd001`3931afd0 fffff801`28b23637 VerifierExt!SLIC_StatefulAbort+0x22b
02 ffffd001`3931b0c0 fffff801`28b23db3 VerifierExt!SLIC_XdvNdisMiniportOidRequestHandler_exit_NdisOidComplete+0xc7
03 ffffd001`3931b100 fffff801`294f2ea4 VerifierExt!XdvNdisMiniportOidRequestHandler_wrapper+0x777
04 ffffd001`3931b170 fffff801`294463c9 ndis!ndisMInvokeOidRequest+0x23df8
05 ffffd001`3931b1b0 fffff801`29444f4f ndis!ndisMDoOidRequest+0x42d
06 ffffd001`3931b260 fffff801`294454ce ndis!ndisQueueOidRequest+0x4bf
07 ffffd001`3931b400 fffff801`29985a1e ndis!NdisFOidRequest+0xc2
08 ffffd001`3931b4c0 fffff801`2944698e wfplwfs!LwfLowerOidRequest+0x6e
09 ffffd001`3931b4f0 fffff802`1dee8703 ndis!ndisFDoOidRequestInternal+0x2ee
0a ffffd001`3931b5f0 fffff801`29444d5a nt!KeExpandKernelStackAndCalloutInternal+0xf3
0b ffffd001`3931b6e0 fffff801`294454ce ndis!ndisQueueOidRequest+0x2ca
0c ffffd001`3931b880 fffff801`29f710b8 ndis!NdisFOidRequest+0xc2
0d ffffd001`3931b940 fffff801`2944698e pacer!PcFilterRequest+0x5c
0e ffffd001`3931b970 fffff802`1dee8703 ndis!ndisFDoOidRequestInternal+0x2ee
0f ffffd001`3931ba70 fffff801`2944f1f5 nt!KeExpandKernelStackAndCalloutInternal+0xf3
10 ffffd001`3931bb60 fffff801`2944f100 ndis!ndisFDoOidRequest+0x31
11 ffffd001`3931bba0 fffff801`2944ee2e ndis!ndisDoOidRequests+0x30
12 ffffd001`3931bbd0 fffff802`1df7636c ndis!ndisWorkerThread+0x8e
13 ffffd001`3931bc00 fffff802`1dfcd2c6 nt!PspSystemThreadStartup+0x58
14 ffffd001`3931bc60 00000000`00000000 nt!KiStartSystemThread+0x16


3: kd> !devstack ffffe00107c54050
  !DevObj           !DrvObj            !DevExt           ObjectName
> ffffe00107c54050  \Driver\RTL8168    ffffe00107c541a0  NDMP1
  ffffe00106d54720  \Driver\pci        ffffe00106d54870  NTPNP_PCI0018
!DevNode ffffe00106d543f0 :
  DeviceInst is "PCI\VEN_10EC&DEV_8168&SUBSYS_81681849&REV_06\4&18e591e5&0&00E5"
  ServiceName is "RTL8168"


Loaded Module Info: [rt630x64] 
         Module: Rt630x64
   Base Address: fffff8012c045000
     Image Name: Rt630x64.sys
   Machine Type: 34404 (X64)
     Time Stamp: 518cc4ec Fri May 10 10:59:08 2013
           Size: 94000
       CheckSum: 9d8fe
Characteristics: 22

It's the same reason as before, and strangely enough, the driver that caused the crash is the Realtek driver, and the same timestamp.
I'm wondering if the driver was automatically installed.
I don't think you're using the Windows generic driver anymore.

I'm still not convinced it's a hardware issue, it's not something - or at least from what I've seen - failing hardware would do.
 
Wow, THAT is confusing but relieving at the same time. It means it can be fixed! :) Thanks!

I am 150% sure I uninstalled the driver (and deleted driver files/data with device manager) and rebooted. Then a microsoft driver was installed.

http://i.imgur.com/Xl6XdZq.jpg

The driver supplier is microsoft and the device "name" is: Realtek PCIe GBE Familiy Controller.

When I install the realtek driver it says the exact device name.

Hmm... Do I manually delete the files now? How to check if windows installed the driver automatically?
 
Hmm this might be an evil hack but I will manually delete the driver file/move it and see what happens.

It could be a possibility that Realtek provided Microsoft with "runs on all chips" generic drivers and microsoft uses that driver as it's go-to driver. Driver details in device manager say that the driver provider is actually "realtek"... :-/

http://i.imgur.com/HPufRts.jpg
 
Hmm, I can not edit my old post. So another one.

I deleted the driver from windows/system32/drivers but after reboot it's back again. The same driver. So yeah I guess Realtek gave the driver to microsoft. :-/
 
Hmm, actually.
The driver itself is from Microsoft, my apologies.
I do see some bluetooth drivers, they would be a good idea to remove, I've seen lots of issues with them.
Just as a test.

Although I still think it's a bad driver.
Unfortunately, there isn't much you can do but try an update.

Yeah, you can't just delete the driver, it will come back.
 
Okay. Thank you for all your help. I don't know what to do now but I am happy that I nailed the source of corruption. :)

Just on a side note - COULD this be a hardware issue? Motherboard is 3-5 years old. How to hardware issues usually "show" themselves?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top