Had BSOD twice and not sure if it hardware or driver

Hello there, I changed one of my HDDs around two weeks ago and also started to connect external HDD to the front usbs slots daily right after that (It not connected 24/7)

Day after that I got BSOD when I download things in all of my 3 HDDs and web in firefox and have IE10 opened in the background as I do daily for years. suddenly my mouse freeze and I got BSOD that claim it may be driver or hardware, I got it before with other system or maybe even on this one some long time ago and it just was fixed alone after restart as the BOSD stated, probably because win7 auto fix it.


I don't think it the HDD because I have three of the same kind and they all work fine (I just got one BSOD while I do what I always do even at this very moment and 100% of the time I never get BOSD and the system don't look like it under any stress)

Today I suddenly got another one. I let win7 look for fix in the second time and don't know if it fix the issue, it happening very rarely honestly.

I didn't touch the drivers but I know that my mobo have annoying bios so it may have hard time having 3 HDDs with the exact same version

I don't think it the HDDs or my gaming mouse, it may be the external HDD but I don't sure, all HDDs were tested with the last version of Crystal Disk Info and seem fine.

I send the dump files hoping to find someone who can help me debug them and tell me what the issue is


Thanks

We need more information to analyze your logs. Follow Blue Screen of Death (BSOD) Posting Instructions, let the tool run until it has completely finished and then upload the new logs.

Thanks

I read it after I already open the thread and planned to upload it after all my downloads will finish so I can make system restore point before I will run that tool


the files are upload now

Download and run MemTest86+ to test your RAM.

   Note

Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.

Report back with the results from MemTest86+ before following the next step.


Driver Verifier will stress your drivers and cause BSODs if any fail. Follow this tutorial to enable/disable it. Driver Verifier - Enable and Disable

Enable Driver Verifier but only enable these options:
Standard settings and IRP logging step 3.
Don't enable Force Pending I/O Requests

   Warning

Make a System Restore point before enabling Driver Verifier.

   Note

Your system will act very sluggishly while DV is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

Uninstall DaemonTools, a known cause of BSODs.
1. Uninstall Daemon Tools.
2. Download the SPTD standalone installer and follow these steps:
3. Double click the executable to open it
4. Click the button shown below



If the button it is grayed out, as shown in the image, there is no more SPTD installation on your system, and you can just close the window.

Thanks

I know I may sound picky but I really don't like to install these stuff on my pc

WIN7 have a ram testing tool right? won't it be better to use it?



Driver Verifier sound like a dangerous app if it need a restore point... it need installation too?


As for DaemonTools and the SPTD... they on my pc for years and I didn't update them lately, I must them on my pc and I use them daily so delete them is something that I probably won't do



did the test showed that it hardware issue? they didn't hint on the source? they all start happened After I put my new HDD and start to use another external HDD more frequently, not to mention that the pc don't seem to give BOSD under stress of gaming, the BOSD only happened to me today and before ten days ago.


the second time of course was more then enough to hint me that something is wrong but it still happened after 10 days of heavy use on the PC (and I also leave it to work alone where it can run process in idle mod)


there's any hint about what can cause it?


Edit I updated DT, it fix another BSOD case, don't know if it was what I had though

I apologise, for some reason I opened a different log and read a STOP 0x124 which is the hardware error I was advising the fix for. You have a STOP 0x1A which will still require some of the tests above which I'll address in a minute.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa800272e110, ffff, 0}

Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )

Followup: MachineOwner

egozi44 said:

Windows 7 have a ram testing tool right? won't it be better to use it?

No, MemTest86+ is the RAM testing tool to use. You need to run it for at least 8 passes to rule out bad memory.

egozi44 said:

Driver Verifier sound like a dangerous app if it need a restore point... it need installation too?

It's built into Windows, please read the tutorial I linked. You will need to run this if MemTest86+ shows your RAM as good. The Restore Point is just a fail safe.

egozi44 said:

know I may sound picky but I really don't like to install these stuff on my pc

They're tried, tested and trusted tools. You need to run them if you want to pinpoint the cause of your BSODs.

egozi44 said:

As for DaemonTools and the SPTD... they on my pc for years and I didn't update them lately, I must them on my pc and I use them daily so delete them is something that I probably won't do

You don't want to install testing software on your PC but already have installed a known and well documented cause of BSODs and refuse to uninstall it. It's up to you, keep DaemonTools and keep BSODs. Uninstall it.

No, MemTest86+ is the RAM testing tool to use. You need to run it for at least 8 passes to rule out bad memory.

I didn't was able to find the download links, more like I don't know what to download,

can you give me direct link please? and if possible then any portable version can you link me this one instead?

It's built into Windows, please read the tutorial I linked. You will need to run this if MemTest86+ shows your RAM as good. The Restore Point is just a fail safe.

I see, it 100% safe to use for that test and you can delete it setting and history as if you never touch it right?

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa800272e110, ffff, 0}

Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )

Followup: MachineOwner

So what it hint?

MachineOwner mean it one of my drivers or app? or it hardware?

Bugcheck 1A suggests it's either your RAM or a driver. We need to find out which.

The link below is for MemTest86+ bootable ISO. You'll need to create either a DVD or bootable USB with the ISO and boot from that. Remember it needs to run for at least 8 passes.


Download



Driver Verifier is easily disabled as explained in the tutorial linked previously. There are no settings or history to delete, it's a part of Windows.

Did you uninstall DaemonTools yet?

OK after testing it seem to be he memory

I have 16 ram and 4 slots, How can I know what the slot with the defective ram from the pic?


P.S I passed 9 passes but the pic I took was some minute before the 8 pass



I saw that the screened showed more then 22 errors on the "error" section

but only showed 1 red line, does it mean that it just one defective ram card?

The only way to determine which stick is bad is to test each stick one by one in each slot. It's tedious but essential. If all sticks fail in one slot then it's the slot that's bad, if one (or more) fail in all slots then it's the stick that's bad.