Solved Random BSOD error 0x0000003b and 0x00000024

[Vir Gnarus]

Hello
Sorry for my late reply. Have been away from home. Anyway are u saying that even after playing games like medal of honor warfighter and battlefield for hours ( both demanding games) the temperature of my cpu & gpu shouldnt reach 65 C ? Sorry but what u are saying contradicts all i know about heat & pc. I never said that 65 C is "alarming" for my system, just that i dont like it going any higher . Anyway why are we even discusing the temperature of my pc? As i have stated in my previous posts the BSOD never occurs while i am playing games ( when the temperature of my pc is higher than normal ) but during startup, while browsing folders and surfing on the net- in other words when my pc temperature is normal 40-42 C. I hope we have that clear now.
More than 24 hours have passed since i activated driver verifier and nothing has happened. Should i leave verifier on till a BSOD happens? This question will sound stupid but i have to ask : do i have to enable driver verifier every time i turn my pc on again?

65C for a GPU isn't anything much to worry about, and 65C for a CPU is pushing it to where it'll age the CPU faster, but you're right, there's nothing here with the temperature that says it should cause these BSODs, nor is it a problem for the immediate health of the system (though 65C for CPU is pretty high). Rather, it really depends on if you are comfortable with those temperatures. If not, you'll want to step it up on the cooling a bit to make sure it doesn't reach that point. Temperature just shouldn't be something that you should be thinking about when using your system. A truly stable system is one that can be pressured for any length of time by the applications it's running without the user having to worry about it breaking down from the stress, and it appears yours just hasn't quite reached that level. I'm just saying this for your own sanity; you'll feel a lot better not having to worry about temp unless something bugs out like a fan, in which case that is when you'll have HWMonitor/Speedfan ready to alert you before it actually becomes an issue for the health of your system.

Anyways, Driver Verifier, once setup and the system restarted afterwards, will stay 'on' permanently unless you go in and manually turn it off, or you use System Restore to restore it to a point prior to DV being activated. Driver Verifier itself is really just a frontend for setting up extra driver checks built into Windows that are used for diagnostic purposes. It just makes Windows more paranoid with what drivers are doing, and if it find problems, it will do what it usually does when it finds one, and that is BSOD. The crashdumps generated from it will help us pinpoint the problem better.

What you'll want to do is just turn on Driver Verifier, restart the PC, verify it's on by going into Command Prompt and typing verifier /query or open DV again and select "Display existing settings", and once you find it's successfully on and going, just use the computer as normal. If it crashes again, provide us the crashdump. Obviously because of the extra checks, things may end up running a bit slower, so you'll have to deal with that.

The concern I have is that if DV has been on and hasn't 'found' anything yet, is that it may be hardware related, in which no amount of driver checks is going to discover. Of course, I'm crossing my fingers on it being the AVG/Spybot (wouldn't doubt it on AVG, it's done it to others before).

 

[dmc1986]

Hello
U are right about temperature. For the cpu 65 C is high but not near overheating ( i heard its around 80+ C when it gets dangerous) but for the time being it will have to suffice. Once i gather money for a new pc, i wont rely on intel's integrated coolers anymore but get a custom one from noctua . Thanks for the useful info. As for the dv i will leave it on till tommorow 7 pm and then, if nothing happens, turn it off.
If the BSOD continues after that then its most likely hardware. Well i added 2 gb of ram prior to installation of windows 7. Maybe i have installed it in the wrong slot? The fist slot was occupied, i left the second slot free and installed the new ram in the third slot. Maybe i shouldnt have skiped a slot? Thats the only hardware change to my pc since i bought it in 2009. I havent run memtest86 since i heard it isnt really reliable. Will keep you updated.

 

[Vir Gnarus]

Hello
U are right about temperature. For the cpu 65 C is high but not near overheating ( i heard its around 80+ C when it gets dangerous) but for the time being it will have to suffice. Once i gather money for a new pc, i wont rely on intel's integrated coolers anymore but get a custom one from noctua . Thanks for the useful info. As for the dv i will leave it on till tommorow 7 pm and then, if nothing happens, turn it off.
If the BSOD continues after that then its most likely hardware. Well i added 2 gb of ram prior to installation of windows 7. Maybe i have installed it in the wrong slot? The fist slot was occupied, i left the second slot free and installed the new ram in the third slot. Maybe i shouldnt have skiped a slot? Thats the only hardware change to my pc since i bought it in 2009. I havent run memtest86 since i heard it isnt really reliable. Will keep you updated.

You'll often want to skip a slot when the motherboard has 4 slots, as the slots actually go by 1-3-2-4 instead of 1-2-3-4, because of the extra channel stuff. Consult your system manual to make sure. Otherwise, if you do skip a slot when you're not supposed too (like putting one in #1 and one in #3 but leaving #2 open) that can be a recipe for problems (often the system shouldn't startup or pass POST checks, but who knows!).

 

[dmc1986]

Hello
I checked and it was in the 3rd slot. Took it out and placed it in the 2nd. Now my ram is in the 1st and 2nd slot as it should be. Hopefuly thats it with my bsod problem and i can close this thread. Again thank you for your help kat and vir