Windows 7 Windows 7

[Neutral]

My problems with BSOD started a while ago. Probably in first quarter of 2012.
It lasted for at least half of year, and at the end of July they stopped. I can't remember what I did, I think I unninstalled nVidia drivers or sthg that was installed.
Now, about a week ago, BSOD's came back.

I attached all necessary files following Link Removed.

 

[Neutral]

Would you please use your Sytem's BIOS Utility to set your memory timings properly and see if that helps with the machine's stability
Currently your 400MHz memory which should be set to 5, 5, 5, 18, command rate 2T, is currently set as 266MHz memory 4, 4, 4, 12 command rate 2T
Please make those corrections and see if the problem persists.

Could you please explain your request a bit more.
What is that, and how do I do that what you want.

@kemical
Hm.. I'll go in order:

1) Mouse = Logitech MX518
2) Keyboard = Logitech G11
3) Sound = Logitech X-230 speaker set. (2 FDD satellites and 1 subwoofer)
4) Xbox 360 Controller for Microsoft Windows (Xbox 360 Controller - Wikipedia, the free encyclopedia)
I use Xbox 360 Accessories Software 1.2 64-bit for Windows 7 .
5) I have Zune software for my mobile phone (Nokia Lumia 710)

That's all I can remember for now, I don't think I use any extra hardware that would require drivers.

P.S.
Don't hesitate to torture me. I will give you all info you need, just ask

 

[kemical]

If you go into your bios and look under the memory section can you see if you can change the values? On certain boards you can, some you can't. Trouble is referring to RAM speed and timings which are currently incorrect. You may see a setting called 'set the bios to optimized defaults', try using that if all else fails.
Thank you for the info on what's on the machine. The drivers I couldn't find referred to daemon tools (big thanks to John Carrona for that info)

 

[Neutral]

I did as Trouble said, but I'm not sure I did it the way he wanted me to.

I entered BIOS and I see lots of tabs to choose (in order:
Main | OC Tweaker | Advanced | H/W Monitor | Boot | Security | Exit )

Under "OC Tweaker" there's part Memory configuration.
- Memory clock (It was set to AUTO, I changed to 400MHz DDR2_800)
- DRAM Voltage (I didn't touch it, it's set to AUTO)
- Memory timing (When I click this, new screen opens with a lot of parameters)

-> Memory timing
So first 4 settings were:
CAS LATENCY(CL) 4 CLK
TRCD 4
TRP 4
TRAS 12

I changed them to 5,5,5,18.

Under those 4, there are 20 or 30 more settings to change, all T***, but I didn't touch those.

After I did all that, I saved changes , exit BIOS and restart my PC.
As always I went to play FIFA 12 and as usual BSOD happened.
SYSTEM_SERVICE_EXCEPTION (3b)

*Latest BSOD uploaded in this post!

 

[Trouble]

Go back into your BIOS and return everything back to AUTO or as kemical indicated earlier use use one of the preset configs (like load optimized defaults or whatever the wording might be)
Disconnect your xbox controller from your computer
Uninstall any associated software and check and confirm that this driver
xusb21.sys 8/13/2009 is no longer present on your system. Probably here C:\Windows\System32\Drivers but may be elsewhere so do a search just in case.
See if that resolves the issue.
If not then go back into the BIOS and disable Cool N' Quiet and see if that helps.

 

[Neutral]

Cool N' Quiet is disabled by default.

Now, I uninstalled Xbox accessories and unplug the device from PC.
After that I went to C:\Windows\System32\Drivers and deleted xusb21.sys file.

This time I had BSOD saying "A driver has overun a stack-based buffer..." , don't remember the rest. I uploaded this BSOD as usual.

P.S.
This is first time I meet with this kind of BSOD. Never had one with this overunning stack-based buffer

 

[Trouble]

OK, well I guess if you can't make it better than make it worse and we can start from there.
Check you system memory for issues.

Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD from a cold boot after leaving it off for an hour or more.
Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.
See this Guide to using Memtest 86+

 

[Neutral]

I used Memtest86+ last time when I had BSOD's (check my first post, I refer to 1st Q of 2012), it gave clear results.

 

[Trouble]

My problems with BSOD started a while ago. Probably in first quarter of 2012.
It lasted for at least half of year, and at the end of July they stopped. I can't remember what I did, I think I unninstalled nVidia drivers or sthg that was installed.
Now, about a week ago, BSOD's came back.

I attached all necessary files following Link Removed.

OK, so I have re-read your first post (quoted above) and I am not sure how I might have gleaned from that, that you may have ran MemTest86+ at some point 6 months ago.
The way I see it now is that we can sit around with our fingers crossed and hope that your most recent dump file

[U][B]BugCheck F7[/B][/U], {8000f9600039a255, f9600039a255, ffff069fffc65daa, 0}
Probably caused by : win32k.sys ( win32k!_report_gsfailure+26 )
[U][B]DRIVER_OVERRAN_STACK_BUFFER (f7)[/B][/U]
A driver has overrun a stack-based buffer.  This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
[U][B]A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned.  This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.[/B][/U]
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and bugcheck call is the one that overran its local
variable(s).
Arguments:
Arg1: 8000f9600039a255, Actual security check cookie from the stack
[U][I][B]Arg2: 0000f9600039a255, Expected security check cookie
Arg3: ffff069fffc65daa, Complement of the expected security check cookie[/B][/I][/U]
Arg4: 0000000000000000, zero
DEFAULT_BUCKET_ID:  GS_FALSE_POSITIVE_MISSING_GSFRAME
SECURITY_COOKIE:  Expected 0000f9600039a255 found 8000f9600039a255
BUGCHECK_STR:  0xF7_ONE_BIT
CUSTOMER_CRASH_COUNT:  1
PROCESS_NAME:  firefox.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff96000372aba to fffff80002c831c0
STACK_TEXT:  
fffff880`085d9898 fffff960`00372aba : 00000000`000000f7 8000f960`0039a255 0000f960`0039a255 ffff069f`ffc65daa : nt!KeBugCheckEx
fffff880`085d98a0 fffff960`00209403 : 00000000`00000000 00000000`00000000 fffff880`085d9940 00000000`00000000 : win32k!_report_gsfailure+0x26
fffff880`085d98e0 fffff960`001afcdf : 00000000`00000005 00000000`00000052 00000000`003be430 fffff880`00000062 : win32k!xxxToUnicodeEx+0xf3
fffff880`085d99c0 fffff800`02c82453 : ffffffff`ffffffff 0000007f`ffffffff 00000000`00000000 00000980`00000000 : win32k!NtUserToUnicodeEx+0x187
fffff880`085d9bb0 00000000`7389056a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0027dd48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7389056a
STACK_COMMAND:  kb
FOLLOWUP_IP: 
win32k!_report_gsfailure+26
fffff960`00372aba cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  win32k!_report_gsfailure+26
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: win32k
IMAGE_NAME:  win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  5006fd0d
FAILURE_BUCKET_ID:  X64_0xF7_ONE_BIT_MISSING_GSFRAME_win32k!_report_gsfailure+26
BUCKET_ID:  X64_0xF7_ONE_BIT_MISSING_GSFRAME_win32k!_report_gsfailure+26
Followup: MachineOwner

was a one off and will not reoccur or we can continue trying to troubleshoot your issue.

Here is what Microsoft has to say about that particular Bug Check

These actions might prevent an error like this from happening again:

1. Download and install updates and device drivers for your computer from Windows Update.
2. Scan your computer for computer viruses.
3. Check your hard disk for errors.

SOURCE: Bug Check 0xF7: DRIVER_OVERRAN_STACK_BUFFER
Which is pretty typical of what they say about most Bug Check Codes.

But something corrupted or otherwise altered that GS Cookie by one bit. And it could be a bad driver, in which case you can attempt to use Driver Verifier and hope to catch and identify the offending process and if you choose to do so please read usama's fine article regarding the proper use of DV here Link Removed
OR it could be a faulty or failing hard disk in which case check your system disk for issues by using the native Check Disk Utility

Launch an elevated command prompt (StartOrb->All Programs->Accessories->Command Prompt, right click it and choose Run As Administrator) and type
chkdsk C: /R
hit enter and answer Yes “Y” when prompted and reboot.
Let it run all five stages. When complete check the log file in Event Viewer for results (Click the StartOrb and type event viewer and hit enter, expand Windows Logs and highlight / select Application, click Action on the menu bar and select Find and type chkdsk and hit enter.

OR it could be malicious software in which case use this program here What is Windows Defender Offline? (get the correct version for your system architecture) and read the page for instructions as to how to proceed.

OR it could be a bad memory module or potentially a motherboard memory slot in which case, as I suggested above

Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD from a cold boot after leaving it off for an hour or more.
Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.
See this Guide to using Memtest 86+

How you decide to proceed is up to you.
Regards
Randy

 

[Neutral]

Hi,
Sorry but I couldn't reply in meantime, had been busy a lot.
Anyway, I've installed nVidia Phsyx, and after installation I had a new BSOD.
I attached dump file.

 

[Neutral]

Can anyone please reply?

 

[usasma]

Since I'm new to this topic, I may miss some of the actions that were performed in previous posts. Feel free to let me know if something has already been done. And, just FYI, I have some severe eye problems - so I do occasionally miss things.

This is a STOP 0x124 error - which is primarily hardware based, but can be caused by low-level drivers.

You have had numerous BSOD's - and most seem to have been different errors. This is also a symptom of a hardware or low-level driver problem.

As such, I'll suggest that you update a few drivers - and then we'll (most likely) end up troubleshooting the hardware.

Please update your nVidia chipset drivers from the nVidia website. NVIDIA DRIVERS 15.49WHQL
If you've already done this, please let me know
If not, then un-install the current nVidia stuff from Control Panel...Programs...Uninstall a program - and then install the freshly downloaded drivers.

Unfortunately, these drivers came out around the time that SP1 for Win7 came out - and haven't been updated since. Yet, in the intervening time, Microsoft has issued a lot of updates. Keep this in mind as it may relate to the low-level hardware problems I talked about earlier.

You have an Adobe File System Driver that dates from 2008 - please remove it. It usually belongs to Adobe Reader - but check to be sure that it's gone after uninstalling it (it's usually located in C:\Windows\System32\drivers) DO NOT delete it manually!!! Post back if it's not removed.

Your Logitech keyboard drivers date from 2009 also - please update them and then check (I have heard that there are no later updates available). If the driver doesn't update, please uninstall the Logitech software and ensure that the driver is removed. Then use another keyboard temporarily to help rule that device out.

Once all of that's done - then it's time to start the free hardware diagnostics (if the BSOD's continue).
Please run all the diagnostics on this page: Link Removed - Invalid URL
Post back as soon as you get an error (or after you've finished all the tests without error)

[/INDENT]


Analysis:
The following is for information purposes only.

[font=lucida console]**************************Fri Oct  5 14:29:30.171 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\100512-27359-01.dmp]
Windows 7 Kernel Version [B]7601 [/B](Service Pack 1) MP (2 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 0:31:58.796[/B]
BugCheck Code: [B]BugCheck 124, {0, fffffa8004812038, f62a4000, 135}[/B]
Probably caused by :[B]AuthenticAMD[/B]
BugCheck Info: [B]WHEA_UNCORRECTABLE_ERROR (124)[/B]
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: [B]wmplayer.exe[/B]
FAILURE_BUCKET_ID: [B]X64_0x124_AuthenticAMD_PROCESSOR_CACHE[/B]
  BIOS Version                  P1.60
  BIOS Release Date             09/19/2011
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct  5 14:29:30.171 2012 (UTC - 4:00)**************************
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Fri Oct  5 14:29:30.171 2012 (UTC - 4:00)**************************
[B]adfs.SYS                    Thu Jun 26 16:52:37 2008 (48640195)[/B]
nvmf6264.sys                Thu Jul 30 19:48:18 2009 (4A723142)
nvstor64.sys                Tue Aug  4 20:31:07 2009 (4A78D2CB)
LGBusEnum.sys               Mon Nov 23 20:36:48 2009 (4B0B38B0)
amdiox64.sys                Thu Feb 18 10:17:53 2010 (4B7D5A21)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
nvstor.sys                  Fri Mar 19 16:45:11 2010 (4BA3E257)
LHidFilt.Sys                Fri Sep  2 02:23:09 2011 (4E60764D)
LMouFilt.Sys                Fri Sep  2 02:23:15 2011 (4E607653)
LUsbFilt.Sys                Fri Sep  2 02:23:19 2011 (4E607657)
AtihdW76.sys                Thu Feb 23 07:30:12 2012 (4F463154)
MpFilter.sys                Fri Mar  9 06:05:26 2012 (4F59E3F6)
atikmpag.sys                Wed Jul  4 01:10:55 2012 (4FF3D05F)
atikmdag.sys                Wed Jul  4 01:16:13 2012 (4FF3D19D)
[/font]

Link Removed
Link Removed - Invalid URL
Link Removed - Invalid URL
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed
Link Removed
Link Removed - Invalid URL
Link Removed
Link Removed - Invalid URL
Link Removed - Invalid URL