[moscatomg1]

Ok, I ran sfc /scannow. It seemed to run very fast--almost a popup, flash, and it was finished. (I ran it a few times for good measure.) I'm not sure if this is normal, but I guess that means it found no errors. Was I supposed to find and post that log file even if it didn't find anything?
Thank you again!

[Advertisements]

SFC is not normally quick in fact it can and mostly does take a long time.

If no errors are found you should receive the following message;

"Windows resource protection did not find any integrity violations".

Please search for C:\Windows\Logs\CBS folder. You'll see CBS.log file.

[phillpower2]

SFC is not normally quick in fact it can and mostly does take a long time.

If no errors are found you should receive the following message;

"Windows resource protection did not find any integrity violations".

Please search for C:\Windows\Logs\CBS folder. You'll see CBS.log file.

[moscatomg1]

Oh, I'm not sure what I was doing wrong the first times. I ran it successfully now I think (I saw it say "100% complete" but still not sure if I saw that other message you mentioned). But here's the link to the CBS log: https://www.mediafir...34qw1qq5rc7r441

Thanks for your help!

[phillpower2]

You are welcome and thanks for the CBS log

Errors have been detected and corrected so all we can do now is wait and see how the computer behaves, what I will ask you to do now is check for and install any/all important updates for Windows 7 and your anti virus software.

Is Avast your anti virus software btw.

Incidentally your earliest error was shown to be as far back as the following;
2013-06-28 15:49:47, Info CBS Failed to get session package state for package: Package_6_for_KB2807986~31bf3856ad364e35~x86~~6.1.1.2 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

Further information on the error here with these details in mind, if the issue is not resolved it would be wise for me to refer you to the malware forums.

[moscatomg1]

Sorry it's taken so long for a reply; for some reason I never saw any auto. email notification in my inbox on your last reply (probably overlooked by me). In any case, thank you for checking the log out. (And, yes, Avast is my antivirus.) Also, I finally remembered to hook my PC to ext. monitor when the screen went glitchy again: it did *not* replicate on the ext. monitor. However, I'm not sure how helpful a test that is since, again, the whole sys. is essentially freezing when this glitch occurs, so what happens is that the ext. monitor just doesn't receive any signal (simply remains blank like nothing is connected). . . . So you think malware check is the next step. . . . Will do. It's too bad that having isolated this problem exclusively to start-up (mostly if not always out of hibernate) didn't help us. But maybe that will be a useful variable for the malware diagnosis. Well, I appreciate all your help & patience--thank you!

[phillpower2]

No apology necessary we all have a blip here and there

As you have not yet created a new topic on the malware forums can I ask you to do two things for us first;
1: In case I misinterpreted the following from your reply #12 "It did result in BSOD at startup." can I ask at what point as in was it during or after Windows had loaded > please retrieve the last dump file from c:\windows\minidump (if there is one available of course) and attach it to your next reply.
2: Purely for elimination purposes can I ask that you temporarily change your AV software from Avast to MSE, if your Avast is the paid for version please make a note of the licence key number before uninstalling it, if you have not done so already that is.

Even if we are able to resolve the issue here first I would still suggest that you follow the GTG malware redirect text that I will provide in my next reply, this as a precautionary measure and if you do need to create a new topic on the malware forums we must put this topic on hold.

You are most welcome btw moscatomg1

[moscatomg1]

OK, I'm attaching the last dump file in a zipped folder. (There was another recent bsod, which this latest dump file should indicate. . . . Like the screen glitches, these seem to occur while Windows is loading.)

Also, I will change av program as recommended.

Thanks again!

Edit: oh, and windows updates are current.

Attached Files

•  011014-35412-01.zip   32.11KB   163 downloads

Edited by moscatomg1, 11 January 2014 - 07:46 AM.

[phillpower2]

Please answer question 1 from my reply #21

1: In case I misinterpreted the following from your reply #12 "It did result in BSOD at startup." can I ask at what point as in was it during or after Windows had loaded

[moscatomg1]

another recent bsod, which this latest dump file should indicate. . . . Like the screen glitches, these seem to occur while Windows is loading.)

Sorry if it wasn't clear from that: both the bsod AND screen glitches appear to occur During windows loading. . . .

BUT I am going to keep a very close eye for next time it happens, b/c now I have a 1% doubt whether it really is happening during Windows loading or immediately/instantaneously after it has started/loaded.

Thank you,

[phillpower2]

Ok we will wait on your next update.

[moscatomg1]

Well, I have not yet seen the screen glitch re-appear, But the BSODs continue. The last BSOD occurred *after* Windows loaded. If useful, here's the minidump file.
Thank you!

Edit: also, Windows is updated, and I did change the A/V from Avast to MSE.

Attached Files

•  011714-32089-01.zip   31.91KB   163 downloads

Edited by moscatomg1, 17 January 2014 - 09:06 PM.

[phillpower2]

After looking at your latest crash dump I recommend that you run Memtest for between 6 and 7 passes, this can take a long time so I suggest that you leave it overnight, Memtest guide courtesy of rev_olie here

Depending on the Memtest results it may be necessary to do a physical check, I will post a guide for this as and when it is required.

Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.17273.x86fre.win7_gdr.130318-1532
Machine Name:
Kernel base = 0x81a0a000 PsLoadedModuleList = 0x81b52810
Debug session time: Fri Jan 17 21:50:16.258 2014 (UTC - 5:00)
System Uptime: 5 days 7:57:19.104
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 81c2cfef, The address that the exception occurred at
Arg3: b5c4fc1c, Trap Frame
Arg4: 00000000

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
nt!ObpDecrementHandleCount+10
81c2cfef 102408 adc byte ptr [eax+ecx],ah

TRAP_FRAME: b5c4fc1c -- (.trap 0xffffffffb5c4fc1c)
ErrCode = 00000002
eax=843869eb ebx=00000000 ecx=b446a944 edx=87a346f8 esi=87a3b5f8 edi=843869a8
eip=81c2cfef esp=b5c4fc90 ebp=b5c4fc94 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!ObpDecrementHandleCount+0x10:
81c2cfef 102408 adc byte ptr [eax+ecx],ah ds:0023:387f132f=??
Resetting default scope

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x8E

PROCESS_NAME: CNABCSWK.EXE

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 81c4fe72 to 81c2cfef

STACK_TEXT:
b5c4fc94 81c4fe72 84148a10 b446a938 843869a8 nt!ObpDecrementHandleCount+0x10
b5c4fcdc 81c51672 b446a938 afd93380 84148a10 nt!ObpCloseHandleTableEntry+0x203
b5c4fd0c 81c517ea 84148a10 84386901 02a3fe64 nt!ObpCloseHandle+0x7f
b5c4fd28 81a4c6da 000001c0 02a3fe68 77676194 nt!NtClose+0x4e
b5c4fd28 77676194 000001c0 02a3fe68 77676194 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
02a3fe68 00000000 00000000 00000000 00000000 0x77676194


STACK_COMMAND: kb

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: STRIDE

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE

BUCKET_ID: MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption