Main Forum > Tweaking.com Support & Help

Tweaking Free- Logs or Reports

<< < (2/6) > >>

Boggin:
Yes there are.

Open Windows Explorer - Windows C: - Program Files (x86) - scroll down to Tweaking com and double click on it then double click on Windows Repair (All in One) then click on Logs.

You haven't said if you are using any other security program(s).

Larbo:
Thanks. Logs- didn't see anything regarding bad results. Lots of things not accessed since it was in Safe Mode, I guess. I added a Logs shortcut to the Start Menu for easy access later. Anything specific to look for or is there a primer on the topic?

Security Progs: Just Avast.  I do use CCleaner weekly or so. Got rid of Spybot months ago. Used Revo to do so.

OMG, I forgot to mention. About 4 months ago a memtested my RAM and one was bad. GSkills sent me a new pair. Yesterday, when I had done that "one at a time" test on the sticks, I put them back in the black slots. This morning I ran System Information and found that it was only detecting 1 stick. Discovered that my mobo prefers that 2 sticks use the gray slots, not the black. I moved them over, msinfo is happy and it has been a quiet morning. Mind you, this BSOD issue is a week old and the sticks went in months ago. But, there ya go. We'll see.

I just ran a program called Who Crashed to see what it woud do and it stated:
"Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. "
Is there any useful info in that? Probably not.

Boggin:
I think that tends to point to a software driver and the clean boot could point to which one.

Can you go Start - type eventvwr and press enter when it comes up.

Click on Error when it has read the data then click on View All Instances of This Event in the lower right pane then look for any time stamped errors for when the BSOD occurred.

There may be associated time stamped errors that may tell us more.

Also expand Windows Logs and click on System which in some cases can identify which driver is the cause - you'll probably have to scroll down the list.

Had you installed any programs or hardware prior to the BSODs occurring ?

Larbo:
Before I went out, I had a few minutes to play with eventvwr. Things didn't quite look the way I read it in your post. I will work with it some more tomorrow. Thanks for sticking with me!

Boggin:
Sometimes when I open Event Viewer, Event Viewer (Local) isn't highlight so you wouldn't get what you need to see.

This is what mine looks like with Windows Logs expanded.

BTW - Did you also check for updates in the Non-Plug and Play Drivers in Device Manager ?

Navigation

[0] Message Index

[#] Next page

[*] Previous page