BSOD happening at Random Times - possibly Video Driver or Malware?

[austin1313]

Need help from someone far wiser than I.

My system is a little long in the tooth, but has been working great for years without ANY issues.
Suddenly last week it started acting unstable and is crashing and BSODing multiple times a day.
There isn't a specific trigger to this, but it seems to happen most often when I'm on the internet w a lot of windows open. Then again, I spend the bulk of my time on the web when I'm on the computer so that could just be coincidental.

At first I thought I might have picked up a bug online somewhere so I checked for Malware.
I didn't see any unusual processes in task mgr, but usually a good first step in troubleshooting is running a few scans. So I ran a scan with Malware Bytes Pro & also w Trend Micro Housecall (Online) and the system came up clean. In addition, I use Eset Nod32 Antivirus and my log doesn't show anything unusual. So my system looks clean.

A few days ago I upgraded my video card to a GeForce GT 730.
I noticed that crashes were more frequently after this, so I downgraded back to my old card. However, the crashes kept happening so I put the new card back in and can't tell if they're any more or less frequent. My computer has ample power to drive the graphics card and I've installed the drivers as per the instruction in the manual without issue.

I also ran a sfc /scannow and windows didn't find any integrity violations.
So I'm stumped since I've never had this kind of issue before.
It either bluescreens and gives me a msg -- or just just restarts to the reboot screen multiple times a day. Below are two recent crash info and I've also attached the DM Log Collector report, as indicated in instructions.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050031
BCP3: 00000000000406F8
BCP4: FFFFF88001838E9C
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\062815-15334-01.dmp
D:\Users\Travis\AppData\Local\Temp\WER-28797-0.sysdata.xml

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80003527306
BCP3: FFFFF8800961FF90
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\062915-15943-01.dmp
D:\Users\Travis\AppData\Local\Temp\WER-31886-0.sysdata.xml

 

[ICIT2LOL]

Hello and welcome Austin sorry for the wait mate just for starters there a few issues and we shall need to work through them in the meantime I would run these (in safe mode where you can) - they don't take long and eliminate something basic or simple.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

http://www.sevenforums.com/tutorials/433-disk-check.html< if necessary include the /f and /r in the command line as per Option2

if no go then these

http://www.superantispyware.com/

http://www.malwarebytes.org/products/malwarebytes_free/

http://www.bleepingcomputer.com/download/adwcleaner/

ADW download from bleeping computerdelete any rubbish found with the malware scans

(with ADW ifyou are running Kaspersky it will throw it up as malware just overrideKaspersky by ignoring it or disabling it for the duration of the scan)

 

[austin1313]

First off, thanks so much for your help!
It's much appreciated and I'm pulling my hair out trying to figure out what's going on w this previously reliable machine.

So I ran a scan w Eset Nod32, as well as Malware Bytes & SuperantiSpyware as suggested.
These all finished clean without finding any issues (except a few tracking cookies)
ADwCleaner found a few things in random folders and I had it clean those.

In addition, I ran the Sfc Scannow and it completed and didn't find any integrity issues.
The other Scanreg f/ r/ command said it would run the next time I rebooted since it needed the drive to be fixed.

I also trimmed the programs that launch at startup and updated my Nvida video driver.
I've also downloaded MemTest since I'm thinking that should be checked to and will run it tonight.

That being said, the system has BSOD at least 7 times today so I've attached the newest DM LOG so you can see it for yourself. I've also attached the notes from the reboot, so please let me know your thoughts and the next steps.


Here is the event log after BSOD w the most recent crashes at the bottom:


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050031
BCP3: 00000000000406F8
BCP4: FFFFF88001838E9C
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\062815-15334-01.dmp
D:\Users\Travis\AppData\Local\Temp\WER-28797-0.sysdata.xml

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80003527306
BCP3: FFFFF8800961FF90
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\062915-15943-01.dmp
D:\Users\Travis\AppData\Local\Temp\WER-31886-0.sysdata.xml

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: 50
BCP1: FFFFF88051A12B38
BCP2: 0000000000000000
BCP3: FFFFF9600013C81F
BCP4: 0000000000000005
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\062915-15288-01.dmp
D:\Users\Travis\AppData\Local\Temp\WER-99840-0.sysdata.xml
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: 50
BCP1: FFFFF8800E5A797A
BCP2: 0000000000000001
BCP3: FFFFF80003580805
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\063015-15990-01.dmp
D:\Users\Travis\AppData\Local\Temp\WER-3090301-0.sysdata.xml
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: 50
BCP1: FFFFF80004580DE6
BCP2: 0000000000000008
BCP3: FFFFF80004580DE6
BCP4: 0000000000000002
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\063015-17737-01.dmp
D:\Users\Travis\AppData\Local\Temp\WER-31449-0.sysdata.xml

 

[ICIT2LOL]

Wow so many dumps mate and one that has got me concerned is this one which involves a graphics issue for ATI failure so before you got the NVidia were you running ATI graphics? if so find and uninstall them plus the Catalyst Control Centre that goes with ATI.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
[COLOR=red]VIDEO_TDR_FAILURE[/COLOR] (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800dd0b4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880048f78c8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
Debugging Details:
------------------

FAULTING_IP: 
atikmpag+78c8
fffff880`048f78c8 4883ec28        sub     rsp,28h
DEFAULT_BUCKET_ID:  [COLOR=red]GRAPHICS_DRIVER_TDR_FAULT[/COLOR]
CUSTOMER_CRASH_COUNT:  1
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
fffff880`02ddb988 fffff880`056da000 : 00000000`00000116 fffffa80`0dd0b4e0 fffff880`048f78c8 00000000`00000000 : nt!KeBugCheckEx
fffff880`02ddb990 fffff880`056d9d0a : fffff880`048f78c8 fffffa80`0dd0b4e0 fffffa80`088476f0 fffffa80`0833f410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02ddb9d0 fffff880`05780f07 : fffffa80`0dd0b4e0 00000000`00000000 fffffa80`088476f0 fffffa80`0833f410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`02ddba00 fffff880`057aab75 : 00000000`ffffffff 00000000`092db8cd 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02ddbae0 fffff880`057a92bb : 00000000`00000102 00000000`00000000 00000000`092db8cd 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02ddbb10 fffff880`0577c2c6 : ffffffff`ff676980 fffffa80`0833f410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02ddbbb0 fffff880`057a8e7a : 00000000`00000000 fffffa80`08bbeb30 00000000`00000080 fffffa80`0833f410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02ddbcc0 fffff800`02d30e6a : 00000000`fffffc32 fffffa80`087c7b50 fffffa80`06a4b040 fffffa80`087c7b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02ddbd00 fffff800`02a8af06 : fffff800`02c0ce80 fffffa80`087c7b50 fffff800`02c1acc0 3033646e`49584c2f : nt!PspSystemThreadStartup+0x5a
fffff880`02ddbd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
atikmpag+78c8
fffff880`048f78c8 4883ec28        sub     rsp,28h
SYMBOL_NAME:  atikmpag+78c8
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME:  [COLOR=red]atikmpag.sys[/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  4ebb331c
FAILURE_BUCKET_ID:  [COLOR=red]X64_0x116_IMAGE_atikmpag.sys[/COLOR]
BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x116_image_atikmpag.sys
FAILURE_ID_HASH:  {83e844bc-fe68-2042-4230-7f5d3e90b48a}
Followup: MachineOwner

 

[austin1313]

Yes, my system has been going down like a $2 hooker lately.

As far as ATI and Catalyst, that is exactly right!
Before I switched to the NVidia card a few weeks ago, I was using an ATI Radeon HD 4850 w ATI Catalyst software. Since updating the NVidia drivers yesterday, I don't see any reference to Catalyst or ATI in my programs in Control Panel. Does this mean it has already been removed from my system when I updated??

Please let me know.

 

[ICIT2LOL]

Ok mate now one way you can check to see if there are any ATI stuff on the machine is to look inside the registry.

To do that > Start > type "regedit" No quotes) > a blue box with regedit will pop up > click on that > then - Yes > a window will open with the registry entries in it.
Look at my pic and open it out - you can see my old laptop here has ATI entries listed let us know if you have the same. Now it may be that being the on board graphics (like my old laptop here) it will have entries because of the hardware.
Don't do anything until we know.

 

[austin1313]

Interesting. It's not in control panel but regedit shows there are entries for both AMD and ATI.

I've attached a screenshot here.
Please let me know what I should do next.
And thanks again for the helping hand.

 

[ICIT2LOL]

Ok sorry for late reply and that is just about exactly what is in my registry entries though I am running ATI graphics simply because the laptop cannot accept a NVidia card.

You will notice a little further down that listing the NVidia entries Now before you go deleting any entries for ATI follow and do this http://www.sevenforums.com/tutorials/4230-registry-backup-restore.html I being a tad pedantic do it to my desktop and a stick.

Now I have to go offline for a while and I will get back to you a little later

 

[austin1313]

Hello there, my friend.
I was away for a bit enjoying the holiday and am now back at the grind and at this crashing computer.
Hopefully you're well and had a nice break offline too.

So I backed up the registry w a restore point, as suggested in your link.
Please let me know how to delete these ATI entries in the registry and I'll be sure to do so.

I also had hoped that maybe updating the NVidia driver would have reduced the crash frequency, but that is not the case. In fact, I've already had at least 4 BSODs this morning. Also the computer was on while I was away and since I sometimes remote in to grab work files, I know it crashed a number of times over the weekend/earlier in the week also since it was always at the log in screen when I remoted in instead of the desktop. So I ran DM log collector and have attached the update report file as well as the updated text file showing the errors on reboot.

It also seems that crashes most frequently occur when I'm browsing the web.
My browsers are Chrome, Internet Explorer and Firefox and I can't say it happens more with any specific browser. Then again this observation may be coincidental since I spend most time on the web.

Please let me know what we should do/update/etc since this thing is driving me nuts.

Thanks again.

 

[austin1313]

Good afternoon.

Crashed another 10 times this afternoon and the day is only halfway over, so posting an updated log file.
Hopefully this helps sleuth out what is crashing this system so frequently.
And it does seem to happen more often when a browser is open.

Please let me know what the next steps are.
Thanks.

 

[ICIT2LOL]

Ok mate something is very amiss

*******************************************************************************
*                                                                            *
*                       BugcheckAnalysis                                   *
*                                                                            *
*******************************************************************************[/COLOR]

[COLOR=black]PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected bytry-except,
it must be protected by a Probe.  Typically the address is just plain bador it
is pointing at freed memory.
Arguments:
Arg1: fffff6fb7e203f28, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002cd4bc1, If non-zero, the instruction address which referencedthe bad memory
 address.
Arg4: 0000000000000009, (reserved)[/COLOR]

[COLOR=black]Debugging Details:
------------------[/COLOR]


[COLOR=black]Could not read faulting driver name[/COLOR]

[COLOR=black]READ_ADDRESS:  fffff6fb7e203f28 Nonpaged pool[/COLOR]

[COLOR=black]FAULTING_IP: 
nt!MmBuildMdlForNonPagedPool+81
fffff800`02cd4bc1 488b4500       mov     rax,qword ptr [rbp][/COLOR]

[COLOR=black]MM_INTERNAL_CODE:  9[/COLOR]

[COLOR=black]CUSTOMER_CRASH_COUNT:  1[/COLOR]

[COLOR=black]DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT[/COLOR]

[COLOR=black]BUGCHECK_STR:  0x50[/COLOR]

[COLOR=black]PROCESS_NAME:  System[/COLOR]

[COLOR=black]CURRENT_IRQL:  0[/COLOR]

[COLOR=black]ANALYSIS_VERSION: 6.3.9600.17298(debuggers(dbg).141024-1500) amd64fre[/COLOR]

[COLOR=black]TRAP_FRAME:  fffff8800b54a610 -- (.trap0xfffff8800b54a610)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000000c0 rbx=0000000000000000 rcx=0000000000000780
rdx=000000000000183f rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cd4bc1 rsp=fffff8800b54a7a8 rbp=fffff6fb7e203f28
 r8=0000000000000000  r9=0000007c407e5888 r10=fffffa800990fd30
r11=fffff880fcb11000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MmBuildMdlForNonPagedPool+0x81:
fffff800`02cd4bc1 488b4500       mov     rax,qword ptr [rbp]ss:0018:fffff6fb`7e203f28=????????????????
Resetting default scope[/COLOR]

[COLOR=black]LAST_CONTROL_TRANSFER:  from fffff80002c8e265to fffff80002ce61c0[/COLOR]

[COLOR=black]STACK_TEXT:  
fffff880`0b54a4a8 fffff800`02c8e265 : 00000000`00000050 fffff6fb`7e203f2800000000`00000000 fffff880`0b54a610 : nt!KeBugCheckEx
fffff880`0b54a4b0 fffff800`02ce42ee : 00000000`00000000 fffff6fb`7e203f28fffffa80`0823dd00 fffffa80`0990fd60 : nt! ?? ::FNODOBFM::`string'+0x4539d
fffff880`0b54a610 fffff800`02cd4bc1 : fffffa80`09c06180 fffffa80`0823d050fffff880`0593128e 00000000`c000000d : nt!KiPageFault+0x16e
fffff880`0b54a7a8 fffff880`0593128e : 00000000`c000000d fffffa80`06e77a00fffffa80`06eacdf0 00000000`00000000 : nt!MmBuildMdlForNonPagedPool+0x81
fffff880`0b54a7c0 fffff880`05939e74 : fffffa80`06df5d30 fffffa80`085d0009fffffa80`06df5d30 fffffa80`09c06180 : USBPORT!USBPORT_ProcessURB+0x91a
fffff880`0b54a870 fffff880`05913af4 : 00000000`00000000 fffffa80`085d9050fffffa80`096c8c60 fffffa80`06df5d30 :USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x138
fffff880`0b54a8b0 fffff880`062c5566 : fffffa80`085db050 fffffa80`06f14060fffffa80`06df5d30 fffffa80`085db1a0 : USBPORT!USBPORT_Dispatch+0x1dc
fffff880`0b54a8f0 fffff880`062f5d8f : 00000000`00000000 00000000`00000000fffffa80`06f14060 00000000`00000801 : usbhub!UsbhFdoUrbPdoFilter+0xde
fffff880`0b54a920 fffff880`062c3fb7 : fffffa80`06e961b8 00000000`00000000fffffa80`06df5d30 fffffa80`06f481b8 : usbhub!UsbhPdoInternalDeviceControl+0x373
fffff880`0b54a970 fffff880`06219ec4 : 00000000`00000000 fffffa80`06f482b800000000`00000000 fffffa80`06f481b8 : usbhub!UsbhGenDispatch+0x57
fffff880`0b54a9a0 fffff880`06216812 : fffffa80`06e961b8 fffffa80`06df5d3000000000`00000324 fffffa80`06df5d30 : usbccgp!UsbcForwardIrp+0x30
fffff880`0b54a9d0 fffff880`06216aba : fffffa80`06f481b8 00000000`00220003fffffa80`06df5d30 fffffa80`06e961b8 : usbccgp!DispatchPdoUrb+0xfa
fffff880`0b54aa10 fffff880`0621472e : 00000000`0000000f fffffa80`06e961b0fffffa80`06e961b8 fffffa80`06df5d30 :usbccgp!DispatchPdoInternalDeviceControl+0x17a
fffff880`0b54aa40 fffff880`0a176b05 : fffffa80`06e96060 fffffa80`06e9600100000000`00000000 00000000`00000000 : usbccgp!USBC_Dispatch+0x2de
fffff880`0b54aac0 fffffa80`06e96060 : fffffa80`06e96001 00000000`0000000000000000`00000000 00000000`00000000 : RTS5121+0x7b05
fffff880`0b54aac8 fffffa80`06e96001 : 00000000`00000000 00000000`0000000000000000`00000000 00000000`00000000 : 0xfffffa80`06e96060
fffff880`0b54aad0 00000000`00000000 : 00000000`00000000 00000000`0000000000000000`00000000 00000000`00000001 : 0xfffffa80`06e96001[/COLOR]


[COLOR=black]STACK_COMMAND:  kb[/COLOR]

[COLOR=black]FOLLOWUP_IP: 
RTS5121+7b05
fffff880`0a176b05??             ???[/COLOR]

[COLOR=black]SYMBOL_STACK_INDEX:  e[/COLOR]

[COLOR=black]SYMBOL_NAME:  RTS5121+7b05[/COLOR]

[COLOR=black]FOLLOWUP_NAME:  MachineOwner[/COLOR]

[COLOR=black]MODULE_NAME: RTS5121[/COLOR]

[COLOR=black]IMAGE_NAME:  [/COLOR][COLOR=red]RTS5121.sys[/COLOR]

[COLOR=black]DEBUG_FLR_IMAGE_TIMESTAMP:  484630fc[/COLOR]

[COLOR=black]FAILURE_BUCKET_ID:  X64_0x50_RTS5121+7b05[/COLOR]

[COLOR=black]BUCKET_ID:  X64_0x50_RTS5121+7b05[/COLOR]

[COLOR=black]ANALYSIS_SOURCE:  KM[/COLOR]

[COLOR=black]FAILURE_ID_HASH_STRING: km:x64_0x50_rts5121+7b05[/COLOR]

[COLOR=black]FAILURE_ID_HASH: {39668f1d-2e60-d622-1e8a-d61d8e2a4cd9}[/COLOR]

[COLOR=black]Followup: MachineOwner

This is an issue with Realtek USB mass storage(Card reader) namely drivers

In addition going on the age of the machine Iwould suggest you run these too

http://www.seagate.com/au/en/support/downloads/item/seatools-win-master/ forthe drive but first run my ditty too as I am interested to see what thePSU comes up with

Using HW Info

You can test the volts on the PSU with HWInfo HWiNFO, HWiNFO32/64 -Download < download the right bit version andclose the right hand window select Sensors and scroll down to the power sectionwhere you will see what the volts are doing see my pic.

The original right hand window shows themachine running and is handy for that but for looking at the components in some detail close it and use themain left hand side panel

FOR OTHER COMPONENTS

Open each + down into the componentitself and then click on it - in theright hand side will appear all sorts of details including brands speeds andother essential info that device. See pic for example.

 

[austin1313]

Thanks again for the advice, even if some of it is a bit over my head.... especially the log report.
So I ran that hardware program and I think the voltages are fine since they were close to yours.
I've copied a screen shot of it here so you can confirm I'm reading it correctly since it looks a little different than your screen shot being that its a different version.

I also ran the SeaTools and while my OS & Data drive passed the short DST and short generic, my XiMeta Diskdisk NDAS drive failed. This is a net drive that all computers on the network access.
That said, I've been running it as a USB attached drive for the last 2 months (local and not networked) since its performance was spotty and the BSOD errors keep coming even w it not on the LAN, so I don't think it's that drive taking things down. Most likely just a future problem (I'll order a new drive tonight to prevent a problem later)

In the interim, I'm updating all my drivers tonight.
That TweakBit program that was linked to the word drivers in your page let me scan my system but not update. Since the reviews for it were hit or miss w respect to it dling the right drivers, I'm going to use a different program called SlimDrivers where I can manually DL each driver.
This way if something fails, I know which driver is DLed in error since I'll do a restart after each driver install.

Other than that, did any of the recent dump logs give us a primary culprit??
I've already updated the realteck drivers and I think it controls the card reader built into this case.
I don't use it too often, but maybe it also controls the external front USB ports, which I do use.

Let me know what you recommend doing next and I'll also let you know once the drivers are all updated.

And thanks again for all your help!

 

[ICIT2LOL]

Ok mate you are right the volts are ok see pic.

Now I much prefer getting drivers for machine from the manufacturers. Having said that I see the Gateway site is a bit of a sows ear Drivers & Downloads perhaps you might have more luck then me by using the auto detedt form that link.

Now I have used Slim Drivers and they are not bad but if you want my advice - then as soon as you have finished with it uninstall it because it is a nagging site for one thing and for another will put up drivers that need not be updated.

Your board of course is getting on now and I think it would not be a bad idea to run a test on the RAM to be honest see this

MEMTEST

The memtest you will need to make a bootable disk / stick andset the BIOS to boot from the optical or USBand it will take a fair time torun- some leave it overnight.

This is the current version Memtest86+ - Advanced Memory Diagnostic Tool please use this as any other test is useless - the Windows one sadly is not worth even a thought about.

But one thing is very important you must let the test run for at least 8passes any less and the findings are no good. Now if errors come upstraight away then you can stop it - see my pics. Now if there are errors andyou have more than one stick of RAM in then you will need to test each stick ieremove the sticks and replace stick 1 in slot 1 and test no errors do thesame in slot 2 with stick 1 no errors then repeat the process with stick 2 -that will show up the faulty stick - the other thing is it could be a faultyslot but most unusual. With more than two sticks the process is even longer asone may realize.

It is a very lengthy and tedious process but worth it if youhave errors.

 

[austin1313]

Good afternoon.
You weren't kidding that Memtest takes a long time.
I ran it 10 hours last night and it was only on the 5th pass this morning.
Since I had to work today, I had to stop the program so I could use the computer.
That said, there were no errors found.
I think I ran it as a single thread on one core, so next time I'll run as multi-thread/core tonight and hope the full 8 passes takes less than 12 hours.

I've updated all of my drivers w SlimDrivers and also w DriverBooster2.
What's interesting is that SlimDrivers says everything is up to date, DriveBooster says everything is up to date but there are 3 drivers that can only be updated w the full (Paid) version of the software (and it doesn't tell me what these are), and tweakbit driver updater says there are 14 drivers that need updates (this is the original number so it's almost like that program hasn't noticed the updates since the scan)
Any thoughts if I should run another program to reconfirm the driver updates.

One thing I've noticed is that my screen will sometimes turn black and then instead of crashing it'll say NVidia graphics process crashed but has successfully restarted.
Not sure if this helps w diagnostic, but wanted to advise.
Also we were going to get rid of the ATI remnants in the registry, but we never did that since I'm not sure how. We backed up the registry w a restore point, but that's it.
So please let me know if I should remove those 3 or 4 entries and if there's anything else I should do before tonight.

And thanks!!
The BSOD frequency seems to have decreased somewhat and I appreciate your time and expertise w this.

 

[austin1313]

Also a lot of times when I'm using Chrome to watch youtube or watching videos it says "Aw, snap. Something went wrong while displaying this webpage" and shows the crashed plugin icon.

This happens frequently.

Just wanted to add that in case it clarifies.

 

[ICIT2LOL]

Yes well Austin mate this is a very odd dump as I have no real references for it that we usually use.

The memory mate it will take a long time but needs to be done to rule out that possibility.

 

[austin1313]

Thanks for the prompt reply and your help.
It is strange and intermittent problems are also more difficult to tech than consistent ones.

That said, my Nvdia display driver erros: "Display has stopped responding and recovered" are VERY Frequent. In fact, I feel that instead of BSODs happening all the time when I'm watching something, now I'm getting these messages all the time-- but at least everything comes back without the system restarting.

I'll let you know the result of the ram tomorrow morning when that finishes.
But if you get any other ideas, please advise.

 

[ICIT2LOL]

Ok you have given me an idea - run these two ditty's of mine and post back what you find and what happens. Do the slot cleaning first as it is the most simple and the HW Info after if you have any problems in finding the PSU rail volts as in the ditty the give away is the Vbatt in the section you scroll down to.

Anyhting that comes out of either could explain the intermittent behaviour.

SLOT CLEANING

Now as for the slots to clean themuse a strip of old credit card about 1/2 inch wide nip the corners off one end- preferably round them off hold a piece of thin lintfree cloth over the end dab on some form of alcohol - isopropyl alcohol (whatwe swab the skin with before an injection) is good and GENTLY swipe along the slots.

This can also be done for the GPUslot/s and also the contacts of the sticks or cards - not the stick but somelint free cloth of course. See my pic for the sick but please be very gentledoing it if you are in any doubt - please ask before doing it but I use thisall the time and have yet to damage anything.


Using HW Info

You can test the volts on the PSU with HWInfo HWiNFO, HWiNFO32/64 -Download < download the right bit version andclose the right hand window select Sensors and scroll down to the power sectionwhere you will see what the volts are doing see my pic.

The original right hand window shows themachine running and is handy for that but for looking at the components in some detail close it and use themain left hand side panel

FOR OTHER COMPONENTS

Open each + down into the componentitself and then click on it - in theright hand side will appear all sorts of details including brands speeds andother essential info that device. See pic for example.