BSODs, computer waking up from sleep immediately. Already spent a lot of time troubleshooting, need help.

Toggle sidebar Toggle sidebar
SchuetzenHaus

SchuetzenHaus

Prominent
Apr 20, 2017
21
0
510
Hi there.

So my computer's been a bizarre mess, and after extensive troubleshooting I'm at a loss. I would absolutely appreciate the help.

Specs -
■ CPU - Intel i7-6700k (No OC)
■ Mobo - ASRock Z170 Extreme7+
■ GPU - 2x EVGA GeForce GTX 970 (Sli)
■ RAM - CORSAIR Vengeance LPX 16GB (2 x 8GB)
■ PSU - EVGA SuperNOVA 1000 G2 120-G2-1000-XR 80+ GOLD 1000W
■ SSD - SAMSUNG 850 EVO 500gb
■ NIC Card - TP-Link Archer T9E AC1900
■ Case - Thermaltake Level 10 GT
■ Cooler - CORSAIR Hydro Series H105
■ OS - Windows 10
■ Extra drives - 2 HDD's, one 2tb one 4tb

Symptoms -

The occasional BSOD
- no error code provided
- Not very consistent. will happen randomly, though seems to happen way less during gaming
- Seems to happen more during long conversations with Skype, but that might very well be

Hard freeze - This one is much rarer, but has happened. Only fix is hard reset via power button

Waking up from Sleep immediately
- When the computer goes to sleep, the system will shut down for a second, then immediately boot back up

Waking up from Shut down immediately
- If I choose to shut down the PC from the menu, then the same issue as the sleep. The system will shut down for about a second, then boot right back up.

- it looks like even hitting the power button once while the computer is awake it'll shut down...then boot back up.

One of my drives will disconnect for 1/2 a second, then connect again. Windows gives me the notification sounds.

Troubleshooting I've already done:

Sleep issue -
I've gone though every single post about the sleep issue before. I've checked the restart times for update, I've checked seeing which devices would wake up the computer from sleep. I've also done the sleep test with every single USB device unplugged. If I check event viewer, it'll give me the notification that something woke my computer up, but the source is unknown.

I tried unplugging the machine completely from power and holding the power button for a few seconds, a suggestion I heard somewhere. The lights did flicker for a couple seconds. Did not fix anything though.

I've done a fresh install of Windows 10, issue still persists.

After a BSOD here are the Crash reports from WhoCrashed: (Hopefully this formatting works)
Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Tue 2017-04-04 7:51:42 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\040417-8953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x1A (0x4477, 0xDEADBF07, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 2017-04-04 7:51:42 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: bcmwl63a.sys (bcmwl63a+0x17704F)
Bugcheck code: 0x1A (0x4477, 0xDEADBF07, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\drivers\bcmwl63a.sys
product: Broadcom WiFi Driver wireless driver
company: Broadcom Corp
description: Broadcom WiFi Driver wireless driver
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bcmwl63a.sys (Broadcom WiFi Driver wireless driver, Broadcom Corp).
Google query: Broadcom Corp MEMORY_MANAGEMENT



On Sat 2017-04-01 2:16:54 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\040117-10078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x1A (0x4477, 0xDEADBF07, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I've downloaded the most recent Broadcom driver as seen in the crash report, tried to troubleshoot, there doesn't appear to be anything wrong. I've also checked for the drivers for my NIC, no issues there either. My wireless has been fine, no issues.

I found someone online with the EXACT same crash log as me, although it appears there was no help. Awesome

No unknown devices under device manager

I've flashed to the latest BIOS version

I've downloaded Mobo Drivers

I've run temperature checks, nothing over 60.

Memtest86 - no errors

Ran hard drive diagnostics. One one of my drives my computer did a hard freeze twice, however on the 3rd scan it ran fine, showed no errors. No errors on all drives.

I've made sure that all connections inside case were secure

I've replaced the SATA cables with my drives in case the previous cables were faulty.

-

It seems at this point that my ability to google and troubleshoot are done. Can anyone maybe help?

I have a weird feeling that perhaps the PSU might be faulty, previous experiences taught me that when a series of issues come together that don't make sense, it was the PSU. Though, I don't really have a way to prove it obviously 😛

Please let me know if there's any more information I can provide.
 
Sort by date Sort by votes
memory management error code 0x4477 is not documented.
I would just update your : Broadcom 802.11 Network Adapter wireless driver
and see if that helps.

here is the list of codes:
https://msdn.microsoft.com/en-us/library/windows/hardware/ff557391(v=vs.85).aspx

a bugcheck from memory managemnet means that the contents of the memory is not what was expected. it does not mean that you have a problem with the physical ram (although that can cause the data to be incorrect)
 
Upvote 0 Downvote


I'll triple check the connectors, just to be sure. I'll also check for XMP, thanks for the suggestion.
 
Upvote 0 Downvote


Thanks for the suggestion, but I have already downloaded latest broadcom drivers. Did not fix issues.
 
Upvote 0 Downvote
Want to add an edit, it looks like choosing to "shut down" the computer via the OS causes the same issue as the sleep. Where the system will shut down fully for maybe 1 second, but then boot up again right after. Only way I can reliably keep the machine off is by holding the power button.


I tried unplugging the machine completely from power and holding the power button for a few seconds, a suggestion I heard somewhere. The lights did flicker for a couple seconds. Did not fix anything though.
 
Upvote 0 Downvote
change the memory dump type to kernel, run cmd.exe as an admin then run
verifier.exe /all /standard

and reboot. put the next bugcheck binary c:\windows\memory.dmp on a cloud server like microsoft one drive, share the file for public access and post a link.

be sure to know how to get into safe mode to turn off verifier if it bugchecks during the boot process. when done testing, you have to turn off verifier.exe via
verifier.exe /reset
or your machine will run slowly until you do.
 
Upvote 0 Downvote


Hi there! Here is the file - https://drive.google.com/open?id=0B2AyLX1Ez30EQzJkSEJXcGpBaFU

Please let me know if it's done correctly.

if it's worth anything, I was getting BSOD's during the reboots (no error code). Did end up having to boot to safe mode to disable.
 
Upvote 0 Downvote


Yes, XMP is enabled. Double checked bios settings for speed and timing, all seems up to snuff.

And yes, Mobo is fully plugged in to the PSU.
 
Upvote 0 Downvote
bugcheck shown in the memory dump was caused by:
Asrock V Drive driver
\SystemRoot\system32\DRIVERS\AsrVDrive.sys Mon Oct 1 01:21:03 2012

looks like windows plug and play called the raid adapter which talked to asrvdrive.sys which used a bad memory address that lead to the bugcheck.

I would remove the driver or look for a update if you actually need it.

(the memory address used looked like a proper kernel mode address, so i guess it could also be a bug in your storage driver
Asmedia 106x SATA Host Controller Driver
\SystemRoot\System32\drivers\asstahci64.sys Tue Jun 16 20:36:23 2015

if the removing the asrock v drive drive does not fix the problem, you might put your drive on a the second sata controller (if you are not running raid)
(or see if you can get a driver update for the asmedia controller)
 
Upvote 0 Downvote


Alright well this gets interesting.

Removed suggested driver (I'm not attempting to run RAID), tried to put computer to sleep, booted up again immediately. Issue still persists. So I went to go change the physical SATA cable of my SSD to a different SATA slot on my board. BSOD, "INACCESSIBLE_BOOT_DEVICE". Huh, okay, so I try a different Sata slot. Same thing. Then I tried another. Same thing. So it'll only boot if it's in one specific SATA Slot.

I went back and re-did your initial post and created a new memory dump. Here is the link - https://drive.google.com/open?id=0B2AyLX1Ez30EaGxiUUp2eDc5Tmc
Interestingly enough, I did not BSOD on the restart this time, so deleting the driver did have some kind of effect.

I don't know if it means anything, but in Device Manager under Storage controllers, I have 2 "Asmedia 106x SATA Controller"s, and both have an exclamation mark. Here is a screenshot of that - https://puu.sh/vvuLz/7a6473ea14.png
It seems each one is connected to one of my HDD's. If I disable one, then a HDD disappears.

EDIT:
So I tried turning my PC off, and then BSOD. "DRIVER_VERIFIER_DETECTED_VIOLATION". That being said, it booted up fine, and I tried replicating the error. Couldn't get it to happen again. Seemed like a one time thing. Here is a crash report from that though.
On Tue 4/25/2017 1:32:50 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\042517-5218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xC4 (0xF5, 0x0, 0xFFFFC802420CDDC0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver passed a NULL handle to ObReferenceObjectByHandle. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 4/25/2017 1:32:50 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase!GreCreateRectRgn+0x4B4)
Bugcheck code: 0xC4 (0xF5, 0x0, 0xFFFFC802420CDDC0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Base Win32k Kernel Driver
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver passed a NULL handle to ObReferenceObjectByHandle. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
 
Upvote 0 Downvote
i would need access to the new memory dumps to see which driver is causing the problem.
it looks like a error code for a bug in a file filter driver. (a driver trying to free a memory address of zero, (a common bug))

you can start cmd.exe as an admin (or powershell) and run the command

fltmc.exe
it will list out all of your file filters

here is the list that my machine shows:

PS C:\WINDOWS\system32> fltmc

Filter Name Num Instances Altitude Frame
------------------------------ ------------- ------------ -----
WdFilter 5 328010 0
storqosflt 0 244000 0
wcifs 1 189900 0
FileCrypt 0 141100 0
luafv 1 135000 0
npsvctrig 1 46000 0
Wof 4 40700 0
FileInfo 5 40500 0
PS C:\WINDOWS\system32>
 
Upvote 0 Downvote


New memory dump - https://drive.google.com/file/d/0B2AyLX1Ez30EaGxiUUp2eDc5Tmc/view

Here are the results of the filters on my PC

wcnfs 0 409900 0
WdFilter 4 328010 0
storqosflt 0 244000 0
wcifs 1 189900 0
FileCrypt 0 141100 0
luafv 1 135000 0
npsvctrig 1 46000 0
FileInfo 4 45000 0
Wof 2 40700 0
 
Upvote 0 Downvote
you might need to just boot into safe mode, turn off verifier.exe via:
verifier.exe /reset
then boot into windows and remove the asrvdrive.sys
if it comes back it will be in the hidden driverstore and you might have to use this method to remove it.
https://technet.microsoft.com/en-us/library/cc730875(v=ws.11).aspx
------
the memory dump was from sat april 22
and just shows a bugcheck caused by AsrVDrive.sys
Image path: \SystemRoot\system32\DRIVERS\AsrVDrive.sys
Timestamp: Mon Oct 1 01:21:03 2012


I think this is a old bugcheck or the same as before.

the bugcheck was 5 seconds into the boot, and shows that asrvdrive is having problems trying to get resources and having a problem with windows plug and play.

you just need to get asrvdrive uninstalled. then turn off verifier.exe when done testing




--------


 
Upvote 0 Downvote
Hmm, so rebooted a bunch, Asrvdrive.sys does not come back, it's gone. I checked the link you provided, and using it's methods it didn't even recognize it. It does recognize "Asmedia Technology storage controllers though..
Published name : oem17.inf
Driver package provider : Asmedia Technology
Class : Storage controllers
Driver date and version : 06/17/2015 3.1.6.0
Signer name : Microsoft Windows Hardware Compatibility Publisher

Don't know if that's responsible for anything

I ran the verifier.exe /all /standard, rebooted, no BSOD this time, and it looks like no MEMORY.dmp was made at all. Double checked to see if the memory dump type was still kernel, and yeah everything is good there.

Issues still persist though, immediate reboot on sleep or shut down.

 
Upvote 0 Downvote
Additional little update, it looks like even hitting the power button once while the computer is awake it'll shut down...then boot back up. Don't know if that helps add anything.
 
Upvote 0 Downvote
try putting the output in your documents folder
or don't specify the output and just copy the report from the default location to your document directory.
you can view the report in the default location if you use a browser. You just can not open the file in the default directory using write permissions.



 
Upvote 0 Downvote
Thanks. So it looks like a lot of the errors are USB related, however one of the main steps I did try was trying to put the computer to sleep with nothing plugged in, so I don't know how helpful this test was. Here was the report if you want to take a look - https://drive.google.com/open?id=0B2AyLX1Ez30ESDI3RkFvdi1TXzA

has a lot of warnings that might be useful though.

 
Upvote 0 Downvote
if you resolved the earlier error with the AsrVDrive.sys messing up the power irps
you should force a kernel memory dump using the keyboard and put the new memory dump on a server and I will take a look at it to see if power irps are still being blocked.

in the old memory dump all of the blocked requests were in the high def audio

 
Upvote 0 Downvote
https://drive.google.com/open?id=0B2AyLX1Ez30EUFp2b253ZkxLWEE - Here you go



 
Upvote 0 Downvote
Asmedia 106x SATA Host Controller Driver
is failing to load

InstancePath is "PCI\VEN_1B21&DEV_0612&SUBSYS_06121849&REV_02\6&cd1956b&0&002800E2"
ServiceName is "asstahci64"
assume it is for this chip on your motherboard:
4 x SATA3 6.0 Gb/s Connectors by ASMedia ASM1061, support NCQ, AHCI and Hot Plug
(the driver needs to match your motherboard version and your bios version)

you should confirm you have the version that came with your motherboard.
I would install it while verifier.exe is off, then turn it back on if you want to continue testing.


if you don't use the this second controller you might disable it in bios if you can then you will not hit this bug.

verifier.exe /reset will turn off verifier so you don't get a bugcheck
(if found a null pointer being used and called the bugcheck)
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom