BSOD from sleep

I've always had this issue when I did use sleep mode. Because of this issue I just disabled PC from using sleep mode....no big deal.

Now, with the new FCU - a clean install; It set the PC to use sleep mode after 30 minutes of idle. It worked for almost 2 days and this morning....BAM. BSOD - IRQL NOT LESS OR EQUAL .....that's all it said. No driver was mentioned.

So now I'm asking for help with this issue. Here's the zip file as requested.


Attachment 158945

Attachment 158945

Well.....just another straw on the camels back for FCU. Thanks anyway.....maybe when the symbols are fixed you guys and debug it and tell me what's going on. I guess it's back to hurry and wait again.

Hi Plankton,

There maybe a problem with a harddrive which results in pagefile errors. See your event log. For example at around 6:30 on 18th Oct you had lots of these errors:
Attachment 158956

Looking at the crashdump I see the following sequence of events (read from bottom to top)

Code:

3: kd> !dpx
Start memory scan  : 0xfffffb080c90f4c8 ($csp)
End memory scan    : 0xfffffb080c910000 (Kernel Stack Base)

               rsp : 0xfffffb080c90f4c8 : 0xfffff803f62001e9 : nt!KiBugCheckDispatch+0x69
0xfffffb080c90f4c8 : 0xfffff803f62001e9 : nt!KiBugCheckDispatch+0x69
0xfffffb080c90f4f0 : 0xfffff803f611e8d2 : nt!MiDispatchFault+0x142
0xfffffb080c90f4f8 : 0xfffff803f611c002 : nt!MiAllocateWsle+0x442
0xfffffb080c90f5a8 : 0xfffff803f65bcfb8 : nt!ObpLookupObjectName+0x678
0xfffffb080c90f608 : 0xfffff803f61fe57d : nt!KiPageFault+0x23d
0xfffffb080c90f750 : 0xfffff803f64a2380 : nt!CmpRegistryLock
0xfffffb080c90f778 : 0xfffff803f611e8d2 : nt!MiDispatchFault+0x142
0xfffffb080c90f888 : 0xfffff803f6091000 : "nt!MmSetTrimWhileAgingState <PERF> (nt+0x0)"
0xfffffb080c90f8b8 : 0xfffff803f6595e36 : nt!ObpRemoveObjectRoutine+0x86
0xfffffb080c90f918 : 0xfffff803f611d826 : nt!MmAccessFault+0x686
0xfffffb080c90fa00 : 0x006d007200650050 :  !du "PermissionsharedBroker"
0xfffffb080c90fa08 : 0x0069007300730069 :  !du "issionsharedBroker"
0xfffffb080c90fa10 : 0x00680073006e006f :  !du "onsharedBroker"
0xfffffb080c90fa18 : 0x0064006500720061 :  !du "aredBroker"
0xfffffb080c90faf8 : 0xfffff803f61fe472 : nt!KiPageFault+0x132
0xfffffb080c90fb00 : 0xffffca82cad88080 :  Trap @ fffffb080c90fb00

This seems to confirm something is not right with reading and accessing data. Thoroughly check the hard drive and memory.

I used this dump: 101917-35328-01.dmp

Running the same command as you I get the following from WinDBG Preview:

Code:

3: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffffb08`0c90f4c8 fffff803`f62001e9 nt!KeBugCheckEx
01 fffffb08`0c90f4d0 fffff803`f61fe57d nt!KiBugCheckDispatch+0x69
02 fffffb08`0c90f610 fffff803`f611e8d2 nt!KiPageFault+0x23d
03 fffffb08`0c90f7a0 fffff803`f611d826 nt!MiDispatchFault+0x142
04 fffffb08`0c90f920 fffff803`f61fe472 nt!MmAccessFault+0x686
05 fffffb08`0c90fb00 00007ff8`555d4fb0 nt!KiPageFault+0x132
06 0000001d`6377b018 00000000`00000000 0x00007ff8`555d4fb0

hawkman said:

looking at event logs,

it appears youve installed a couple of extras, did the gsod start after installing one of these?
Gigabyte NIC - its showing odd shutdown events on IPV6 settings
Razer Keyboard - this is showing as a problem in the Dxdiag report
(phil/Axe0 have you seen this, appears to be a new addition to the log)


Roy

Can you provide a copy & paste of what you are referring to, I must have missed it and can't find it.

hawkman said:

looking at event logs,

it appears youve installed a couple of extras, did the gsod start after installing one of these?
Gigabyte NIC - its showing odd shutdown events on IPV6 settings
Razer Keyboard - this is showing as a problem in the Dxdiag report
(phil/Axe0 have you seen this, appears to be a new addition to the log)


Roy

I think you might be on to something here with the Razer issue. I "DON'T" have a Razer keyboard but I do have a Razer mouse (DeathAdder 3.5 -it's old but works very well). It had it's own driver/firmware back in the day (windows Vista/7). Then Razer released the Synapse 2.0 Cloud based driver/software. IMO is crap.

So on hunch, I found and installed the legacy driver/software package and installed that. Which is what I did after the clean install. With the FCU is set up sleep mode to it's defaults and sleep mode worked great. In device manager it showed an unknown device with yellow triangle. Investigating that, it turns out to be the legacy driver....so I went and got the Synapse 2.0 driver/software and left the sleep mode settings from clean install. That is when I had my first and only BSOD with this clean install.

Since reverting back to the legacy driver.....auto sleepmode seems to be working fine. It's only been 3-4 hours and 2 triggers for coming out of sleep mode but all seems OK for the moment.