New
#31
Any updates, how did it go?
I ran MemTest for 16 hours or something and it failed; as this was the second memory failure in less than a year and everything is still under guarantee, I sent the whole system back for the manufacturer to have a look at. As I suspect there might be more to it than just memory failure.
Thanks for the update :) .
If you feel the issue is solved please mark the thread as so.
P.S.
Be sure to update on their findings :) .
OK, I am back. :/ They replaced the memory and did whatever bench testing they do and it ran fine for them.
However, within two hours of me using it I have had a crash.
There is also a number of items in event viewer:
Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4
Faulting module name: SHELL32.dll, version: 6.1.7601.18222, time stamp: 0x51f1ddfa
Exception code: 0xc0000005
Fault offset: 0x000000000009a809
Faulting process id: 0x848
Faulting application start time: 0x01cefd101aa88a48
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: C:\Windows\system32\SHELL32.dll
Report Id: 8a946bd5-6903-11e3-828e-14dae90f7e20which I have never encountered before and don't really understand.Possible Memory Leak. Application (C:\Windows\System32\svchost.exe -k LocalServiceNetworkRestricted) (PID: 1164) has passed a non-NULL pointer to RPC for an [out] parameter marked [allocate(all_nodes)]. [allocate(all_nodes)] parameters are always reallocated; if the original pointer contained the address of valid memory, that memory will be leaked. The call originated on the interface with UUID ({3f31c91e-2545-4b7b-9311-9529e8bffef6}), Method number (20). User Action: Contact your application vendor for an updated version of the application.
Would really appreciate your help.![]()
I also have this coming up in the event viewer fairly regularly.
And Windows Explorer crashed again, seemingly random.Code Integrity determined that the page hashes of an image file are not valid. The file could be improperly signed without page hashes or corrupt due to unauthorized modification. The invalid hashes could indicate a potential disk device error.
File Name: \Device\HarddiskVolume1\Windows\System32\sxs.dll
Here is what I have done so far -
1. Sfc / scanow - no issues to report.
2. Scanned the C drive for problems, which came up clear.
3. Malware-Antibytes scan. TDSS Killer scan, both fine.
What did you have running during that time?
Please export and upload your system event log.
Start → type eventvwr → hit Enter.
- Toggle open the triangle to the left of Windows Logs, right-click on System and choose Save All Events As...
- A dialogue box will pop up asking you to name the file and select the save directory, name the file the same as your Seven Forums user-name and save it to the desktop.
- A second dialogue box will appear asking you to select the Display Information, select Display information for these languages and check the box next to English (if you don't have English automatically offered check the box at the bottom to display additional languages - Show all available languages and check English).
- Wait a few moments until the cursor returns to normal. The file will now be on your desktop (given it's the directory it was saved to) UserName.evtx, next to it there will be a folder called LocaleMetaData select both the .evtx file as well as the folder and compress them using Winrar / 7zip and attach it in your next post.
The bug check is again a TDR, you can see back in post #16.
This is what I usually post to try and troubleshoot a TDR, some of it we already gone through
but a long time has passed since as well.
What you're experiencing is called a TDR (Timeout Detection Recovery) is not a bugcheck in the true sense in that somethingCode:VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed.
has went terribly wrong in the kernel which forced the machine to crash.
Please roll-back your nVidia drivers to a known stable release:
Note- Don't install GeForce Experience -
Reset the BIOS back to default:
NoteWrite down the current value of the SATA Mode!
Its either AHCI or IDE.
After resetting the CMOS go back and verify the value for SATA Mode is what it was
when the OS was installed.
If any component is overclocked reset it back to stock speeds!
What is the make, model and age of your PSU?
Fill out this form and post back the result:
Test for thermals and stability:
- Download HWinfo and post a Screenshot of the sensors window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.
- Before running Prime95 make sure to enable Round-off checking (see 1st post under the tutorial).
NoteIt is not mandatory to run both tests simultaneously, although possible as long as the temperatures are under constant monitoring.
Testing the RAM:
When done with the testing procedure take a picture and upload it here.
This will help you to determine where the issue is origination from (if any):
Post back with the results.
Thanks YoYo. At the time, I was running DayZ and it crashed after around an hour and a half of playing. At the time, the GPU temperature was about 70 degrees.
The system seems stable enough, I have not stopped using it in terms of doing day to day tasks. But I have not played any games since the crash.
The rest of the errors that I have seen in the Event Viewer, haven't really manifested themselves in anything as of yet. Except the two cases of 'Windows Explorer' crashing, which was then restarted and was ran fine. The MSE error in event viewer appears everytime I boot. I guess I should probably try a reinstall.
Anyway, I have attached the log you requested and will work through the rest of your post.
Hi I found this,
Code:The description for Event ID 17 from source mv91xx cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: 0
Start menu → type: devmgmt.msc (Hit enter).
- Take a screenshot and attach it in your next post.
Other than that I don't see something out of the ordinary, yet the log has been reset on the 18th.
Is there anything you want me to expand in device manager?
I'm looking for entries with yellow triangle/exclamation points, if you have any of those then double clicking them and taking a screenshot of the General Tab would also help.