New
#81
Thx Axe0!!
Thx Axe0!!
I guess we can't really blame the RAM? it took 16 hours.
Attachment 52821
the only thing I can wait for now is a BSOD with HDD disconnected.. that means we're out of options.
Please install the Realtek network driver again.
It is the same version, but it looks like there are some updates compared with the updates date and the date of your driver.
BSOD randomly browsing internet; ntoskrnl.exe - Page 2 - Windows 10 Forums
Attachment 52831
Driver Reference Table - rt640x64.sys
Are there things you can do that do not require internet?Code:fffff801`9836b4e8 fffff801`11f7ae7eUnable to load image rt640x64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for rt640x64.sys *** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys rt640x64+0x1ae7e 0: kd> lmvm rt640x64 start end module name fffff801`11f60000 fffff801`12045000 rt640x64 T (no symbols) Loaded symbol image file: rt640x64.sys Image path: rt640x64.sys Image name: rt640x64.sys Timestamp: Thu Oct 01 12:34:33 2015 (560D0C39) CheckSum: 000F03D5 ImageSize: 000E5000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
I'd like you to try to replicate the crash in safe mode, it makes it easier to find out if the problem is hardware related.
Safe Mode - Start Windows 10 in - Windows 10 Forums
Please scan your system files, just to make sure there is no problem according to the test.
NOTE: this test is NOT 100%, even if it says no problem is detected it is possible there is a problem.
Please try following:
- Open an admin command prompt
- Copy/paste "sfc/scannow" (without quotes) and press enter
- When it finished reboot your system
- Open again an admin command prompt
- Enter sfc/scannow again
If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.
I deleted realtek, rebooted, reinstalled.
SFC found errors "which it couldn't fix" when I opened it up second time. Log included.
http://www.filedropper.com/cbs
An image file is corrupted.
I however do recommend to get this problem solved, even a picture in the system files could cause many problems.
Please try following command in admin command promptCode:2015-12-09 23:02:57, Info CSI 0000559b [SR] Cannot repair member file [l:106{53}]"MicrosoftEdgeSquare44x44.scale-125_contrast-white.png" of Microsoft-Windows-MicrosoftEdge, Version = 10.0.10240.16603, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-12-09 23:02:57, Info CSI 0000559c [SR] This component was referenced by [l:158{79}]"Package_816_for_KB3116869~31bf3856ad364e35~amd64~~10.0.1.2.3116869-2083_neutral" 2015-12-09 23:02:58, Info CSI 0000559d Hashes for file member \??\C:\WINDOWS\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\Assets\MicrosoftEdgeSquare44x44.scale-125_contrast-white.png do not match actual file [l:106{53}]"MicrosoftEdgeSquare44x44.scale-125_contrast-white.png" : Found: {l:32 b:d88KqKptc/J61/qkL3yadqaJpg10SD+WBQ3BzArbiMA=} Expected: {l:32 b:VR3+fshmsSxNARCI3MhFhrszJNS2j5z4HNbWiTeYEjU=} 2015-12-09 23:02:58, Info CSI 0000559e Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-microsoftedge_31bf3856ad364e35_10.0.10240.16603_none_193be55a8ac9469d\MicrosoftEdgeSquare44x44.scale-125_contrast-white.png do not match actual file [l:106{53}]"MicrosoftEdgeSquare44x44.scale-125_contrast-white.png" : Found: {l:32 b:d88KqKptc/J61/qkL3yadqaJpg10SD+WBQ3BzArbiMA=} Expected: {l:32 b:VR3+fshmsSxNARCI3MhFhrszJNS2j5z4HNbWiTeYEjU=} 2015-12-09 23:02:58, Info CSI 0000559f [SR] Could not reproject corrupted file [ml:142{71},l:140{70}]"\??\C:\WINDOWS\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\Assets"\[l:106{53}]"MicrosoftEdgeSquare44x44.scale-125_contrast-white.png"; source file in store is also corrupted
If there are problems with RestoreHealth, please follow step 6 or 7 (depending on the file you have from the download) from the tutorial DISM - Repair Windows 10 Image - TutorialCode:DISM /Online /Cleanup-Image /RestoreHealth
Updated the network driver; fixed that image file; unplugged external HDD.
No BSODs since I unplugged HDD drive.
Is there any test that I could do to see if my USB 3.0 ports are screwed?
Can I test the drive somehow to see if it's really the cause?
I kinda need that thing connected, but it seems to be the cause.
From post 32: BSOD randomly browsing internet; ntoskrnl.exe - Page 4 - Windows 10 Forums
In this case, 'each device' is the HDD. Connect the HDD to different USB and see if the system crashes.I'm not sure if it will be a 100% possible, but try to connect each device on another USB port and see if that helps.
If the system crashes in different USB's, the connection of the HDD is faulty, in that case get another HDD and backup the data from the HDD with the faulty connection.
sadly I got two more BSODs, but both happened when something was physically plugged into one of the USB 3.0 ports.
"Physically" because one time it was an "ejected" USB HDD (you know, the one I considered troublemaker? the system crashed on shutdown).
The other - a 3.0 hub was connected to that port, but no devices were connected to the hub itself. I was playing some games.
Could you take a look?
Attachment 53709
Oh, and I can't connect the HDD to anything else than a USB 3.0 port (which I have two...), because it doesn't work properly, it starts, speeds up, clicks, stops, and speeds up again... ad infinitum, making those annoying clicking noises.
No dump is present, recently done a cleanup?
Does a crash occur when you don't use that 3.0 USB port?
Oh, right. My windows 10 applied a long, painful update and some things reverted to default afterwards, so I guess dumps went away... :/
So far, no - the BSODs didn't happen when that particular port was disconnected, but it just might be my wishful thinking.
I'll report back once a BSOD hits - and keep that port empty, of course.