|
Problem description: For about the last week I've been getting bluescreens (varied, but mainly MEMORY_MANAGEMENT or IRQL_NOT_LESS_THAN...) To begin with it looked like heat or bad memory, but it doesn't seem to be either. In fact the more I've tried to narrow in on what's going on, the wierder things have got. I now have a couple of leads that may be two problems or related: a bad driver, and a strange problem with sfc reporting the same files continually being corrupt. And I have no idea where to go from here. Attempted fixes: Chasing the "bad memory" idea I tried running Vista's Memory Diagnostics Tool. That reported I had bad memory, but then after I read up on MDT I reran with Memtest x86+ (to take Windows out of the loop) and that passed two 24 hour runs. CPUID Hardware Monitor shows voltages and heat are pretty stable Scanned for malware (MWB found nothing). So at this point I think - something in the OS has gone bad. So that's one problem I don't know what to do with. Second, I thought OK, if it's memory corruption *maybe* a driver has gone bad (kernel drivers live in shared memory and one bad one can corrupt the pool for everyone). Ran windows Driver Verifier telling it to hook all drivers. Straight away on loading Windows *bam* - ilokdrvr.sys bluescreens with BAD_POOL_CALLER. Again, searching the web I see people generally bemoaning the shittiness of iLok security dongles. I remove it so the driver doesn't get loaded and I can boot into Windows. I still however get a bluescreen after a few hours. So I can't say it's all the fault of that driver. So that's another problem, well, I can always just not use the dongle, I'm fine with that. I mention it at all because again googling on wdf01000 seems to suggest it's a core part of driver loading, and maybe the fact mine's screwed up is making my dongle driver throw a fit where it hasn't for the last year? I dunno. What I haven't done: Repair install, as I'm on SP2 and my install disks are SP1. Recent changes: Nothing hardware related. -- Operating system: Windows Vista Home Premium 64-bit SP2 System specs: Home built, Gigabyte EP45-DS, Intel E8400 C2D@3 Ghz, Memory is 2x1Gb of Crucial 2x1Gb of Corsair (don't have the model numbers but I can edit them in), Radeon HD 4870, System HDD is WDC WD5000 Edit: PSU is a Thermaltake Toughpower pushing something around 700/800w Location: UK I have Googled and read the FAQ: Yes HauntedRobot fucked around with this message at Mar 20, 2013 around 14:36 |
| # ? Mar 20, 2013 11:22 |
|
|
|
| # ? May 21, 2013 11:40 |
|
|
Did you by chance installed any new software lately? Software which is running on the background, another application you're using while the system is active?
|
| # ? Mar 21, 2013 00:11 |
|
|
No and that's the weird thing. If what I've read is correct, the memory_management error I'm getting suggests that it's kernel memory being corrupted. Either my hardware's flaking in a way that Memtest can't detect or I have a bad driver (or service? Something that runs in kernel mode anyway). Thought I'd solved it as I had 12 or so hours of uptime but it suddenly went in the middle of playing a game last night. So I'm going to run with verifier on again, which will hopefully force a bluescreen when the corruption happens, rather than hours later when the corrupted bit of memory gets hit again.
|
| # ? Mar 21, 2013 09:08 |
|
|
You could try to remove a memory module to test if it will solve the problem, if not remove the next and place the other back. Repeat this until you've found the broken module. Could be possible that memtest won't report any problems because the bits aren't corrupted until a certain temperature is reached or the corruption will only occur when all system resources are used.
|
| # ? Mar 21, 2013 12:53 |
|
|
Rz666 posted:You could try to remove a memory module to test if it will solve the problem, if not remove the next and place the other back. Repeat this until you've found the broken module. Could be possible that memtest won't report any problems because the bits aren't corrupted until a certain temperature is reached or the corruption will only occur when all system resources are used. On this note, try memtest with various combinations of individual sticks in individual slots. It could also be a videocard issue. For completeness, it's always worth posting a screenshot of Crystal Disk Info in case it's a pagefile memory issue or similar.
|
| # ? Mar 22, 2013 14:47 |
|
