Not likely to be overheating.
My money's on the video driver clashing with another part of windows. Usually this is due to a driver being written in contravention of kernel protection rules - something like that.
There's a whole string of stuff about the ialmrnt5 driver at http://software.intel.com/en-us/forums/user-community-for-intel-graphics-technology/topic/51557/
It'll prolly end up with you downloading the latest driver from Dell or Intel (taking care that the driver is compatible with your precise chipset).
Suspishio
Posting Virtuoso
1,730 posts since Aug 2007
Reputation Points: 47
Solved Threads: 145
caperjack
I hate 20 Questions
13,068 posts since Aug 2003
Reputation Points: 1,064
Solved Threads: 812
Overheating can be tested by blowing cool air into the vents while the laptop is running.
Sticking for now to past theories in this thread, it's now not clear when the latest BSOD occurred. Some video driver has to be there for you to receive the BSOD! Had you fully re-installed the OS and thus the old/current ialmrnt5 driver was part of your system - in which case I don't think you can infer a hardware problem. This type of error is a soft corruption in memory which means the OS can't continue. Rarely if ever due to hardware unless something is glitching electrically from time to time.
So can we have more info on where you'd got to in the build of your OS.
Incidentally what happens in Safe mode? You could certainly install your replacement drivers there.
Suspishio
Posting Virtuoso
1,730 posts since Aug 2007
Reputation Points: 47
Solved Threads: 145
I, and I'm sure others, don't see this as a heat related issue. You even sort of say so yourself because you can't feel excessive heat coming from the working fan.
The BSOD can happen when there is a memory overwite that destroys the system's ability to continue. That is always (?) a driver related issue and the error message indicates the causing driver. When there is no reported module, then IMHO the corruption itself has prevented from being reported.
There are brainios who can decipher the post mortem dump if one is fully take (Dr Watson sort of thing).
But all that's academic. The Dell technician's diagnosis is now something from which we all hope to learn. We hope!
Look forward to your next report.
Suspishio
Posting Virtuoso
1,730 posts since Aug 2007
Reputation Points: 47
Solved Threads: 145
What if your problem isn't with the system rather than with your hard disk. I had problem with a HP laptop way back i problem reinstalling windows because it kept giving me the blue screen. then i partioned it. afterwards i installed an antvirus to scan for any virus since i used a live cd to partion and backup the data. when it started to scan the logical drive i get the blue screen thus i assumed which is the case that the hard drive has physical errors which are making my system to crash. have you tried defragmenting or scanning?
ramjo
Junior Poster in Training
79 posts since Dec 2006
Reputation Points: 10
Solved Threads: 4
Well done. If it isn't a memory clash with driver/kernel, then it's the memory itself.
Glad you're sorted.
Suspishio
Posting Virtuoso
1,730 posts since Aug 2007
Reputation Points: 47
Solved Threads: 145
@notuserfriendly: He fixed it
Suspishio
Posting Virtuoso
1,730 posts since Aug 2007
Reputation Points: 47
Solved Threads: 145
fixed it, and it was a laptop, so no pci cards!
caperjack
I hate 20 Questions
13,068 posts since Aug 2003
Reputation Points: 1,064
Solved Threads: 812