What's new Search

Recent content by lobstergy

L
[SOLVED] BSOD Random occur, mostly hal.dll ntoskrnl.exe error, Win8.1proWMC x64 update latest.

Alright, thank you, Patrick. Your help has been more than appreciated!!!
- lobstergy
- Post #14
- Dec 5, 2014
- Forum: BSOD Crashes, Kernel Debugging
L
[SOLVED] BSOD Random occur, mostly hal.dll ntoskrnl.exe error, Win8.1proWMC x64 update latest.

Er,how can I say, there are some misunderstanding here. Normally run it's ok, butI still got BSOD when verifier turned on, just I can login windows and last longernow. So, I still need help, please check the latest dump file above, thanks.
- lobstergy
- Post #12
- Dec 5, 2014
- Forum: BSOD Crashes, Kernel Debugging
L
[SOLVED] BSOD Random occur, mostly hal.dll ntoskrnl.exe error, Win8.1proWMC x64 update latest.

Sorry for feedback late. You're absolutely right,ESET is the culprit. After replace firewall back to windows, BSOD disappear with verifier turned on. But I really don't used to WFC, as zone alarm and comodo firewall as well, everything different, uncomfortable. Besides I got ESET two years...
- lobstergy
- Post #11
- Dec 4, 2014
- Forum: BSOD Crashes, Kernel Debugging
L
[SOLVED] BSOD Random occur, mostly hal.dll ntoskrnl.exe error, Win8.1proWMC x64 update latest.

After another round BSOD, locate program name pcmaster with pcmastercoredrv.sys wrong, uninstall it. Finally I reboot into windows 8.1 with verifier turn on which is very exciting. Unfortunately, it's last only few minutes when login windows and got BSOD again. Several times as the same. The...
- lobstergy
- Post #9
- Dec 2, 2014
- Forum: BSOD Crashes, Kernel Debugging
L
[SOLVED] BSOD Random occur, mostly hal.dll ntoskrnl.exe error, Win8.1proWMC x64 update latest.

Thanks for the clear explanation Patric. I do right away followed by your instruction to break driver, then do verifier again. Then got BSOD again, restore recovery and report dump file, Please check. Thanks This time, uim_vimx64.sys appear, bluescreen show that it's from paragon, should I...
- lobstergy
- Post #7
- Dec 1, 2014
- Forum: BSOD Crashes, Kernel Debugging
L
[SOLVED] BSOD Random occur, mostly hal.dll ntoskrnl.exe error, Win8.1proWMC x64 update latest.

1. There are 4 SeLow_x64.* files remain partition c, I'd deleted them all to recycle bin, do I need restore them and rename all to SeLow_x64.bak? 2.ESET refer to ESET smart security 7, right? Sorry, I don't understand what the "break thedriver for now and don't touch ESET." mean? How to break...
- lobstergy
- Post #5
- Dec 1, 2014
- Forum: BSOD Crashes, Kernel Debugging
L
[SOLVED] BSOD Random occur, mostly hal.dll ntoskrnl.exe error, Win8.1proWMC x64 update latest.

Hi Patric, Thanks for such quick responding. I have already uninstalled Softether VPN software, uninstall softether vpn driver. after this,selow_x64 still remain in c disk, then I use everything.exe search and del all selow_x64.* (inf, pnf, sys) files. I've just meant to do verifier again to...
- lobstergy
- Post #3
- Dec 1, 2014
- Forum: BSOD Crashes, Kernel Debugging
L
[SOLVED] BSOD Random occur, mostly hal.dll ntoskrnl.exe error, Win8.1proWMC x64 update latest.

Hi Sysnative experts, I'm happy to find you guy's website after I'd been desperately suffered random BSOD since last week. I'd try "blueScreenView" & "WinDbg" with minidump files to locate error, mostly cause by hal.dll, ntoskrnl.exe, but don't know how to fix them. Hope some experts from...
- lobstergy
- Thread
- Dec 1, 2014
- Replies: 14
- Forum: BSOD Crashes, Kernel Debugging

lobstergy