Im trying to gather data about the crashing issue r2 owners can encounter. Because this is after a solution versus just reporting the problem, instead of continuing to reply deep in that thread which no one looks at. I felt it is time to make a thread just for this discussion.
See this thread.
http://forum.notebookreview.com/ali...ing-lockups-crashes-discussion-thread-31.html
I have looked elsewhere on other forums from WOW to Dells own and it seem the answer is the motherboard replacement.
However, earlier attempts at motherboard replacements in 2010 failed to solve the issue and I believe I know why. They were sent the same revision of the motherboard they already had.
In attempt to verify this. For those willing.
1. Open the bottom of your system and look next to the memory. Near the heatsinks you will see parts of revision numbers (covered by the heatsinks unfortunately) as well as the manufacturing date.
Post these if you have this problem and had to downclock, or if you replaced your motherboard and it worked or failed.
Sample:
Exhibits the aforementioned crashing (ctl/alt/del - cannot end process): Yes
Date seen: 4/19/2010
Rev seen (part): 1 or 1E
2. Now this part may be unrelated and the same for all. Download GPU-Z.
Download TechPowerUp GPU-Z v0.5.3 | techPowerUp
Post your results (free upload tool with the program).
Specifically looking at what revision of the 335m included.
![]()
(Note revision A2, which may or may not be for the 335m in particular, or just signifying the A2 is the 335m version of the GT215 chip.)
-
-
Bump. Can anyone give their revision numbers on the motherboard (again, revision number under the r2 line. NOT speaking about the r1-r3 general revisions).
-
My GpuZ says that it's revision FF, so maybe it's just GPU revision not mainboard
-
Thats a good start. Is yours showing any of the crashing?
Even if its the gpu itself, still requires a new MB. -
About the crashing or lockup, I also experience things like that before. On the first and second month after purchased, my m11xR2 i5 lockup-ed once or twice per week. I tried many solutions like disable the auto power off of wifi, update the windows, etc... and then, the lockup has just gone. Actually, it only happens once per 3-4 weeks.
Now I'm thinking maybe the hard disk protection software causes the problem. -
Yea its not the same issue. It been settled upon the GPU. I have plenty of windows dump files showing the nvidia causing it. I also have other threads showing people that got their MB replaced not having the issue anymore. Which to me points to a revision of the GPU thats at fault. Especially since I can underclock the GPU and not crash.
Here is link to good software to discern dmp files. Though only BSOD ones not just programing crashing.
http://www.resplendence.com/whocrashed -
Hey,
I have the FF revision model, and I have nvlddmkm.sys issue with the 270. xx driver. Still, with the other drivers, I still have this issue as I have to manually force my PC to close after CTRL+ALT+DELETE out of the game. Do you guys think I have the motherboard issue?
Thanks -
I have the same as you, A2, and I do crash with 270 series of drivers but not the 260 series. (Been running 260.99 and 267.76 for about a month now to make sure)
-
-
I run tons of games. All are fine. Ill just post a pic of my steam list because its too long to type. All of them work on 260series.
Attached: List of games.Attached Files:
-
-
I don't know what to say then. Maybe it is motherboard related versus gpu as the 260 still could crash with the process not being able to be closed. Even more, since they are older, cause graphical glitches (example sometimes inverted colored zombies in l4d2).
On top of that downclocking as described did fix it with all driver revisions.
If you do feel confident. Maybe you could open up the bottom and look where I describe above to see what it says about your manufacturing date and motherboard revision? -
Thats what I am saying it DOESNT crash on the 260. It does on the 270. So I imagine its driver related.
-
-
Bump, DeeVu did in fact get crashes in 260 with WOW and is trying a new motherboard (with same revision of GPU unfortunately).
So we need a larger sample of people posting their GPU revision and how its working. -
Now it gets weirder. Look at the posting of the FF version. I put my a02 next to it as comparison. Note, his is a newer version of the program, so possibly glitch?
Anyhow he has confirmed the FF version is not showing the crashing he had before.
So straight across.
A02:72 Shaders and 8 Rops
FF: 384 Shaders and 32 Rops
The 335M is spec'ed for only 72. -
I have the A2 revision and mine has shown the same incorrect numbers a couple of times as well. I would guess it is something wrong with GPU-Z. If it does it again I will take a screenshot of it.
-
I noticed that when mine displays correctly, it says A2. I got it to display incorrectly again and when it does it says FF. It is GPU-Z that is not displaying the correct info.
Edit: Another pic displaying correctly. -
Really? DAMN! Well there goes that theory down the toilet. Ok, then the next idea is again for those willing. Open the bottom and look near your memory at the motherboard. You will see revision numbers and build date. Please let me know what they are since it sounds like the GPU revision itself isnt the cause. I know for one mine was a very early build.
-
-
I haven't been able to get mine to show A2, it always shows FF as the revision.
Even weirder is the Pixel and Texture fillrate.. (I have mine slightly overclocked but I don't know if that has anything to do with it.)
M11X R2 Motherboard Revisions - Related to crashing issue.
Discussion in 'Alienware M11x' started by potentiality, Jun 27, 2011.