BSOD screen

Closed
kenshiro078 Posts 1 Registration date Monday December 5, 2016 Status Member Last seen December 5, 2016 - Dec 5, 2016 at 09:06 AM
Ambucias Posts 47310 Registration date Monday February 1, 2010 Status Moderator Last seen February 15, 2023 - Dec 6, 2016 at 05:26 PM
hi guys i have a problem with my computer, the computer show me 2 blue screens... and i dont know how to fix that problems. anyone could help me? thanks :)


i going to paste the following words:

==================================================
Dump File : 120516-21437-01.dmp
Crash Time : 05-12-2016 01:09:57 a.m.
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`00001200
Parameter 3 : 00000000`00000000
Parameter 4 : fffff901`406c0090
Caused By Driver : hal.dll
Caused By Address : hal.dll+669a
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14e3a0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\120516-21437-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 9600
Dump File Size : 279.880
Dump File Time : 05-12-2016 02:00:57 a.m.
==================================================

==================================================
Dump File : 120416-22984-01.dmp
Crash Time : 04-12-2016 07:44:16 p.m.
Bug Check String :
Bug Check Code : 0x00000139
Parameter 1 : 00000000`00000003
Parameter 2 : fffff801`1f70fba0
Parameter 3 : fffff801`1f70faf8
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14e3a0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14e3a0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\120416-22984-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 9600
Dump File Size : 279.880
Dump File Time : 04-12-2016 07:45:59 p.m.
==================================================
Related:

2 responses

Blocked Profile
Dec 5, 2016 at 04:46 PM
These are generic logs, and are of no value. Besides, the logs are over 6 months old! Did it just happen? If so, get into BIOS and check your time. Correct it and reboot!
0
Ambucias Posts 47310 Registration date Monday February 1, 2010 Status Moderator Last seen February 15, 2023 11,164
Dec 5, 2016 at 05:03 PM
With all due respect sir Mark, the log was produced today.

It seems that the failure comes from ntoskrnl.exe which may be corrupted and should be replace.

In most cases ntoskrnl.exe was blamed because a driver (typically a 3rd party driver) has corrupted the memory space that ntoskrnl.exe considers as it's own. When this happens, ntoskrnl.exe typically finds unknown data (from the 3rd party driver) in it's memory space. At this point the OS panics and throws a BSOD to prevent damage to the system.

That perticular driver is : hal.dll

What do you think ?
0
Blocked Profile
Dec 6, 2016 at 05:16 PM
aH, 12-4. GOTCHA!
0
Ambucias Posts 47310 Registration date Monday February 1, 2010 Status Moderator Last seen February 15, 2023 11,164 > Blocked Profile
Dec 6, 2016 at 05:26 PM
Sir ! I've been hit in the b**t ! Medic !
0