Message boards :
Number crunching :
Blue Screen:REFERENCED_BY_POINTER - what could be the reason?
Message board moderation
Author | Message |
---|---|
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
My main cruncher started to reboot itself recently. When I disabled auto-restart I saw BSoD with REFERENCED_BY_PINTER bugcheck message. AFAIK no system-wide updates were done immediately before these reboots begin. Anyone encountered this type of BSoD and what were the reasons (I read MS article about ref/deref mismatch, but don't know what driver cause this)? SETI apps news We're not gonna fight them. We're gonna transcend them. |
Highlander Send message Joined: 5 Oct 99 Posts: 167 Credit: 37,987,668 RAC: 16 |
only one question Raistmer: do you use a NDAS? - Performance is not a simple linear function of the number of CPUs you throw at the problem. - |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
only one question Raistmer: do you use a NDAS? If NDAS is Network Direct Attached Storage then no, don't use. SETI apps news We're not gonna fight them. We're gonna transcend them. |
Lazydude Send message Joined: 17 Jan 01 Posts: 45 Credit: 96,158,001 RAC: 136 |
If you are using dumpfiles: This is a set of tools for analyse of what happend. Look at "Who Crashed". http://www.resplendence.com/downloads Hope this will help you |
Morten Ross Send message Joined: 30 Apr 01 Posts: 183 Credit: 385,664,915 RAC: 0 |
First of all you should ensure only minidumps are created, as full memeory dump is not necessary unless third party needs it to create a fix. I've used BluescreenView for many years as it's to the point to quickly find which drivers were loaded. Some more URIs on the topic here on MSDN. Morten Ross |
janneseti Send message Joined: 14 Oct 09 Posts: 14106 Credit: 655,366 RAC: 0 |
If it is your computer with AMD Radeon HD 6900 series which are malfunctioning, it is perhaps the same problem I have had for a long time. It started with Catalyst version 12.4 that made my computer started BSOD with the error message REFERENCED_BY_POINTER sometimes. But when I recently upgraded to version 12.10, it seems that the problem has disappeared. I have now been using the driver for over a week without BSOD occurs. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Thanks all for suggestions. Will try to implement them. Regarding HD6950 - yes, it's that host. But driver installed long time ago (Cat 12.6). Some time ago there were often reboots, then I reduced number of running simultaneously tasks to 1 they gone. Recently I set again 2 tasks simultaneously and that config worked for week or even more. But now restarts (and BSoDs now, when restar was disabled) go too often to do anything useful on that host. SETI apps news We're not gonna fight them. We're gonna transcend them. |
SciManStev Send message Joined: 20 Jun 99 Posts: 6652 Credit: 121,090,076 RAC: 0 |
When that happened to me this summer, it was because I had run the CPU at 1.47 VDC for about 3 years at 4.2 GHz, and eventually fried the CPU. I orginally thought it was a Window update, then the hard drive, then the RAM, then the motherboard. I knew it wasn't the PSU, so all that was left was the CPU. I replaced the i7 980 with an old i7 950, and it worked just fine. I really do miss that unlocked multiplier though.... Steve Warning, addicted to SETI crunching! Crunching as a member of GPU Users Group. GPUUG Website |
janneseti Send message Joined: 14 Oct 09 Posts: 14106 Credit: 655,366 RAC: 0 |
Try upgrade your drivers. Your are using OpenCL 1.2 AMD-APP (938.1) which in my case causes problems. I'm using OpenCL 1.2 AMD-APP (1016.4) right now without problems. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
When that happened to me this summer, it was because I had run the CPU at 1.47 VDC for about 3 years at 4.2 GHz, and eventually fried the CPU. I orginally thought it was a Window update, then the hard drive, then the RAM, then the motherboard. I knew it wasn't the PSU, so all that was left was the CPU. I replaced the i7 980 with an old i7 950, and it worked just fine. I really do miss that unlocked multiplier though.... It's Q35M motherboard w/o any overclocking features... And fan replaced from stock to Titan long time ago. CPU temp quite low and moreover, host lack of CPU work last few days... and still hangs. So, probably something else in my case. SETI apps news We're not gonna fight them. We're gonna transcend them. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Try upgrade your drivers. I will leave it as is through night with mini-dumps enabled. Maybe I will catch faulty AMD driver to rise the case with their support once again... Then will do update. [Not sure update it should be or rollback though. Just discovered that app built with old APP SDK 2.5 faster than built with APP SDK 2.6 ... And will support much more hosts ...] SETI apps news We're not gonna fight them. We're gonna transcend them. |
Mike Send message Joined: 17 Feb 01 Posts: 34258 Credit: 79,922,639 RAC: 80 |
Try upgrade your drivers. And will cause much more trouble because all those buggy drivers. With each crime and every kindness we birth our future. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Looks like motherboard for that host is completely dead now. After another BSoD it refused to reboot. Starts and stops CPU and system fans in loop. I removed already all but CPU itself.... Even replaced PSU with old one. Same behavior. Now when PSU switched ON (by own hard switch) it sometimes starts to spinup system and CPU fans few times sometimes even not start at all. No reaction on "Power" button pressing (on the front side of case). Before this motherboard performed short fans and HDD spin up when PSU power ON then turned off awaiting power button press. SETI apps news We're not gonna fight them. We're gonna transcend them. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
After motherboard replace same BSoD happened again. But now it was catched! WhoCrashed gave next info:
So, it's AMD crappy driver again... SETI apps news We're not gonna fight them. We're gonna transcend them. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.