First Blue Screen

[tw33k]

Can someone take a look at this for me and give me details please?
View attachment 80401

 

[ttran]

Hi there
The minidump file pointed stop error code 3B, which I think the usual causes are system services, device drivers, graphic drivers...or might be memory.
I realized that you have some old drivers that can be updated:

PFC027   PFC027.SYS   Tue Dec 05 10:34:25 2006 (4574E8C1)
jraid    jraid.sys    Tue Nov 04 09:20:09 2008 (490FB159)
wdcsam64 wdcsam64.sys Wed Apr 16 15:39:08 2008 (4805BB2C)

I'm thinking about malware stuff, can you run this free scan:
Malwarebytes

bugcheck

BugCheck 3B, {80000003, fffff88001559100, fffff8800a40fa00, 0}
Probably caused by : cng.sys ( cng!CngCreateProcessNotifyRoutine+f0 )
Followup: MachineOwner
---------

Regard

 

[tw33k]

Thanks but I use the full version of Malwarebytes along with other software. No malware here

 

[Tews]

Tweek.. while your .dmp file blames cng.sys as the faulting module(Cng.sys Kernel Cryptography, Next Generation) It is unlikely that it is in and of its self the sole culprit. After a quick look on google, there seems to be quite a few instances of malware that are disguising themselves as cng.sys. Best bet, do a deep and through scan, or restore a backup image of the OS... Good luck...

EDIT: oops... you're too quick...

 

[tw33k]

Hmmm...this is a new install (maybe a week)

 

[ttran]

humm...please update those drivers..you can run your full malware test again. Sometime Bsods occur and it will not appear again...may be you are fine now
~Tuan

 

[Capt.Jack Sparrow]

Hello !!

Since it's pointing to System Driver most probably that won't be an issue some other rogue driver might be causing it. If you get again you can enable the Driver verifier and find what driver is causing it.

Good Luck,
Captain

 

[tw33k]

Just got another one. I think it has something to do with my graphics because both happened while trying to watch video. Can someone have a look for me and let me know.
View attachment 82638

 

[ttran]

You are right, eventhough your graphic card driver is not blamed directly, it is process running at the time your computer crash. atieclxx.exe is a process from ATI Controlpanel by Ati and part of ATi Graphiccard drivers. This task is responsible for a hardware piece in your system. It offers additional configuration options and support for this device

I would suggest you to re-install your graphic card driver (remove all trace of older version first as well as Catalyst Control Center)

This should help you when to uninstall ATi graphic drivers. I've done a bit research and found out that atieclxx.exe is hard to remove even after you uninstall the driver.
http://forums.amd.com/game/messageview.cfm?catid=260&threadid=121536
or this:
http://morganramsay.blogspot.com/2009/12/removing-atieclxxexe-and-atiesrxxexe.html
Then, please run this free video stress test:
FurMark

BugCheck 50, {ffffffffffffff91, 1, fffff80002e14ea3, 0}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------
PROCESS_NAME:  atieclxx.exe

Good luck friend!
Tuan

 

[tw33k]

Thanks mate

 

[ttran]

Thanks mate

My pleasure! BSOD is annoying

 

[tw33k]

This one happened just now while I was outside. This time I wasn't doing anything so don't know where it came from. It's really strange because before these 3, I hadn't had a blue screen since I first installed Windows 7 over a year ago.

View attachment 83065

UPDATE: 2 more straight away. Now it's annoying me. I'm sure my drivers are up to date. Maybe I need to go back to an older version (?)

View attachment 83067

 

[ttran]

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION

Usual causes: System service, Device driver, graphics driver, ?memory
STOP 0x000000C2: BAD_POOL_CALLER

Usual causes: Device driver, ?Memory

Please update these drivers my friend:

wdcsam64 wdcsam64.sys Wed Apr 16 15:39:08 2008 (4805BB2C) [COLOR=Blue]Western Digital External Drive RAID Manager[/COLOR]
PFC027   PFC027.SYS   Tue Dec 05 10:34:25 2006 (4574E8C1) [COLOR=Blue]PFC027 -                              PixArt Imaging Probably a webcam[/COLOR]
gdrv     gdrv.sys     Sat Dec 06 07:57:14 2008 (4939CDEA) [COLOR=Blue]Gigabyte's Dynamic Energy Saver Advanced  program
[/COLOR]

RtHDMIVX RtHDMIVX.sys Thu Dec 25 16:30:47 2008 (495352C7)

I guess it belong to Realtek audio driver, please update it

Also, download third party called memtestx86, burn it to CD using http://isorecorder.alexfeinman.com/W7.htm , and let it run for at least 5 passes.

Scan whole computer with: Malwarebytes
Run: http://www.sevenforums.com/tutorials/433-disk-check.html

BugCheck 3B, {c000001d, fffff80003390e9d, fffff8800a876e20, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------
BugCheck C2, {7, 1097, 5110409, fffff8a02354e3d0}

GetPointerFromAddress: unable to read from fffff800032b90e0
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCreate+253e )

Followup: MachineOwner
---------

 

[Capt.Jack Sparrow]

Hello !!

Just to quick suggestion make sure you update PFC027.SYS belongs to PixArt Imaging Inc Driver. It's dated 2006. Most of the times old drivers used to cause BSOD. If you didn't find the update uninstall it and rename the Driver from %systemroot%\Windows\System32\drivers. Also update your RAID Driver jraid.sys it's dated 2008.

Good Luck,
Captain

 

[tw33k]

PFC027.SYS is my old web cam driver which I don't use so I got rid of it. The JMicron driver is now updated. Thanks mate. I hope that ends these crashes.