[Rollin' Rog]

If you don't see any readings it's because your Dell motherboard, like my old Dimension 8200 does not support temperature monitoring.

Have you had a look inside the case and blown out all accumulated dust and ensured the fan is working?

[Zenoxio]

I've done that and still getting BSODs. If the fan failed, it should say on boot. Plus I feel an air flow out the back.

I've attached some more dumps in hope they have info.

[Rollin' Rog]

Mostly I'm seeing these >>

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption. Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: 879bcf68, address trying to free
Arg2: 879bcdea, address where bits are corrupted
Arg3: 00350094, (reserved)
Arg4: 00000023, caller is freeing an address where nearby bytes within the same page have been corrupted

And the "back trace" >>

kd> kd (display back trace)
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*** WARNING: Unable to verify timestamp for ATMFD.DLL
*** ERROR: Module load completed but symbols could not be loaded for ATMFD.DLL
*** WARNING: Unable to verify timestamp for nltdi.sys
*** ERROR: Module load completed but symbols could not be loaded for nltdi.sys
*** WARNING: Unable to verify timestamp for smwdm.sys
*** ERROR: Module load completed but symbols could not be loaded for smwdm.sys
*** WARNING: Unable to verify timestamp for e100b325.sys
*** ERROR: Module load completed but symbols could not be loaded for e100b325.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for drmk.sys -
*** WARNING: Unable to verify timestamp for GEARAspiWDM.sys
*** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
*** WARNING: Unable to verify timestamp for OMCI.SYS
*** ERROR: Module load completed but symbols could not be loaded for OMCI.SYS
*** WARNING: Unable to verify timestamp for speedfan.sys
*** ERROR: Module load completed but symbols could not be loaded for speedfan.sys
*** WARNING: Unable to verify timestamp for aeaudio.sys
*** ERROR: Module load completed but symbols could not be loaded for aeaudio.sys
*** WARNING: Unable to verify timestamp for giveio.sys
*** ERROR: Module load completed but symbols could not be loaded for giveio.sys
Couldn't resolve error at 'display back trace)'

In one recent rather similar issue, I suggested everything but reinstalling the Display Drivers -- and that seemed to be what solved the problem -- found by poster himself.

Might be why you had that "beserk" monitor as well.

[Zenoxio]

Reinstalled and update display drivers yesterday.

Left the computer on overnight and came back to finding it had crashed.

[Rollin' Rog]

kd> kd (display back trace)

*** WARNING: Unable to verify timestamp for smwdm.sys
*** ERROR: Module load completed but symbols could not be loaded for smwdm.sys
*** WARNING: Unable to verify timestamp for e100b325.sys
*** ERROR: Module load completed but symbols could not be loaded for e100b325.sys
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*** WARNING: Unable to verify timestamp for ATMFD.DLL
*** ERROR: Module load completed but symbols could not be loaded for ATMFD.DLL
*** WARNING: Unable to verify timestamp for nltdi.sys
*** ERROR: Module load completed but symbols could not be loaded for nltdi.sys
*** WARNING: Unable to verify timestamp for OMCI.SYS
*** ERROR: Module load completed but symbols could not be loaded for OMCI.SYS
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for drmk.sys -
*** WARNING: Unable to verify timestamp for GEARAspiWDM.sys
*** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
*** WARNING: Unable to verify timestamp for speedfan.sys
*** ERROR: Module load completed but symbols could not be loaded for speedfan.sys
*** WARNING: Unable to verify timestamp for aeaudio.sys
*** ERROR: Module load completed but symbols could not be loaded for aeaudio.sys
*** WARNING: Unable to verify timestamp for giveio.sys
*** ERROR: Module load completed but symbols could not be loaded for giveio.sys
Couldn't resolve error at 'display back trace)'

The number of drivers in the back trace is relatively small; the one I have highlighted is for "NetLimiter" -- which could be a wild card here.

You might try uninstalling or disabling that.

------------------------------------------------------------

You can also try running "driver verifier" to see if it throws an error.

In your case -- I recommend using "custom settings" rather than "standard" as the cutnpaste directions below suggest.

When you select Custom settings you will click "next" and choose the option to select specific settings. You want to check the "special pool" here.

On clicking "next" again you get the option of selecting signed or unsigned drivers -- try the "unsigned" first, but if no boot failure, try again with all drivers.

remember if driver verifier shows a STOP, it is the driver file NOT the STOP error (which is specific to verifier) which is important.

Then you will have to reboot to Safe Mode and run: verifier /reset

-----------------------------------------------------------------------------------------
USING DRIVER VERIFIER

Windows has a built in driver tester that may find something.
Before using it you must ensure that you can start in Safe Mode and return from it. If verifier issues a STOP screen, rebooting in Safe Mode is the only way to reset it.

In its default configuration verifier tests "unsigned" drivers, but you can have it test all drivers under maximum conditions.

There's less to it than meets the eye in this MS article:

http://support.microsoft.com/default...b;en-us;244617

To run verifier simply go to Start > run and enter:

verifier.exe

and select "standard configuration" and follow the prompts.
It will run on the next reboot. If it finds something you will get a Blue Screen STOP message.

Ignore the STOP parameters -- they are specific to verifier. The only thing important is the driver file name if it finds one.

If you get a STOP screen you will have to reboot to Safe Mode and run verifier again and have it "delete existing settings"

If you do not get a STOP message you can run it again checking all drivers; driver verifier will continue to run on every boot up until you run:

verifier /reset

or use the graphical interface to delete existing settings.

[Zenoxio]

Uninstalled that program today, didn't restart, had a BSOD, booted it backup and it BSOD'd in the middle of the boot (before the desktop). Attached are those BSODs, is that NetLimiter gone from the backtrace?

And didn't I do the driver verifier thing already?

[Rollin' Rog]

2 of the 3 bugchecks are "special pool corruption" and the back traces are identical except for the absence of Netlimiter which we can now rule out.

However the last is a win32k.sys fault and while these can be caused by some low level kernel driver fault such as display drivers and security software -- they are also commonly hardware associated.

Overheating is one of these, and faulty ram another.
What have you done to check for overheating?

It looks like some graphics processing is going on in the win32k.sys fault

Debug session time: Fri Nov 6 13:28:29.968 2009 (GMT-8)
BugCheck 1000008E, {c0000005, bf88b901, f5c9ffe0, 0}

Probably caused by : win32k.sys ( win32k!vLoadFontFileView+f1 )
STACK_TEXT:
f5ca0068 bf88bc9e f5ca01b8 0000001d e1f38a68 win32k!vLoadFontFileView+0xf1
f5ca00e4 bf88cb46 f5ca01b8 0000001d 00000001 win32k!PUBLIC_PFTOBJ::bLoadFonts+0x1da
f5ca012c bf88ca78 f5ca01b8 0000001d 00000001 win32k!GreAddFontResourceWInternal+0xab
f5ca0274 804de7ec 00ddf338 0000001d 00000001 win32k!NtGdiAddFontResourceW+0x172
f5ca0274 7c90e514 00ddf338 0000001d 00000001 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
00a6feec 00000000 00000000 00000000 00000000 0x7c90e514
FOLLOWUP_IP:
win32k!vLoadFontFileView+f1
bf88b901 f6402120 test byte ptr [eax+21h],20h


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!vLoadFontFileView+f1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49e87572

FAILURE_BUCKET_ID: 0x8E_win32k!vLoadFontFileView+f1

BUCKET_ID: 0x8E_win32k!vLoadFontFileView+f1

--------------------------------------------------------------------------------
Debug session time: Fri Nov 6 13:27:40.191 2009 (GMT-8)
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption. Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: 88e2af68, address trying to free
Arg2: 88e2a9ca, address where bits are corrupted
Arg3: 00250094, (reserved)
Arg4: 00000023, caller is freeing an address where nearby bytes within the same page have been corrupted

[Zenoxio]

I had the computer off all weekend, and when I booted it today 10 minutes later it had a BSOD. Doesn't really seem like an overheating problem, but I'm not sure how I would check it if 3rd party fan programs don't work with a Dell.

[Rollin' Rog]

If you have ensured the inside of the case is clean and the fan working, not much else you can do there.


Has chkdsk been run on the drive recently?

http://support.microsoft.com/kb/315265

After chkdsk completes, the log will be available in the Event Viewer (run: eventvwr.msc) > Applications Log > Winlogon entry.

You can double click that to read the description and use the double-paper copy icon to copy the log to the clipboard for pasting.

[Zenoxio]

chkdsk results are back on page 1.
http://forums.techguy.org/6850074-post13.html

[Rollin' Rog]

Let's try removing Adobe Type Manager; just fixed one thread by getting rid of this, and one your recent BSODs involves Fonts:

Debug session time: Fri Nov 6 13:28:29.968 2009 (GMT-8)
BugCheck 1000008E, {c0000005, bf88b901, f5c9ffe0, 0}

Probably caused by : win32k.sys ( win32k!vLoadFontFileView+f1 )
STACK_TEXT:
f5ca0068 bf88bc9e f5ca01b8 0000001d e1f38a68 win32k!vLoadFontFileView+0xf1
f5ca00e4 bf88cb46 f5ca01b8 0000001d 00000001 win32k!PUBLIC_PFTOBJ::bLoadFonts+0x1da
f5ca012c bf88ca78 f5ca01b8 0000001d 00000001 win32k!GreAddFontResourceWInternal+0xab

http://www.bang.ro/atmfd_dll.htm

[Zenoxio]

I don't seem to be able to remove just that without removing Photoshop, which I need.

The BSODs are quick, but I can catch it saying something like MEMORY_CORRUPTION. But I don't know if this is correct or not, because http://wer.microsoft.com/responses/R...0-2c602542da1a pops up after I restart and says it's a driver issue.

[Rollin' Rog]

You're right Photoshop would have to be uninstalled to remove the Adobe Type Manager

Drivers can cause "memory corruption" -- that is probably the "special pool" corruption that we've seen before.

What "unsigned" drivers are on the system? run sigverif.exe


If these BSODs are frequent or predictable enough it may be worthwhile to try a "clean boot" troubleshooting technique; I know I've suggested this before, but it doesn't look like you have tried it. Upload any new minidumps for BSODs during a "clean boot" >>

Run msconfig and select the "Services" tab. Check "Hide Microsoft Services" and then disable the rest. Also uncheck "load startup items" on the general page.


Now restart and test the issue at hand

If no problems, run msconfig and recheck half the disabled items on the Services tab. Test again. If the problem recurs, UNcheck half the items you just checked to narrow down the culprit.

If the problem didn't occur, check the other half, so all the Services are enabled -- proceed to do this on the startup tab as well.

Get the idea? You want to isolate the problem to a specific startup if possible.

Note: if you already have items unchecked under msconfig > startups and are in “selective” startup mode – you should note what these are before beginning. They will need to be de-selected again.


http://support.microsoft.com/kb/929135/en-us >> writen for Vista but applies just as well to XP

[Zenoxio]

Unsigned drivers: http://imgur.com/fnpYT.png

These BSODs aren't predictable, but I'll see what I can do about a clean boot.

[Rollin' Rog]

Strange, this is the only "system" driver that is unsigned, one for "remote desktop", and it should belong to Microsoft >>

http://www.google.com/search?client=...utf-8&oe=utf-8

I doubt it is causing a problem, but if enabled it might be exploitable

The rest are Printer dlls -- applications extensions.