- Thread Author
- #1
Usually happens when i play games, pc seems to reset a lot ,
windows 7
intel i5
giggabyte motherboard
8 giggs of ram
windows 7
intel i5
giggabyte motherboard
8 giggs of ram
[font=lucida console]**************************Sun May 12 17:15:43.312 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\051213-10233-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 2:31:27.139[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!ExDeleteResourceLite+b8 )[/B]
BugCheck [B]3B, {c0000005, fffff80002c71d18, fffff88005cd5580, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002c71d18, Address of the instruction which caused the bugcheck
Arg3: fffff88005cd5580, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR: 0x3B
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: explorer.exe
FAILURE_BUCKET_ID: [B]X64_0x3B_nt!ExDeleteResourceLite+b8[/B]
CPUID: "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed: 3400
CurrentSpeed: [B]3403[/B]
BIOS Version F6
BIOS Release Date 05/31/2012
Manufacturer Gigabyte Technology Co., Ltd.
Product Name To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun May 12 13:17:59.733 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\051213-8595-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 1:41:23.936[/B]
Probably caused by :[B]fileinfo.sys ( fileinfo!FIStreamLog+89 )[/B]
BugCheck [B]3B, {c0000005, fffff800030141c0, fffff88002898680, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800030141c0, Address of the instruction which caused the bugcheck
Arg3: fffff88002898680, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR: 0x3B
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: RapportMgmtSer
FAILURE_BUCKET_ID: [B]X64_0x3B_fileinfo!FIStreamLog+89[/B]
CPUID: "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed: 3400
CurrentSpeed: [B]3403[/B]
BIOS Version F6
BIOS Release Date 05/31/2012
Manufacturer Gigabyte Technology Co., Ltd.
Product Name To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun May 12 09:47:53.353 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\051213-8252-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 2:38:10.555[/B]
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by :[B]igdkmd64.sys ( igdkmd64+32e61c )[/B]
BugCheck [B]50, {fffff8a00d365298, 1, fffff880043ab61c, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: fffff8a00d365298, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff880043ab61c, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
BUGCHECK_STR: 0x50
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x50_igdkmd64+32e61c[/B]
CPUID: "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed: 3400
CurrentSpeed: [B]3403[/B]
BIOS Version F6
BIOS Release Date 05/31/2012
Manufacturer Gigabyte Technology Co., Ltd.
Product Name To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]
[font=lucida console]**************************Sun May 12 17:15:43.312 2013 (UTC - 4:00)**************************
intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
SASKUTIL64.SYS Tue Jul 12 17:00:01 2011 (4E1CB5D1)
SASDIFSV64.SYS Thu Jul 21 19:03:00 2011 (4E28B024)
L1C62x64.sys Wed Aug 3 02:21:09 2011 (4E38E8D5)
[COLOR=RED][B]AppleCharger.sys Tue Nov 1 22:46:00 2011 (4EB0AEE8)[/B][/COLOR]
RTKVHD64.sys Tue Jan 17 06:14:33 2012 (4F155819)
iusb3hub.sys Tue Mar 27 04:09:29 2012 (4F7175B9)
iusb3xhc.sys Tue Mar 27 04:09:32 2012 (4F7175BC)
HECIx64.sys Mon Jul 2 18:14:58 2012 (4FF21D62)
MpFilter.sys Wed Oct 31 18:43:06 2012 (5091A97A)
igdkmd64.sys Wed Dec 12 19:42:26 2012 (50C92472)
RapportCerberus64_51755.sys Wed Mar 6 06:28:28 2013 (5137285C)
RapportKE64.sys Mon Apr 29 18:26:27 2013 (517EF393)
RapportEI64.sys Mon Apr 29 18:26:41 2013 (517EF3A1)
RapportPG64.sys Mon Apr 29 18:26:42 2013 (517EF3A2)
[/font]
1) That the SSD firmware is the latest available for the SSD
2) That the storage controller drivers on the motherboard are the most recent. They must date from late 2012 or later. This is ALL controllers, not just the one that the SSD is attached to.
Only 106 Windows Updates installed. Most systems have 160 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).
E: drive only has about 2% free space; F: has about 5%. Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance. Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty)
SSD's were temperamental when they first came out, but their reliability has improved greatly over the last year or two. There are 2 things that MUST be checked on systems with BSOD's and SSD's:
We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:
There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.
Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website). Be sure to update ALL controllers on the motherboard! I STRONGLY suggest not using controller drivers older than mid-2012 with SSD's.
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
- Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
05 Jan 2013 - very interesting post about difficulties with the Marvell controllers even when not connected to the SSD drives: Solved Win8 x64 PC reboots when waking from sleep
27 Feb 2013 - I'm starting to see much better reliability with SSD's using current (mid-2012 and later) storage drivers. I have withdrawn my objections to using these devices in everyday systems.
If the firmware needs updating and you don't update it - it may be the reason for your BSOD's
It'll never get easier to reinstall your Windows installation than it is today - your call.
Here's the long spiel on SSD's and BSOD's:
The number of Windows Updates is an estimate - each system requires a different number of them.
As long as you've checked repeatedly, then it's probably good.
The OS is on your primary drive, the OS is what runs the games - so it is being used.
The reports that I requested will allow me to see if there are other issues that may be causing problems. In quite a few cases systems will black screen/freeze after we've started fixing BSOD's.
Please provide this information so we can provide a complete analysis (even though it's not BSOD'ing at this time): Link Removed
Also, Please do the following:
- open Event Viewer (eventvwr.msc)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on Administrative Events
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).
Please provide this information so we can provide a complete analysis (even though it's not BSOD'ing at this time): Link Removed
Still need this:
Have you run the hardware diagnostics that I suggested? If so, what were the results?
i got all malware and spyware protection, looked at hardware diagnostics and went to the website for my ssd, no help at that site, on memory test it said on the page that the links were not very good now to do the test, i think i'll just buy some more ram and free up some space on my secondary drivesSorry, my mistake - I skipped re-reading the entire post and tried to just remember what I'd seen.
The admin event viewer stuff shows errors that can be related to hardware or malware.
Have you run the hardware diagnostics that I suggested? Included in that link is a listing of free malware scans.
Here's the link again in case you need it: Link Removed
Please let us know the results
It's probably better to run the diagnostics before updating the firmware on the SSD - that way if you find a hardware problem you may be able to avoid the firmware update process (if it stops the BSOD's).
Good luck!
Please run the hard drive diagnostics on your other hard drives. To make it easy, you can run the Seatools Long test on all drives: SeaTools for DOS | Seagate
As for the memory diagnostics, please run the MemTest86+ from here: Memtest86+ - Advanced Memory Diagnostic Tool
Thanks for that link, i dont know if i downloaded the right one but it said my agility ssd (and the other drives) were all in good health,You have 3 hard drives in your system.
SeaTools will not work on the SSD
Run SeaTools on the other 2 hard drives
As for the OCZ SSD, use the tools from OCZ.
If none are available, use this free test: Software - Crystal Dew World
Yep, RED in MemTest86+ is a sign of bad memory.
Finish up the steps here (from #6 onwards) to help isolate which sticks/slots are at fault: Link Removed