New
#31
Will do
OK, here we go again, this time (luckily) there's a minidump...
==================================================
Dump File : 071912-16723-01.dmp
Crash Time : 7/19/2012 6:24:07 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff960`0018d5ca
Parameter 3 : fffff880`0b4f9f90
Parameter 4 : 00000000`00000000
Caused By Driver : peauth.sys
Caused By Address : peauth.sys+3bb48e0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump1\071912-16723-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 301,939
==================================================
They just don't wanna give up! They are starting a war that I am gonna win(even with my beginner experiance!) lol.
Well atleast there is a .dmp file this time. Do you have any chat programs on your computer?
Run SFC /SCANNOW Command - System File Checker
and then Disk Check
Last edited by HonorGamer; 19 Jul 2012 at 11:37. Reason: Wrong link to chkdsk
Also please find where this file is located on your C drive: icq.exe
Do not launch it, just give me the path to it.
Chat programs - well, ICQ and Skype.
SFC and CHKDSK didn't show any problems whatsoever.
I'm 99% certain there's no malware on the laptop - unless it's something super new and exclusive but I doubt it LOL
You may be right when you said earlier that it's some kind of a hardware problem...
The weird thing is that the BSODs always show a different reason, there's no consistency at all...
The ICQ.exe location is D:\Program Files (x86)\ICQ7.0
Try unisntalling ICQ because this one pointed towards ICQ which is kinda odd, but go ahead and give it a go
OK, I'll do that and we'll see what happens... Even though... ICQ? Really? LOL But I'm desperate enough so let me do this now.
On a related note, maybe I should upgrade to the latest ICQ version instead?
That could work to, and honestly im desperate to, I've ran out of explanations and everything. If we don't figure this out soon I'll get someone from the BSOD team to take a look.
Was there any other files with this .dmp file?