BSOD?????

[enyawd]

i dont know what is BSOD technically or what it causes it!

but this morning when i open my pc there was a tit tit tit sound and monitor not responding. ( Twice - rebooting )

but when i removed all the plug inserted in my cpu and return it back and open my pc it works but suddenly it appears with blue screen with technical support something and restarted fine .

and so i ended up here asking for help . (sorry for my cad english)

please help dont want to have stress this x'mas.

WINDOWS 7 - 32 BIT

 

[DeanP]

Can you access to Safe Mode and upload the dump files?

 

[enyawd]

Can you access to Safe Mode and upload the dump files?

there you go. sorry for the late reply

 

[yowanvista]

i dont know what is BSOD technically or what it causes it!

but this morning when i open my pc there was a tit tit tit sound and monitor not responding. ( Twice - rebooting )

but when i removed all the plug inserted in my cpu and return it back and open my pc it works but suddenly it appears with blue screen with technical support something and restarted fine .

and so i ended up here asking for help . (sorry for my cad english)

please help dont want to have stress this x'mas.

WINDOWS 7 - 32 BIT

There is no dump file in your attachment, try the alternative method
http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

 

[enyawd]

Minidump folder empty!.

The link you gave me Attachment 71394 is broken!

 

[enyawd]

please help!

 

[enyawd]

bump!

 

[yowanvista]

The minidump blames KernExplorer64.sys - part of AdAware. Remove AdAware immediately.
Replace it with MSE

Also, it would be a good idea to run a memtest sooner rather than later just incase faulty RAM is the cause.
RAM - Test with Memtest86+

BugCheck 93, {3d38, fffff8a0000018c0, fffff8a0090ab4e0, 1}

Unable to load image \??\C:\Program Files (x86)\Lavasoft\Ad-Aware\KernExplorer64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for KernExplorer64.sys
*** ERROR: Module load completed but symbols could not be loaded for KernExplorer64.sys
Probably caused by : KernExplorer64.sys ( KernExplorer64+1277 )