I attach dump files with the 2 latest crashes (+ all the others) which occured while I was doing absolutely nothing with my comp.
Unfortunately I have no other RAMs to swap with these at the moment.
Every time it's different modules that are reported as causing BSODs. This time WhoCrashed reports shareduserdata.sys...
Thanks.
Bump the 'VDDNB Over Voltage' to 1.350v.
D/L and run Seagate SeaTools – Short Drive Self Test and Long Drive Self Test. Should work on your Samsung HDD.
What is 'i view 32'?
Can't read any of your event logs, take a look at them and tell me what the 'Errors' and 'Warning' events are.
This crash is STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000003452, The subtype of the bugcheck. Arg2: 000007fefdedf000 Arg3: fffff70001084f98 Arg4: 9620000097426404 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_3452 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: taskhost.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002ef25f3 to fffff80002e83c80 STACK_TEXT: fffff880`0a777058 fffff800`02ef25f3 : 00000000`0000001a 00000000`00003452 000007fe`fdedf000 fffff700`01084f98 : nt!KeBugCheckEx fffff880`0a777060 fffff800`02e54942 : fffffa80`04261160 fffffa80`00000000 fffff8a0`00000156 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x356b3 fffff880`0a777910 fffff800`0315881a : fffff8a0`0bab5060 00000000`00000001 00000000`00000000 fffffa80`040f7060 : nt!MmCleanProcessAddressSpace+0x96 fffff880`0a777960 fffff800`0313a0d8 : 00000000`00000000 00000000`00000001 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x56a fffff880`0a777a60 fffff800`02e82f13 : fffffa80`04261160 fffff880`00000000 fffffa80`040f7060 00000000`00000001 : nt!NtTerminateProcess+0x138 fffff880`0a777ae0 00000000`774415da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0024fc48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774415da STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+356b3 fffff800`02ef25f3 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+356b3 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ecdc9f2 FAILURE_BUCKET_ID: X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+356b3 BUCKET_ID: X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+356b3 Followup: MachineOwner ---------
This driver is a bit concerning.
Can't find any reference to it.Code:tmp9720.tmp Sat Jul 26 21:29:37 2008
Last edited by Dave76; 15 Feb 2012 at 05:02.
i view 32 is irfan view picture viewer app
I will bump the voltage and run the seagate tools and report back
what do you mean by "I can't read any of your event logs" - the file is corrupted or the difficulty is in the language?
as for the driver, something similar (same date, but different file name) was found on page 3 of this thread here and my reply below that in fact i never had LoL installed on my pc and that the file itself was nowhere to be found.
one thing for sure, this is my last amd-based rig
Uninstall irfan viewer for testing, it's been crashing.
Language issue.
That driver is showing as loaded in the debugger, so it is there.
One possibility is that it's from a virus.
What Anti-virus are you using now?
If still Avira, uninstall it and run the Avira RegistryCleaner.
Download Avira RegistryCleaner
Then install MSE
Microsoft Security Essentials*- Free Antivirus for Windows
Update it through Windows Update.
Run a full scan.
Download and run Malwarebytes,
Update the virus definitions before running a full scan.
Thanks for replying Dave.
The drive passed all tests with this tool and reported no errors.
Uninstalled it, but if I continue, I would need to uninstall virtually everything on my PC, including windows explorer since it's been crashing as well :) together with loads of other native windows processes.
Should I translate what is in the $msinfo32.nfo file under windows error reporting contained in the griff zip?
I cannot find any reference to that either.
I stopped using Avira a few weeks ago after I was advised to do so
Done, with latest updates, nothing was detected.
Also done and also nothing caught.
I bumped the voltage as suggested. Seems like there's no pattern whatsoever for crashes. Which is true however, BSODs have become much more rare than before, it's mainly apps that crash randomly. Sometimes it's all good during 3-4 days, then all starts again without me making any changes.
Will need to get some other RAM to test, but spending 50-60EUR just to test remains quite expensive. I'd like some RAM please @ US and not EU prices :)
Another funny thing: OCZ states on their website that this RAM is dedicated for AMD 6.. and 7... chipsets...
Your previous CPUZ Mainboard tab is showing BIOS version 0802 and the Asus mobo site's latest BIOS version is 0801.
Where did you get the BIOS 0802 version?
That is good the crashes are becoming less, hope we are removing the drivers and apps that are causing or contributing to the crashes.
You may have to uninstall more apps until we find the cause. After your system is stable you can get new versions of the apps and install them a couple at a time, check for stability. Add or remove as needed.
Debugging is not a fine art, sometimes you can find the cause quickly and sometimes, well, it takes a while.
This could be an intermittent hardware fault or slight compatibility issue.
Usually RAM is the offending culprit, further down the list are graphics cards (or drivers), PSU and motherboard.
I have seen different RAM solve these kind of tough cases before.
Let us know if you get any more crashes.
Another method for determining applications causing crashes is to Troubleshoot Application Conflicts by Performing a Clean Startup.
Hi, the version you're referring to is for another MB, the M5A78L-M-USB3 ASUSTeK Computer Inc. - Motherboards- ASUS M5A78L-M/USB3, while mine is M5A78L/USB3 ASUSTeK Computer Inc. - Motherboards- ASUS M5A78L/USB3
To cut the story shorter (at least that's what I hoped, but read on) I got new RAMs: Corsair XMS3 - 8GB 1600MHz PC3-12800 DDR3 - 240 pin - 1.65V - CL9 - Kit: CMX8GX3M2A1600C9 - Komplett.be
At first the computer would not boot up, then it would after I reset the BIOS. All good so far, but once I launched memtest, it froze after a couple of minutes, so I rebooted and re-run it, it spit out errors and after 1hour or so, froze again.
BIOS sets the RAMs to 9-9-9-24 right away, which are the specification's speeds.
Symptoms are the same though, application crashes and a couple of BSODs as well. But again, nothing crashes under load, but on default settings and in low-resources consuming situations.
Starting to think it might not be a RAM issue after all? Unless this CPU/MB combination is so extremely picky on RAMs. Corsair guarantees full compatibility with all aMD and Intel systems and the sticks are on ASUS' qualified vendors list - although they list 2x2GB and not 4x4, I couldn't get the 2x2 anymore.
I cannot upload any dumps now, will do later. Any ideas will be more that appreaciated.
What is the RAM frequency?
If not 1333MHz then manually set it to that.
Manually set the RAM to manufacturers specs, 9-9-9-24 and Command Rate of 2T.
DRAM voltage to 1.65v manually.
Set the 'VDDNB Over Voltage' to 1.250v.
If that's not stable, we'll bump the CPU voltage a little.
Can you upload the CPUZ CPU tab under full load?
Go to 'CPU Over Voltage' and tell us the options there.
Start with a +0.10v.
Last edited by Dave76; 22 Feb 2012 at 07:11.
Hi Dave,
Didn't have time to reply these days, and to test.
So, the current situation is as follows: with the Corsair RAMs the PC won't even boot up - sometimes I can't even get to BIOS! And once I succeed, after lowering the speed to 1333 and setting the rest as suggested, Windows won't start, it just stays blocked on the "windows loading" screen and nothing happens.
I should stress that I reset the BIOS before putting new mems.
As I had stated before as well, the Corsair mems show errors in Memtest after a couple of minutes, and after another quarter of an hour, memtest freezes.
So I stuck back the OCZ, the PC boots up, but I'm still getting constant app crashes, but only a couple of blue screens.
So in the end it seems I'll have to RMA the corsair mems, but what puzzles me is that the problem actually could be with the MB and not RAMs - what do you think?
Damaged DIMM slots, short circuit on the MB, what else?
Thanks.
PS Will upload recent dump files and once I have some time, I'll translate the errors in the event log as precisely as I can.
I also noticed that when launching call of duty, every time it says "some parameters of your PC have changed since last usage, would you like to auto-adjust the settings?" although I don't change anything at all!
Starcraft suggests from time to time file corruption due to graphic problems, but I tested the GPU for several hours with a stress test, which showed no errors.
Seems like RAM settings are inconsistent and change randomly without me doing anything whatsoever.
MB fault? BIOS fault? RAM fault, I ran out of ideas.
Quote