Error related to symbols?

[jtypeb]

Hello all,

Brand new member here. I came upon this forum while looking for ways to understanding debugging better. I have had some problems in the past with stop codes, crashes etc. I am currently trying to solve a problem that I know is related to ram. I have been posting on Corair House of Help and TweaK Town forums under the same name and I'm convinced the ram I'm using has problems. Unfortunately the issues seem to come and go and so it's very challenging to try to fix. I decided I need to learn to debug these things as best I can. Besides, the whole process is kind of fun.

Anyway, that leads to the real reson for this post. I have included a recent memory dump and with it I ask 2 specific questions:

1.) What is the meaning of the Warning that says--"WARNING: Whitespace at end of path element"? I copy/pasted the path provided on the tutorial page to access symbols. Is it related to that?

2.) If there is anything in minidump that leads you to solving my problems...please do. I guess that really isn't a question but you know what I mean.

Thank You in advance for any assistance

 

[usasma]

Whitespace isn't desirable because the tool doesn't really know how to deal with it.
It most likely means that there's some blank spaces after the link for the symbols, but it could also be indicating spaces between the 2 entries.

First, highlight and delete the current entry in the Symbol File Path.
Then copy and paste the text in the following Code box:

SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols

Then click on OK to save it in the current workspace
Then, when closing the debugger, click on Yes when it asks if you want to save it.

There is very little in the analysis of your dump file that helps us to figure this out. This is because the error pertains to a System Service Exception.

First, these errors are most often solved by examining multiple dump files and finding a common pattern.
There's also other things that we do to massage the dump files to extract extra info.

Please follow the directions here to provide us with more data to analyze: http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

 

[jtypeb]

Thanks usasma. I made the change in the symbols path as you said and the error is gone.
Ive attached the minidumps like you asked too. Eager to hear what you think

Thanks again

 

[usasma]

One of the memory dumps was empty, so it won't appear in this analysis (120509-21996-01.dmp)

Although I doubt that this is a memory problem, you've got a couple of Memory Management errors - so it's a wise move to conduct a free memory diagnostic: Memory Diagnostics

I suspect that this is a System Service that's been misbehaving (from the stack text). The most successful way of diagnosing these is remembering what changes happened to the system just before the BSOD's started to occur. Unfortunately, this isn't always possible, so we'll try other stuff.

Please upload this report:

MSINFO32
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.

This will, hopefully, allow us to spot other errors that may be related (such as application errors that precede the kernel dumps).

But, in the event that that doesn't work, let's also try Driver Verifier. Please follow these instructions exactly to enable it:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.


So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista Startup Repair feature).


Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.


Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.


Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.


More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
​

 

[jtypeb]

I've attached the msinfo32 file as you requested.
I know you don't think this is a memory error and you might well be right but I think it is. Here's the history:

I have been receiving many errors when using a particular brand of memory(Corsair) and the computer runs error free when using a different brand(Crucial). The build as about a year old. Do not overclock and don't partake in any real risky behavior. The system is well built, well cooled and well organized. The Corsair memory was the original install but it came with a bad module. I RMA'd it but didn't want to wait for the replacement so I bought the Crucial. The Corsairs are a much higher performance stick though and so I installed them when the new ones came. The Crucials went into the closet with me knowing I had a spare if needed.

Until about 3 weeks ago the Corsairs have worked flawlessly. Then the errors started. Mostly application hangs but also blue screens and other weird behavior including services not loading or timing out etc. I have deleted and replaced graphics, chipset, network, and audio drivers. CHKDSK finds no errors on the hard drive.

I have memtest86+ v4.00 and have used it numerous times on this and my other computers. I have also used the Windows memory test program.

These past 3 weeks I have run memtest many many times in various different ways. Both sticks in, one stick at a time, different slots etc. The only consistency is this;

Crucial always tests fine
Corsair single stick always tests fine. Either stick, any slot, results always the same...no errors.
Corsair both sticks test fine as long as I haven't suffered a recent bad event. In other words when changing from one pair to the other I would always memtest first. Results always pass. Once I've had an error, if I shut down and memtest-always errors, sometimes thousands.

This morning after reading your response my computer started to throw errors. Started with IE Explorer hang, then windows explorer wouldn't respond, then event viewer wouldn't respond, then shut down wouldn't work resulting in a black screen(1st time for this). Shut down with the switch. Then powered back on and ran memtest. 3 passes with errors in test#5 only on the 1st pass.

I am booted back on to Windows and for now it's working but I know it's only a matter of time. Event viewer gave a 2 warning that "The winlogon notification subscriber <GPClient> was unavailable to handle a notification event." Whatever that means.

The most significant shange to my system recently is I installed the Retail version of Windows 7 ultimate. I originally had Vista Home Premium and since Spring was dual booting Vista and Window 7 Beta. I liked windows 7 so much I almost never used Vista

Sorry to make this such a long post but wanted you to know the backround.

I will wait for your review of the msinfo32 stuff before I move on to the Driver Verification exercise.

Thanks for helping

 

[usasma]

I've seen a lot of posts from people with the Gigabyte EP45-xxx motherboards
So I wonder if there's a similar issue to the one that the Asus P5x series has.
That is that there are memory voltage and timing issues - and for that I suggest you check with both Gigabyte and the memory manufacturer for the recommended settings.

FWIW - If your system can't run properly at the default settings on the motherboard, then there's something wrong - either with the motherboard or the RAM. I distrust having to change voltages/timings in order to make equipment work - it's akin to overclocking and isn't appropriate in a stock system.

Lot's of errors in the MSINFO32 - but they are nearly all in user mode (and we're looking at kernel mode events here).

Leave the Crucial (error free) RAM in, and then run the Driver Verifier to see if there's an issue.

 

[jtypeb]

FWIW - If your system can't run properly at the default settings on the motherboard, then there's something wrong - either with the motherboard or the RAM. I distrust having to change voltages/timings in order to make equipment work - it's akin to overclocking and isn't appropriate in a stock system.

I agree with that but I guess since I use 1066 ram that too is a version of overclocking. What I really value is stability.

I just last night put the Crucial(Stable)ram back in. Ran memtest and got no errors. Then I ran prime 95 overnight about 10 hours and received no errors. Then this morning I proceeded to do the Driver Verifier Check as you suggested. The attached .zip file shows the resulting bugcheck. I also attached a new msinfo32 file as there have been other activity shown in the event viewer that don't result in minidumps.

The Driver Verifier check would not allow me to reboot to Windows. It would crash immediately before getting to the start screen. Safe mode was not presented as a boot option. Only Launch startup repair or Load Windows normally. I used my restore point and that worked fine so the computer is working.

I am hopeful your look at the dump will give us some insight.

Thanks again for helping me.

 

[usasma]

Please start by running these hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Then, because of the presence of NTFS.SYS in the stack text, please do the following:

CHKDSK /R
Run CHKDSK /R from an elevated (Run as adminstrator) Command Prompt.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry.
Copy/paste the results into your next post.

 

[jtypeb]

Memtest86+ v4.00--5 passes--NO ERRORS
HD Diagnostic--Western Digital Diag504 FCD-Extended Test--NO ERRORS
Malware Scans--Used 3--Found a few cookies but no virus. Note: I regularly scan with MalwareBytes manually as well as Microsoft Security
CHKDSK /R--Results are attached--NO ERRORS

 

[usasma]

Thanks for posting the test results - we can rule out hard drive problems for now.

Please run Driver Verifier according to these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.


So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista Startup Repair feature).


Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
- Select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.


Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.


Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.


More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
​

 

[jtypeb]

Interesting and encouraging development this time using Driver Verifier.

Windows crashed again on boot but this time it happened after keying in my password. The resulting blue screen identified Rivatuner64.sys as the driver trying to currupt the system. The error code is c4.

I was able to boot in safe mode and turned Driver Verifier off. Have since rebooted into Windows and grabbed the minidump. It is attached.

I assume the Rivatuner64 driver needs to go but I havent done anything yet. I do use Rivatuner to control the fan settings on my graphics card. The default fan speed is 40 % so I have programmed Rivatuner to increase it based on temperature when I'm gaming. My hope is to be able to keep using Rivatuner but would like to hear what you think or know about it. Now that I think about it, I had Rivatuner in an older system a few years ago and eventually removed it as it caused quite a few issues.

I await your reply

 

[usasma]

You'll have to uninstall RivaTuner while we're troubleshooting this issue.
If it cures the BSOD's, then there's very few things left to try.

Your RivaTuner64.sys driver is from 2007 (RivaTuner64.sys Tue Jul 17 15:13:42 2007)
I'd suggest seeing if there's a newer version out on the web.
If not, post back and we'll see about installing it in compatibilty mode.

 

[jtypeb]

I have uninstalled Rivatuner. Since I only use it for fan control and dont overclock the card, I'm sure I can find something else to use. I've heard EVGA Precision works well and is compatible with windows 7 64bit. Anyhow, that's for later.

You'll recall that the system is stable with the current ram installed. Is there anything we should do right now in the form of a test or do we just let it ride and see if it stays good?

Please let me know and thanks again for the help.

John

 

[usasma]

Evga uses (AFAIK) components from Riva Tuner - but you'll have to check to be sure.

If it's working well, why mess with it? Leave it go and see if you are error free for a week - after that it's most likely another issue.

Good luck!