Question BSOD- Cause?

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Toggle sidebar Toggle sidebar
C

csaxon

Prominent
Jun 5, 2018
49
0
530
I have been having massive problems with my Laptop (constant BSOD/ no bootable device errors). The SSD with the OS was replaced a week ago and I had no bluescreens since then. I thought this had fixed the issue. Unfortunately I was forced to install windows 1909 and every time I run a program like a game or virus scan, the fans would go full blast and CPU temps would be high. As before the SSD was changed it didn't do this, I installed windows 1803 from an ISO file. No change. I then tried 1709 as this was the original version that laptop had. No change.


Exactly one day after I installed 1709 a once again got a BSOD. Reliability monitor gave the following data;

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80067a0cb7a, 0xffffdb0978d96950, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: a7d78fee-79bb-4c1f-978f-c146bea9eac6.


The dump file can be found at: https://1drv.ms/u/s!AlM0EaguUEl02kBD_p01E1Gb-9oF?e=1Br6WT


I thought the blue screens had been fixed with the change in SSD as the laptop was fine for a week after the change (apart from high CPU temps). Can someone tell me the cause of the BSOD from the dump file? Is it hardware or software?


Also does anyone know why after changing the SSD/doing a clean install, CPU temps go high when its running something (its fine on idle or light browsing). The temps go about 15C higher now then before I changed SSD's/ did a clean windows install. After I did the clean install whenever the fans start up or turn off, the make a sort of squeak/click noise. I have no idea how this could be related to the clean install, but it started at the same time. It is a dell computer, the clean install removes some of the dell features (e.g. Dell power plan, support assist recovery in the boot menu). I don't know if this affects anything.
 
Sort by date Sort by votes
Well the two processes that have caused your issue so far, Chrome and Realtek, aren't really known for causing issues in and of themselves. As "DELL is offering for me to return it for a refund" I would definitely take them up on that offer, as that model is close to three years old, and for the same money, you would most assuredly be getting a better unit for the same money.

The one you have sounds like a lemon, and as soon as I had Dell offered me my money back for it, I would have taken it in a heartbeat.
 
Upvote 0 Downvote
I ran the dump file through the debugger and got the following information: https://beeriestgarden.htmlpasta.com/

File information:123119-10875-01.dmp (Dec 30 2019 - 11:04:29)
Bugcheck:SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 12 Min(s), and 04 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Upvote 0 Downvote
Chrome didn't cause the error, it was just what was running at time.

Do you use wifi or ethernet?
Jun 27 2017rt640x64.sysRealtek NICDRV 8169 PCIe GBE Family Controller driver

May 12 2019Netwtw04.sysIntel Wireless Wifi Link driver
oh fun, realtek again.... its funny, their nic drivers easy to find, why are sound harder? https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software

dumps aren't blaming drivers, they blame code corruption. It passes memtest... i have seen ram pass memtest and yet after being replaced, BSOD stopped. So maybe try new ram since it has been used on both boards.
 
Upvote 0 Downvote
Hello,

Ethernet is no longer available where I live so I use 4G wifi. Is RAM the only cause of code corruption? I ran the microsoft memory test, DELL memory test and memtest86 and no errors flagged.

I did just update the intel drivers through including the wifi (trying to see if updating all the drivers will fix high temps, but no change so far), I can roll it back. Any advice for Realtek? I've downloaded the driver from microsoft, from dell and from realtek itself and still get the crackling noise. It did this when I've first got the computer but went away, the crackles came back with clean install.
 
Upvote 0 Downvote
It could be a driver but its not showing itself in the dumps. And I already know why you don't want to run verifer, so until a driver shows its face, all we can do is replace what you have or wait.

only drivers that should affect temps are chipset drivers. I would think.

Try installing this - https://downloadcenter.intel.com/product/67496/Intel-Management-Engine-Interface-Intel-MEI- , your version is from January.

you have 1 lot of drivers that I don't trust, and you might be surprised what they are
Dec 06 2019nvlddmkm.sysNvidia Graphics Card driver
I seen loads of PC have problems with nvidia all year... you might try https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/ and put on older drivers, maybe from laptop site? depends on age.
 
Upvote 0 Downvote
Also, last time I didn't run Randomized low resources simulation and DDI compliance checking as the website I was using as I guide said not too. Is this correct?
 
Upvote 0 Downvote
Upvote 0 Downvote
Upvote 0 Downvote
Hi, I ran the dump files through the debugger and got the following information: https://purgativefew.htmlpasta.com/
File information:123119-29359-01.dmp (Dec 31 2019 - 08:39:37)
Bugcheck:DRIVER_VERIFIER_DETECTED_VIOLATION (C4)
Driver warnings:*** WARNING: Unable to verify timestamp for ArgusMonitor.sys
Probably caused by:ArgusMonitor.sys (Process: ArgusMonitor.exe)
Uptime:0 Day(s), 0 Hour(s), 03 Min(s), and 24 Sec(s)

File information:123119-27671-01.dmp (Dec 31 2019 - 08:34:51)
Bugcheck:DRIVER_VERIFIER_DETECTED_VIOLATION (C4)
Driver warnings:*** WARNING: Unable to verify timestamp for ArgusMonitor.sys
Probably caused by:ArgusMonitor.sys (Process: ArgusMonitor.exe)
Uptime:0 Day(s), 0 Hour(s), 15 Min(s), and 38 Sec(s)

File information:123119-26421-01.dmp (Dec 31 2019 - 08:17:54)
Bugcheck:SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (C1)
Probably caused by:ntkrnlmp.exe (Process: svchost.exe)
Uptime:0 Day(s), 0 Hour(s), 05 Min(s), and 44 Sec(s)
This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Upvote 0 Downvote
Haven't disabled it yet, although I have removed it. I plan to download an older version of argus moniter and see if that works. As some of the BSOD I had before I ran verifier were linked to nvidia/realtek, should I keep running it? Also should I test the microsoft drivers too?

Also the BSOD that came back with ntkrnlmp.exe (occured right after I started verifier), was that to do with Argus moniter too?
 
Upvote 0 Downvote
2 of them directly blame the argusmonitor drivers, the 3rd isn't so obvious. I cannot tell if the 3rd mentioning ntkrnlmp is related as it doesn't mention any driver names in stack text.

ntkrnlmp = windows kernel. We think MP = multiprocessor, Gardenman & I have tried to figure that out before

You could keep running it after changing monitor and see if it finds anything else.

No need to test MIcrosoft drivers. Those have been tested by Microsoft already before they were put into OS.
 
Upvote 0 Downvote
Hello,

Still running driver verifier and have new BSOD's. One of thems a complete memory dump not an automatic memory dump. I don't know if it will provide more info. I think ones from a new (old) version of Argus moniter, but one mentioned DELL hardware driver. Does this mean there's a hardware issue too?

https://www.dropbox.com/s/tv7k80yz1bcanx1/010220-26203-01.dmp?dl=0

https://www.dropbox.com/s/7eche73nzbtsolr/010120-44828-01.dmp?dl=0

https://www.dropbox.com/s/4ejvdxjelr3aqnu/123119-40578-01.dmp?dl=0
 
Upvote 0 Downvote
I ran the dump files through the debugger and got the following information: https://aquaticnothing.htmlpasta.com/
File information:010220-26203-01.dmp (Jan 1 2020 - 15:38:30)
Bugcheck:DRIVER_VERIFIER_DETECTED_VIOLATION (C4)
Driver warnings:*** WARNING: Unable to verify timestamp for dcdbas64.sys
Probably caused by:dcdbas64.sys (Process: System)
Uptime:0 Day(s), 8 Hour(s), 01 Min(s), and 33 Sec(s)

File information:010120-44828-01.dmp (Jan 1 2020 - 00:17:54)
Bugcheck:DRIVER_VERIFIER_DETECTED_VIOLATION (C4)
Driver warnings:*** WARNING: Unable to verify timestamp for dcdbas64.sys
Probably caused by:dcdbas64.sys (Process: System)
Uptime:0 Day(s), 14 Hour(s), 29 Min(s), and 59 Sec(s)

File information:123119-40578-01.dmp (Dec 31 2019 - 09:47:01)
Bugcheck:DRIVER_VERIFIER_DETECTED_VIOLATION (C4)
Driver warnings:*** WARNING: Unable to verify timestamp for dcdbas64.sys
Probably caused by:dcdbas64.sys (Process: System)
Uptime:0 Day(s), 0 Hour(s), 12 Min(s), and 32 Sec(s)
This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Upvote 0 Downvote
dcdbas64.sys = Dell System Management Device Driver

I guess its date is rather old
DateDriverDescription
Jun 02 2015dcdbas64.sysHardware Abstraction Dell BASE Device driver (Dell Inc.)
If you unsure how to remove it, run autoruns and use that to stop it startup - https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
although if anything needs to use it, it will be started again. What dell apps have you got in the apps list?
 
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