| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 79440 | 2007-05-20 06:03:00 | Another annoying BSOD error with no apparent cause | Agent_24 (57) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 551350 | 2007-05-23 06:40:00 | I've run memtest, 2 passes no errors. I shall let it run longer but I don't think the ram would generate the exact same error every time |
Agent_24 (57) | ||
| 551351 | 2007-05-23 06:43:00 | Ok, so what's the best way to go about dealing with the damn thing? Get a --> :badpc: |
Speedy Gonzales (78) | ||
| 551352 | 2007-05-23 06:44:00 | Get a --> :badpc: As a matter of fact I just tried that, got a HAMMER_STUCK_IN_CHASSIS_TRAP error.... |
Agent_24 (57) | ||
| 551353 | 2007-05-23 06:48:00 | You could try the Search button and enter the IRQL_NOT_LESS_OR_EQUAL string, and go through the threads that finds. One posting quotes the full message from MS, which implicates drivers. But a few people found memory problems ... There might be something. |
Graham L (2) | ||
| 551354 | 2007-05-23 07:11:00 | Hmm this might help (support.microsoft.com) If u can find this pstat file (which by the looks of it is in a resource kit). Its a command, and if u type pstat (that 0x8 error at the end of your BSOD), it'll tell u the driver thats using this address. And will most probably point you to the driver thats giving the BSOD. |
Speedy Gonzales (78) | ||
| 551355 | 2007-05-23 07:19:00 | Did you install any supplied drivers for the monitor? Is the new monitor quite similar to the old one? More information on Stop 0x0A errors here (support.microsoft.com). |
Jen (38) | ||
| 551356 | 2007-05-23 07:33:00 | As a matter of fact I just tried that, got a HAMMER_STUCK_IN_CHASSIS_TRAP error.... heh :D |
stu161204 (123) | ||
| 551357 | 2007-05-23 07:39:00 | Its always a driver error, occasionally a RAM error. It may not be the graphics driver at all, could be something else. |
pctek (84) | ||
| 551358 | 2007-05-23 07:57:00 | Hmm this might help (support.microsoft.com) If u can find this pstat file (which by the looks of it is in a resource kit). Its a command, and if u type pstat (that 0x8 error at the end of your BSOD), it'll tell u the driver thats using this address. And will most probably point you to the driver thats giving the BSOD. Comes in a pack from microsoft "Windows XP Service Pack 2 Support Tools (www.microsoft.com)" (validation required) in case anyone else wants the link. I'm going to check it out in a minute and see what's happening... Did you install any supplied drivers for the monitor? Is the new monitor quite similar to the old one? The new monitor is totally different, windows is using the generic "plug and play" monitor driver - The old monitor was a Philips 105/S and the new one - well you tell me. I'm going to upload a photo of the back sticker for anyone who wants to have fun trying to identify it. "new" monitor sticker (www.imagef1.net.nz) |
Agent_24 (57) | ||
| 551359 | 2007-05-23 08:11:00 | Looks like its a Microvision monitor (www.trademe.co.nz) Its got the same sticker as the one u posted. |
Speedy Gonzales (78) | ||
| 1 2 3 4 5 | |||||