Windows 7: Blue screen error Help please

iandxb · 11 Feb 2012

I am getting occasional Blue screen errors with the computer shutting down unexpectedley. I have attached the dump file as per the instructions. I would appreciate any help in solving this issue.

Thanks.

usasma · 11 Feb 2012

SP1 isn't installed, please do the following:

Quote:

Installing Windows 7 Service Pack 1
1. Visit the PC manufacturer's website and update ALL drivers. DO NOT use Windows Update or the "Update drivers" function of Device Manager.
2. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)
3. Visit Windows Update and get all updates
4. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center
5. Visit Windows Update and get any other available updates

Asus Bluetooth is disabled. Is this deliberate? If so, why?
Please re-enable the device, update it's drivers, then disable it again (if so desired)

If it's not the Service Pack causing the issues, then it's likely a hardware problem. Please start with these free hardware diagnostics: Hardware Diags

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs:
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.

Code:


jraid.sys     Tue Aug 10 05:28:44 2010 (4C611BCC)
amdxata.sys   Tue May 19 13:56:59 2009 (4A12F2EB)
MpFilter.sys  Wed Apr 06 16:07:29 2011 (4D9CC801)
asmtxhci.sys  Wed Dec 08 05:14:06 2010 (4CFF5A6E)
atikmpag.sys  Tue Apr 19 21:22:32 2011 (4DAE3558)
HECIx64.sys   Tue Oct 19 19:33:43 2010 (4CBE2AD7)
e1c62x64.sys  Tue Sep 21 17:34:15 2010 (4C9924D7)
btath_bus.sys Thu Jun 24 02:17:43 2010 (4C22F887)
AtihdW76.sys  Wed Nov 17 07:02:04 2010 (4CE3C43C)
atikmdag.sys  Tue Apr 19 21:53:29 2011 (4DAE3C99)
NuidFltr.sys  Fri Apr 08 18:58:16 2011 (4D9F9308)
RTKVHD64.sys  Tue Nov 23 05:14:08 2010 (4CEB93F0)
asmthub3.sys  Wed Dec 08 05:14:14 2010 (4CFF5A76)
dc3d.sys      Wed May 18 04:07:24 2011 (4DD37E3C)
NisDrvWFP.sys Wed Apr 06 16:08:53 2011 (4D9CC855)
MpNWMon.sys   Wed Apr 06 16:07:23 2011 (4D9CC7FB)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\020912-23556-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu Feb  9 11:05:52.824 2012 (UTC - 5:00)
System Uptime: 13 days 0:11:26.917
Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+87 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+87
Bugcheck code 0000000A
Arguments fffffa80`27f2c130 00000000`00000002 00000000`00000001 fffff800`02d7a7b7
BiosVersion = 0501
BiosReleaseDate = 05/09/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012712-21418-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Jan 27 10:49:13.030 2012 (UTC - 5:00)
System Uptime: 0 days 8:36:40.012
Probably caused by : Ntfs.sys ( Ntfs!NtfsFcbTableCompare+3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dllhost.exe
BUGCHECK_STR:  0x24
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsFcbTableCompare+3
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`07b21c88 fffff880`07b214f0 fffff880`01306173
BiosVersion = 0501
BiosReleaseDate = 05/09/2011
CPUID:        "Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

iandxb · 12 Feb 2012

thanks usasma,

I have installed service pack 1 and checked the bluetooth driver is up to date(which it was). Before I do anything else I will use the computer and see how it runs.
The next step will be to run the hardware tests, I have run out of time today so will do it tomorrow.
Could you tell whether it was a hardware problem?

usasma · 12 Feb 2012

You have to run it a while to see if the Service Pack and the bluetooth updates have fixed it.

You can start with the hardware diagnostics if you'd like - that way you'll be ahead of things if the system BSOD's again.

iandxb · 15 Feb 2012

Computer crashed badly about 2 hours after the update. I couldn't get it going again. I took it back to the shop and they did some tests and found the motherboard faulty. Their theory is the graphics card overheated. it was a xfx radeon hd687 2gb gddr5. can't understand why it would overheat, all i was doing was screen sharing on skype, no games. could this be the cause of the original BSOD errors?
The shop have fitted a new motherboard and graphics card(Palit GE force GTX 560 Ti 2048mb gddr5). it has 2 fans, that was their thinking behind the change of graphics card.
Thanks

usasma · 15 Feb 2012

There's many reasons for a graphics card overheating. The hardest to diagnose (that I've seen) was one where the heat sink didn't make contact with the GPU. We worked on that system for 2 weeks until my hand accidentally brushed up against the video card. The resulting second degree burn convinced us that it was the video card overheating.

iandxb · 15 Feb 2012

That was what got the technicians attention when he burnt his finger on it. Time will tell, i'll see how it runs over the next week.
Thanks