[SOLVED] BSOD Hal.dll+686e0

[FMA2000]

Hi,this is my problem: I have checked all days many BSOD errors and I can't find problem,wherever the cause is hal.dll (686e0) and ntoskrnl.dll (259c4b). Here's my computer description.

· OS - Windows 10, 8.1, 8, 7, Vista ?
Windows 10


· x86 (32-bit) or x64 ?
x64


· What was original installed OS on system?
Windows 10 Home


· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
Full retail


· Age of system (hardware)
I don't know


· Age of OS installation - have you re-installed the OS?
Never re-installed

· CPU
Intel Core I7-7500U CPU 2,70Ghz-2901 Mhz-2 core-4 logic processors


· Video Card
AMD Radeon


· MotherBoard - (if NOT a laptop)
HP 832B on a laptop


· Power Supply - brand & wattage (if laptop, skip this one)
-


· System Manufacturer
Home built


· Exact model number (if laptop, check label on bottom)
I don't know


· Laptop or Desktop?
Laptop

Thanks.

 

[Sysnative Windows Update]

Hello and welcome to Sysnative!

GSmartControl
Follow the instructions below to test your hard drive health with GSmartControl:

• Download GSmartControl and save it on your Desktop;
• Execute gsmartcontrol.exe; Let the install complete and launch the programme.
• Identify your drive in the list, and double-click on it to bring up it's window (usually you'll find your drive by it's size or it's brand name);
• Go in the Perform Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
• Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply;
• Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
  
  

 

[FMA2000]

Here's the screenshot.

 

[Sysnative Windows Update]

Unfortunately, it appears that your HDD is failing. Please backup your data immediately and replace the drive as soon as you can.

 

[FMA2000]

Unfortunately, she is wrong. I went to see the status of the internal HDD with CrystalDiskInfo and as you can see, according to how the computer says, the state of the disk is good. If it were as he says, surely CrystalDiskInfo would have confirmed this hypothesis. Unfortunately I'm not from your country, otherwise I would have already called a real technical support of this country to immediately solve this problem as you suggested, but as you can see I'm in another continent. Regards.

 

[Sysnative Windows Update]

Actually, this utility does confirm my suspicions that you have reallocated sectors which is bad and means that your HDD is failing.

 

[FMA2000]

The HDD is NOT failing, at the moment. Regards.

 

[Sysnative Windows Update]

I disagree. In any case. Please backup your data. You are welcome to run another diagnostic test. As you have a Seagate HDD, the official SeaTools one is good as well).

 

[FMA2000]

Seagate is worst as more HDD internals. SSD is good but not exist in Europe. And repeat: my internal HDD is NOT failing, for the moment. Thanks and regards!

 

[Patrick]

Due to the 0x133 bugcheck it'd be beneficial to have a kernel dump as opposed to a small capture. You can find it in C:\Windows named MEMORY.DMP. Upload wherever you'd link and paste the link here.

 

[FMA2000]

Here's a info from MEMORY.DMP. I can't upload a filedump because is too big (888 MB). Therefore has a info from NirSoft BlueScreenView:


A problem has been detected and Windows has been shut down to prevent damage
to your computer.


The problem seems to be caused by the following file: hal.dll


Technical Information:
*** STOP: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff80228745380,
0x0000000000000000)
*** hal.dll - Address 0xfffff80228cda6e0 base at 0xfffff80228c72000 DateStamp
0xfbe06e6e

 

[Patrick]

Right, as I said, you'll have to upload it somewhere else and then paste the link here. Any drive site works great.

 

[FMA2000]

Unfortunately, i can't upload a Minidump file, because due of restriction file. Anyway thanks.

Here's the Nirsoft BlueScreenView screenshot of the last BSOD. Good Night.

 

[Patrick]

because due of restriction file

Can you explain what you mean?

 

[FMA2000]

Inaccessible file! I have tried to zipped this file but this is Access denied.

 

[Sysnative Windows Update]

You need to copy it to your Desktop first, then zip it.

 

[Patrick]

You need to copy it to your Desktop first, then zip it.

This, it's because you have insufficient permissions when attempting to zip it directly from the C:\ directory itself.

 

[FMA2000]

That's the Minidump file!

 

[Patrick]

Not what I asked for.

You can find it in C:\Windows named MEMORY.DMP

 

[axe0]

Hi FMA2000,

Please do the following:
- copy the file memory.dmp in C:\Windows to your desktop,
- upload this file to onedrive, google drive, dropbox or any other similar service you prefer,
- ceate a share link and
- post the share link in your next post.