Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1466
  • Last Modified:

BSOD help

Hello, I am constantly getting blue screens, usually with the DRIVER_IRQL_NOT LESS OR EQUAL message.

I have tried running Memtest86 and the RAM seems fine, also tried to clean the page file on the C: drive, have taken out the RAM and cleaned the inside of the case but still get the Blue screens, sometimes the computer will run for a week with no problem but sometimes it will get Blue Screens 5x per day.

Here is the computer spec if that helps:
2 x Intel Xeon 3200Mhz
ASUS NCCH-DL Motherboard
4 GB RAM
ATI Radeon 9600 Video
Windows XP Pro

Can post minidumps if required.  Any help will be much appreciated.

Thanks.
0
jns_johnson
Asked:
jns_johnson
  • 24
  • 23
  • 12
  • +1
2 Solutions
 
justinmoore14Commented:
Hello Jns_johnson, a couple of things. When did this start happening?? Did anything change recently?? Have you tried with only one stick of ram?? Also you may want to run sfc /scannow (System File Checker), and make sure you have your disk because if any of the files are screwed you will need it. Hope this helps.


Justin
0
 
jns_johnsonAuthor Commented:
Hi Justin,

Thanks for your comment, it has been happening for a few months now, there has not been any hardware changes and I cannot identify any software that might be causing the problem.

I have tried the sfc /scannow and it did not pick up any errors.

Any other suggestions?

Thanks
0
 
2PiFLCommented:
That error usually means the mother board has a problem.  Is there anything in the event viewer - system log?
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
jns_johnsonAuthor Commented:
Hi 2PiFL,

The system event viewer shows the following errors:

Source: System Error
Category: (102)
Event : 1003
Description: Error code 100000d1, parameter1 a08b1a71, parameter2 000000ff, parameter3 00000000, parameter4 8b1a71a0.

Source: DCOM
Category: None
Event : 10005
Description: DCOM got error "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. " attempting to start the service upnphost with arguments "" in order to run the server:
{204810B9-73B2-11D4-BF42-00B0D0118B56}

Thanks.
0
 
torimarCommented:
If you are certain it's not the RAM or pagefile, there is a chance this might be caused by your network adapter and/or a third-party firewall:

http://support.microsoft.com/?kbid=916595
Stop error message on a Windows XP-based computer: "STOP 0x000000D1"

But this is basically just guessing. It would be very helpful indeed if you could post the minidumps.
(Rename them to *.txt before attaching, please)
0
 
jns_johnsonAuthor Commented:
Hi torimar,

Thanks for your suggestion, the update indicated in that link would not install as I apparently have a newer service pack.

Attached are my latest mindumps.

Many thanks.
Mini021009-01.txt
Mini020909-04.txt
Mini020909-03.txt
Mini020909-02.txt
0
 
justinmoore14Commented:
Jns_Johnson, did you try using only one stick of ram as well (See my post above). Also, you said (sometimes the computer will run for a week with no problem but sometimes it will get Blue Screens 5x per day) is there any particular application that you can think of that is open or you are using when this occurs.

Finally, about how old is this machine as well (System board more specifically).


Justin
0
 
jns_johnsonAuthor Commented:
I tried 1 stick, which worked fine so I added another stick 12 hours later, then a 3rd about 24 hours after that - at this point I started to get the blue sceens again so swapped the last stick I added for the remaining spare stick, still got the blue screens so took out that stick which left 2 in the machine. It worked ok for a bit with the 2 sticks but then started crashing again so I wasnt able to determine much about any particular sticks being faulty. Am now back with the 4 sticks.

The machine is almost 3 years old.

0
 
jns_johnsonAuthor Commented:
I have not noticed a particular application that causes the crashing, sometimes it happens just after boot-up sometimes after a few hours of running several programs.
0
 
justinmoore14Commented:
Have you tried to go to msconfig/startup and disable any applications there that don't need to start up. If so, did you notice any that didn't seem to belong there?? If you haven't you might want to try that. Also, just out of curiosity when you shut down do you get any process that pop up and show Windows is having to kill them (The infamous End Now dialog box)??


As far as the ram goes, if I understand you correctly basically what you are saying you have swapped all sticks with each other and have tried about ever combination you can imagine...Correct?? If this is the case then there could very well be nothing wrong with the ram, but possibly one of the dimm slots on the board itself. If you happen to stick your head in the case again and have a chance you may want to take a peak at the capacitors on the board and make sure none of them are bulging or leaking. If you need help with this let me know.

Justin
0
 
jns_johnsonAuthor Commented:
I have had a look at the msconifg/startup and I cannot see anything that looks like it should not be there or missing, although I am not entirely sure what to look for.

I do not get any 'end now' boxes on shut down.

Regarding the RAM, I have more or less tried all the combinations although with just one stick I did not wait for a blue screen to occur, maybe I should?

The RAM slots look fine to me, will check the capicitors for leaks now.

Also, just had another blue screen now, the same error as the first post, attached is the minidump.

Many thanks.
Mini021109-01.txt
0
 
justinmoore14Commented:
(Regarding the ram) Yes, I would definitely use only 1 stick in the first dimm and see if you get a blue screen. The more variables that you have in this the harder it will be to trouble shoot.


Also, I am still reviewing the minidump files.


Justin
0
 
justinmoore14Commented:
Also, you may want to try booting off your XP disk and going into the recovery console and running chkdsk /r


Justin
0
 
jns_johnsonAuthor Commented:
Currently trying just 1 stick of RAM, in the first slot. It was not long before I got a blue screen,  Am now testing the same stick alone in slot 2.

Any further clues from the minidumps?

Many thanks.

0
 
justinmoore14Commented:
Very Interesting, also how did the chkdsk /r come out??


Unfortunately, I have yet to find any useful information from the minidump files.


Also, you may have posted this already but after a second look over the post I can't seem to find it (So if you did, if you wouldn't mind posting it again I would appreciate it). What is the exact error message that you are getting. For ex. Stop 0x000000XX (Stop 0x000000XX,0x000000XX,0x000000XX,0x000000XX,0x000000XX,) Where XX is the letter followed by the number, or two numbers, etc...


Justin
0
 
jns_johnsonAuthor Commented:
I am yet to try the chkdsk /r, although when I turned on the computer the other day it would not boot (just got stuck on the ASUS screen). Could not get into safe mode or last known config so I tried booting from the XP cd, the windows recovery console got the computer to boot eventually.  I suppose this isnt the same as chkdsk /r so will try that tonight and let you know what happens.

About the stop messages, I think they have been varying although I have not been keeping a record.  If memory serves it was something like 0x0000000D1 or 1D. Will post again when I next get a blue screen.

Thanks again.
0
 
justinmoore14Commented:
I am not sure I follow you...You said (I tried booting from the XP cd, the windows recovery console) and then you said ( I suppose this isnt the same as chkdsk /r)?? What did you do in the recovery console to get it to boot?? Yes, you were almost there, boot off the XP CD, then go to the recovery console, and then run chkdsk /r  (Sounds good let me know if you have any issues getting it to run or getting there).


That's fine, if you have another Blue Screen you can just post it then.


Justin
0
 
torimarCommented:
Sorry for not posting back, but I was busy solving some problems here as well, and yesterday EE was down most of the time.

The minidumps unfortunately are near to useless (STOP 0xd1 - DRIVER_IRQL_NOT_LESS_OR_EQUAL). They only refer to the Windows kernel, which lets us conclude that with a very high probability the root of this evil will be a badly programmed third-party kernel mode driver. Unfortunately, you cannot trace back memory allocations in a minidump; there is a slight (although really slight) chance that a complete memory dump might yield more information. But it could take a long time to get there.

Might take less time to check your drivers for old and outdated versions.

Please bear in mind that your drivers are *not* managed by msconfig or the service administration. They are managed via the device manager: Control Panel > System > Hardware.
An easy way to let your drivers be checked all at once would be something like Drivermax: http://www.drivermax.com
This does have commercial side-intentions, but registration and basic services are free. I used it myself once and coudn't notice anything fishy about it.

 
Mini Kernel Dump File: Only registers and stack trace are available
 
Symbol search path is: SRV*f:\tmpsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.080814-1236
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Feb 11 15:50:37.000 2009 (GMT+1)
System Uptime: 0 days 2:57:01.949
Loading Kernel Symbols
.................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 100000D1, {a08b1a71, ff, 0, 8b1a71a0}
 
Probably caused by : ntkrpamp.exe ( nt!ObSetSecurityObjectByPointer+9 )
 
Followup: MachineOwner
---------
 
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: a08b1a71, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8b1a71a0, address which referenced memory
 
Debugging Details:
------------------
 
 
READ_ADDRESS:  a08b1a71 
 
CURRENT_IRQL:  ff
 
FAULTING_IP: 
+ffffffff8b1a71a0
8b1a71a0 a0711a8ba0      mov     al,byte ptr ds:[A08B1A71h]
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  DRIVER_FAULT
 
BUGCHECK_STR:  0xD1
 
PROCESS_NAME:  System
 
LAST_CONTROL_TRANSFER:  from 805c0023 to 8b1a71a0
 
STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
ba533dac 805c0023 00000000 00000000 00000000 0x8b1a71a0
ba533ddc 805460ee 805401da 00000000 00000000 nt!ObSetSecurityObjectByPointer+0x9
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
nt!ObSetSecurityObjectByPointer+9
805c0023 4a              dec     edx
 
SYMBOL_STACK_INDEX:  1
 
SYMBOL_NAME:  nt!ObSetSecurityObjectByPointer+9
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
IMAGE_NAME:  ntkrpamp.exe
 
DEBUG_FLR_IMAGE_TIMESTAMP:  48a3fbd9
 
FAILURE_BUCKET_ID:  0xD1_nt!ObSetSecurityObjectByPointer+9
 
BUCKET_ID:  0xD1_nt!ObSetSecurityObjectByPointer+9
 
Followup: MachineOwner
---------
 
1: kd> lmvm nt
start    end        module name
804d7000 806e4000   nt       # (pdb symbols)          f:\tmpsymbols\ntkrpamp.pdb\D82F3C0407BA4AB09C7831D423622B691\ntkrpamp.pdb
    Loaded symbol image file: ntkrpamp.exe
    Mapped memory image file: f:\tmpsymbols\ntkrpamp.exe\48A3FBD920d000\ntkrpamp.exe
    Image path: ntkrpamp.exe
    Image name: ntkrpamp.exe
    Timestamp:        Thu Aug 14 11:33:13 2008 (48A3FBD9)
    CheckSum:         001FBC56
    ImageSize:        0020D000
    File version:     5.1.2600.5657
    Product version:  5.1.2600.5657
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0401.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ntkrpamp.exe
    OriginalFilename: ntkrpamp.exe
    ProductVersion:   5.1.2600.5657
    FileVersion:      5.1.2600.5657 (xpsp_sp3_gdr.080814-1236)
    FileDescription:  NT Kernel & System
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
1: kd> r
eax=c000001c ebx=00000000 ecx=00000008 edx=80500009 esi=8aef82c0 edi=00000000
eip=8b1a71a0 esp=ba533db0 ebp=ba533da4 iopl=0         nv up di pl nz ac po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010012
8b1a71a0 a0711a8ba0      mov     al,byte ptr ds:[A08B1A71h] ds:0023:a08b1a71=??
1: kd> lmnt
start    end        module name
804d7000 806e4000   nt       ntkrpamp.exe Thu Aug 14 11:33:13 2008 (48A3FBD9)
806e4000 80704d00   hal      halmacpi.dll Sun Apr 13 20:31:27 2008 (4802517F)
a53b7000 a53bad80   DNINDIS5 DNINDIS5.SYS Thu Jul 24 06:10:32 2003 (3F1F5C38)
a562b000 a5633080   ipfltdrv ipfltdrv.sys Fri Aug 17 22:55:07 2001 (3B7D84AB)
a5c03000 a5c54800   srv      srv.sys      Mon Sep 08 12:41:40 2008 (48C50164)
a5dbd000 a5de9180   mrxdav   mrxdav.sys   Sun Apr 13 20:32:42 2008 (480251CA)
a5f28000 a5f3c480   wdmaud   wdmaud.sys   Sun Apr 13 21:17:18 2008 (48025C3E)
a60ed000 a60fbd80   sysaudio sysaudio.sys Sun Apr 13 21:15:55 2008 (48025BEB)
a6301000 a6304900   ndisuio  ndisuio.sys  Sun Apr 13 20:55:57 2008 (4802573D)
a6305000 a6308e60   AegisP   AegisP.sys   Fri Nov 19 21:55:14 2004 (419E5DB2)
a868d000 a86a4900   dump_atapi dump_atapi.sys Sun Apr 13 20:40:29 2008 (4802539D)
a86a5000 a86fd9c0   WG11TND5 WG11TND5.sys Mon Sep 05 05:21:04 2005 (431BB9A0)
a8826000 a8829f60   HPZipr12 HPZipr12.sys Thu Mar 18 12:22:43 2004 (40598683)
a883e000 a8861180   Fastfat  Fastfat.SYS  Sun Apr 13 21:14:28 2008 (48025B94)
a888e000 a8890900   Dxapi    Dxapi.sys    Fri Aug 17 22:53:19 2001 (3B7D843F)
a8902000 a894fc00   avgldx86 avgldx86.sys Tue Jan 13 17:25:55 2009 (496CC093)
a8950000 a89bf780   mrxsmb   mrxsmb.sys   Sun Apr 13 21:16:58 2008 (48025C2A)
a8a10000 a8a3ae80   rdbss    rdbss.sys    Sun Apr 13 21:28:38 2008 (48025EE6)
a8a53000 a8a56b00   usbscan  usbscan.sys  Sun Apr 13 20:45:34 2008 (480254CE)
a8a63000 a8a84d00   afd      afd.sys      Thu Aug 14 12:04:35 2008 (48A40333)
a8a85000 a8af0000   vsdatant vsdatant.sys Fri Nov 14 00:07:29 2008 (491CB331)
a8af0000 a8b08900   avgtdix  avgtdix.sys  Wed Dec 10 12:50:42 2008 (493FAD12)
a8b09000 a8b2e500   ipnat    ipnat.sys    Sun Apr 13 20:57:10 2008 (48025786)
a8b2f000 a8b56c00   netbt    netbt.sys    Sun Apr 13 21:20:59 2008 (48025D1B)
a8b57000 a8baf380   tcpip    tcpip.sys    Sun Apr 13 21:20:12 2008 (48025CEC)
a8bb0000 a8bc2600   ipsec    ipsec.sys    Sun Apr 13 21:19:42 2008 (48025CCE)
b8d35000 b8d92f00   update   update.sys   Sun Apr 13 20:39:46 2008 (48025372)
b8d93000 b8dc2e80   rdpdr    rdpdr.sys    Sun Apr 13 20:32:50 2008 (480251D2)
b8dc3000 b8dd3e00   psched   psched.sys   Sun Apr 13 20:56:36 2008 (48025764)
b8dd4000 b8dea580   ndiswan  ndiswan.sys  Sun Apr 13 21:20:41 2008 (48025D09)
b8deb000 b8e02880   SCSIPORT SCSIPORT.SYS Sun Apr 13 20:40:29 2008 (4802539D)
b8e03000 b8e4d000   vaxscsi  vaxscsi.sys  Mon Jan 09 22:20:27 2006 (43C2D39B)
b8ffb000 b901ea80   portcls  portcls.sys  Sun Apr 13 21:19:40 2008 (48025CCC)
b901f000 b9032900   parport  parport.sys  Sun Apr 13 20:40:09 2008 (48025389)
b9033000 b9055700   ks       ks.sys       Sun Apr 13 21:16:34 2008 (48025C12)
b9056000 b909e480   deltaII  deltaII.sys  Mon Mar 03 16:08:52 2008 (47CC1484)
b909f000 b90c2200   USBPORT  USBPORT.SYS  Sun Apr 13 20:45:34 2008 (480254CE)
b90c3000 b90e1c00   e1000325 e1000325.sys Fri Aug 29 19:26:44 2003 (3F4F8CD4)
b90e2000 b90f5f00   VIDEOPRT VIDEOPRT.SYS Sun Apr 13 20:44:39 2008 (48025497)
b90f6000 b960d000   ati2mtag ati2mtag.sys Wed Sep 24 04:16:43 2008 (48D9A30B)
b960d000 b9617e00   Fips     Fips.SYS     Sun Apr 13 20:33:27 2008 (480251F7)
b961d000 b9625f20   PQIMount PQIMount.SYS Tue Nov 23 01:08:52 2004 (41A27F94)
b962d000 b9639e20   SCDEmu   SCDEmu.SYS   Thu Jun 12 08:28:49 2008 (4850C221)
b963d000 b9645780   netbios  netbios.sys  Sun Apr 13 20:56:01 2008 (48025741)
b964d000 b9655700   wanarp   wanarp.sys   Sun Apr 13 20:57:20 2008 (48025790)
b965d000 b966bd80   arp1394  arp1394.sys  Sun Apr 13 20:51:22 2008 (4802562A)
b966d000 b967c180   nic1394  nic1394.sys  Sun Apr 13 20:51:22 2008 (4802562A)
b967d000 b968b880   usbhub   usbhub.sys   Sun Apr 13 20:45:36 2008 (480254D0)
b99d9000 b99dcc80   mssmbios mssmbios.sys Sun Apr 13 20:36:45 2008 (480252BD)
b9c20000 b9c22780   ndistapi ndistapi.sys Sun Apr 13 20:57:27 2008 (48025797)
b9c2c000 b9c2e980   gameenum gameenum.sys Sun Apr 13 20:45:29 2008 (480254C9)
b9c30000 b9c33d80   serenum  serenum.sys  Sun Apr 13 20:40:12 2008 (4802538C)
b9c70000 b9c72280   rasacd   rasacd.sys   Fri Aug 17 22:55:39 2001 (3B7D84CB)
b9c74000 b9c77720   pclepci  pclepci.sys  Fri Sep 07 11:09:39 2001 (3B988ED3)
b9cdc000 b9cf5b80   Mup      Mup.sys      Sun Apr 13 21:17:05 2008 (48025C31)
b9cf6000 b9d0a000   srescan  srescan.sys  Fri Apr 11 10:01:22 2008 (47FF1AD2)
b9d0a000 b9d36980   NDIS     NDIS.sys     Sun Apr 13 21:20:35 2008 (48025D03)
b9d37000 b9dc3600   Ntfs     Ntfs.sys     Sun Apr 13 21:15:49 2008 (48025BE5)
b9dc4000 b9dda880   KSecDD   KSecDD.sys   Sun Apr 13 20:31:40 2008 (4802518C)
b9ddb000 b9dec960   TPkd     TPkd.sys     Wed Nov 16 12:04:35 2005 (437B1243)
b9ded000 b9e02360   PQV2i    PQV2i.sys    Tue Nov 23 00:51:56 2004 (41A27B9C)
b9e03000 b9e22b00   fltmgr   fltmgr.sys   Sun Apr 13 20:32:58 2008 (480251DA)
b9e23000 b9e3a900   atapi    atapi.sys    Sun Apr 13 20:40:29 2008 (4802539D)
b9e3b000 b9e60700   dmio     dmio.sys     Sun Apr 13 20:44:45 2008 (4802549D)
b9e61000 b9e7f880   ftdisk   ftdisk.sys   Fri Aug 17 22:52:41 2001 (3B7D8419)
b9e80000 b9e90a80   pci      pci.sys      Sun Apr 13 20:36:43 2008 (480252BB)
b9e91000 b9ebed80   ACPI     ACPI.sys     Sun Apr 13 20:36:33 2008 (480252B1)
b9ebf000 b9ed6880   SPTD6813 SPTD6813.SYS Sun Apr 13 20:40:29 2008 (4802539D)
b9ed7000 b9fa7000   sptd     sptd.sys     Sat Dec 03 14:59:59 2005 (4391A4DF)
ba0a8000 ba0b1180   isapnp   isapnp.sys   Sun Apr 13 20:36:40 2008 (480252B8)
ba0b8000 ba0c7100   ohci1394 ohci1394.sys Sun Apr 13 20:46:18 2008 (480254FA)
ba0c8000 ba0d5080   1394BUS  1394BUS.SYS  Sun Apr 13 20:46:18 2008 (480254FA)
ba0d8000 ba0e2580   MountMgr MountMgr.sys Sun Apr 13 20:39:45 2008 (48025371)
ba0e8000 ba0f4c80   VolSnap  VolSnap.sys  Sun Apr 13 20:41:00 2008 (480253BC)
ba0f8000 ba100e00   disk     disk.sys     Sun Apr 13 20:40:46 2008 (480253AE)
ba108000 ba114180   CLASSPNP CLASSPNP.SYS Sun Apr 13 21:16:21 2008 (48025C05)
ba118000 ba122b80   sbp2port sbp2port.sys Sun Apr 13 20:40:47 2008 (480253AF)
ba128000 ba132580   agp440   agp440.sys   Sun Apr 13 20:36:37 2008 (480252B5)
ba178000 ba184680   HPZid412 HPZid412.sys Thu Mar 18 12:22:40 2004 (40598680)
ba188000 ba197900   Cdfs     Cdfs.SYS     Sun Apr 13 21:14:21 2008 (48025B8D)
ba218000 ba220e00   intelppm intelppm.sys Sun Apr 13 20:31:31 2008 (48025183)
ba228000 ba231000   LaCieUSBFilter LaCieUSBFilter.sys Wed Oct 19 10:34:01 2005 (435604F9)
ba238000 ba247c00   serial   serial.sys   Sun Apr 13 21:15:44 2008 (48025BE0)
ba248000 ba254d00   i8042prt i8042prt.sys Sun Apr 13 21:17:59 2008 (48025C67)
ba258000 ba266b00   drmk     drmk.sys     Sun Apr 13 20:45:12 2008 (480254B8)
ba268000 ba272480   imapi    imapi.sys    Sun Apr 13 20:40:57 2008 (480253B9)
ba278000 ba287600   cdrom    cdrom.sys    Sun Apr 13 20:40:45 2008 (480253AD)
ba288000 ba296100   redbook  redbook.sys  Sun Apr 13 20:40:27 2008 (4802539B)
ba298000 ba2a2780   vacs2xkd vacs2xkd.sys Thu Nov 01 12:53:18 2007 (4729BE2E)
ba2a8000 ba2b4880   rasl2tp  rasl2tp.sys  Sun Apr 13 21:19:43 2008 (48025CCF)
ba2b8000 ba2c2200   raspppoe raspppoe.sys Sun Apr 13 20:57:31 2008 (4802579B)
ba2c8000 ba2d3d00   raspptp  raspptp.sys  Sun Apr 13 21:19:47 2008 (48025CD3)
ba2d8000 ba2e0900   msgpc    msgpc.sys    Sun Apr 13 20:56:32 2008 (48025760)
ba2e8000 ba2f3900   Pcouffin Pcouffin.sys Fri Jun 30 15:40:17 2006 (44A529C1)
ba2f8000 ba301f00   termdd   termdd.sys   Sun Apr 13 20:38:36 2008 (4802532C)
ba308000 ba316000   cledx    cledx.sys    Mon May 09 20:08:41 2005 (427FA729)
ba318000 ba321e80   NDProxy  NDProxy.SYS  Sun Apr 13 20:57:28 2008 (48025798)
ba328000 ba32e180   PCIIDEX  PCIIDEX.SYS  Sun Apr 13 20:40:29 2008 (4802539D)
ba330000 ba334d00   PartMgr  PartMgr.sys  Sun Apr 13 20:40:48 2008 (480253B0)
ba350000 ba354a80   Msfs     Msfs.SYS     Sun Apr 13 20:32:38 2008 (480251C6)
ba370000 ba377880   Npfs     Npfs.SYS     Sun Apr 13 20:32:38 2008 (480251C6)
ba378000 ba37d200   avgmfx86 avgmfx86.sys Wed Dec 10 12:48:14 2008 (493FAC7E)
ba380000 ba387d80   usbccgp  usbccgp.sys  Sun Apr 13 20:45:38 2008 (480254D2)
ba390000 ba396700   USBSTOR  USBSTOR.SYS  Sun Apr 13 20:45:37 2008 (480254D1)
ba398000 ba39e500   usbprint usbprint.sys Sun Apr 13 20:47:37 2008 (48025549)
ba3a0000 ba3a53e0   HPZius12 HPZius12.sys Thu Mar 18 12:21:01 2004 (4059861D)
ba3b0000 ba3b4500   watchdog watchdog.sys Sun Apr 13 20:44:59 2008 (480254AB)
ba418000 ba41e000   pgfilter pgfilter.sys Mon Sep 19 03:02:52 2005 (432E0E3C)
ba448000 ba44d080   usbuhci  usbuhci.sys  Sun Apr 13 20:45:34 2008 (480254CE)
ba450000 ba457600   usbehci  usbehci.sys  Sun Apr 13 20:45:34 2008 (480254CE)
ba458000 ba460000   LaCieFWFilter LaCieFWFilter.sys Tue Oct 18 09:28:06 2005 (4354A406)
ba460000 ba465a00   mouclass mouclass.sys Sun Apr 13 20:39:47 2008 (48025373)
ba468000 ba46e000   kbdclass kbdclass.sys Sun Apr 13 20:39:46 2008 (48025372)
ba470000 ba477000   GearAspiWDM GearAspiWDM.SYS Mon Aug 07 19:11:27 2006 (44D7743F)
ba478000 ba47ca80   TDI      TDI.SYS      Sun Apr 13 21:00:04 2008 (48025834)
ba480000 ba484580   ptilink  ptilink.sys  Fri Aug 17 22:49:53 2001 (3B7D8371)
ba488000 ba48c080   raspti   raspti.sys   Fri Aug 17 22:55:32 2001 (3B7D84C4)
ba4b0000 ba4b5200   vga      vga.sys      Sun Apr 13 20:44:40 2008 (48025498)
ba4b8000 ba4bb000   BOOTVID  BOOTVID.dll  Fri Aug 17 22:49:09 2001 (3B7D8345)
ba5a8000 ba5a9b80   kdcom    kdcom.dll    Fri Aug 17 22:49:10 2001 (3B7D8346)
ba5aa000 ba5ab100   WMILIB   WMILIB.SYS   Fri Aug 17 23:07:23 2001 (3B7D878B)
ba5ac000 ba5ad580   intelide intelide.sys Sun Apr 13 20:40:29 2008 (4802539D)
ba5ae000 ba5af700   dmload   dmload.sys   Fri Aug 17 22:58:15 2001 (3B7D8567)
ba5fc000 ba5fd280   USBD     USBD.SYS     Fri Aug 17 23:02:58 2001 (3B7D8682)
ba600000 ba601100   swenum   swenum.sys   Sun Apr 13 20:39:52 2008 (48025378)
ba602000 ba603f00   Fs_Rec   Fs_Rec.SYS   Fri Aug 17 22:49:37 2001 (3B7D8361)
ba604000 ba605080   Beep     Beep.SYS     Fri Aug 17 22:47:33 2001 (3B7D82E5)
ba606000 ba607080   mnmdd    mnmdd.SYS    Fri Aug 17 22:57:28 2001 (3B7D8538)
ba608000 ba609080   RDPCDD   RDPCDD.sys   Fri Aug 17 22:46:56 2001 (3B7D82C0)
ba614000 ba615a80   ParVdm   ParVdm.SYS   Fri Aug 17 22:49:49 2001 (3B7D836D)
ba62c000 ba62d640   Asapi    Asapi.SYS    Mon Aug 10 18:31:57 1998 (35CF207D)
ba648000 ba649100   dump_WMILIB dump_WMILIB.SYS Fri Aug 17 23:07:23 2001 (3B7D878B)
ba670000 ba670d00   pciide   pciide.sys   Fri Aug 17 22:51:49 2001 (3B7D83E5)
ba6ae000 ba6aec00   audstub  audstub.sys  Fri Aug 17 22:59:40 2001 (3B7D85BC)
ba6ec000 ba6ecd00   dxgthk   dxgthk.sys   Fri Aug 17 22:53:12 2001 (3B7D8438)
ba700000 ba700b80   msmpu401 msmpu401.sys Fri Aug 17 22:59:59 2001 (3B7D85CF)
ba708000 ba708b80   Null     Null.SYS     Fri Aug 17 22:47:39 2001 (3B7D82EB)
bf000000 bf011600   dxg      dxg.sys      Sun Apr 13 20:38:27 2008 (48025323)
bf012000 bf062000   ati2dvag ati2dvag.dll Wed Sep 24 04:17:07 2008 (48D9A323)
bf062000 bf0ee000   ati2cqag ati2cqag.dll Wed Sep 24 03:12:33 2008 (48D99401)
bf0ee000 bf15b000   atikvmag atikvmag.dll Wed Sep 24 03:20:30 2008 (48D995DE)
bf15b000 bf19e000   atiok3x2 atiok3x2.dll Wed Sep 24 03:18:17 2008 (48D99559)
bf19e000 bf570ba0   ati3duag ati3duag.dll Wed Sep 24 03:54:14 2008 (48D99DC6)
bf571000 bf7bae00   ativvaxx ativvaxx.dll Wed Sep 24 03:38:31 2008 (48D99A17)
bf800000 bf9c2c80   win32k   win32k.sys   Mon Sep 15 14:12:42 2008 (48CE513A)
bffa0000 bffe5c00   ATMFD    ATMFD.DLL    Mon Apr 14 02:09:55 2008 (4802A0D3)
 
Unloaded modules:
a4b80000 a4bab000   kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
a4b80000 a4bab000   kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
a4cc0000 a4ceb000   kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
ba749000 ba74a000   drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
a5eda000 a5f05000   kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
a609d000 a60aa000   DMusic.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
a60ad000 a60bb000   swmidi.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
a5f05000 a5f28000   aec.sys 
    Timestamp: unavailable (00000000)
    Checksum:  00000000
ba5f6000 ba5f8000   splitter.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
ba3d8000 ba3dd000   p31usbld.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
ba4a8000 ba4ad000   Cdaudio.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
b9c74000 b9c77000   Sfloppy.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
ba4a0000 ba4a5000   Flpydisk.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
ba498000 ba49f000   Fdc.SYS 
    Timestamp: unavailable (00000000)
    Checksum:  00000000
1: kd> !pool a08b1a71
The pool page you have specified is not in this dump.

Open in new window

0
 
jns_johnsonAuthor Commented:
Justin,
chkdsk /r found some errors on the drive and repaired them. just had another blue screen with the first RAM stick in slot 2 so now testing the same stick in slot 3. the stop message this time was different to the one mentioned in my first post, this time it was STOP: 0x0000007F.

Torimar,
Thanks for your message.  I have run the drivermax driver detective software which has indicated a several out of date drivers. I am now manually updating those drivers.

Thank you both for your help.


0
 
justinmoore14Commented:
Ok, let me know if the next stop error message is the same if you get one. Also, let us know what happens with the driver update when you get a chance.


Justin
0
 
jns_johnsonAuthor Commented:
I have managed to update most of the drivers that were out of date although the Driver Detective still thinks some of them are old versions, but when I update it says I already have newer drivers installed.

No blue screen for over 24 hours now, lets hope it will stay like this. I will post again in 24 hours to let you know if its still not crashing.

Thanks again.
0
 
justinmoore14Commented:
I am glad that you were able to update all of the drives, and thanks for posting back and letting us know. Just keep us posted sometime tomorrow or the next day as it progress (When you have a chance).


Justin
0
 
jns_johnsonAuthor Commented:
Just had 2 more blue screens in the last 24 hours:

Stop: 0x0000000A

Stop: 0x000000D1 - ipnat.sys identified at the bottom.

Any ideas?
0
 
torimarCommented:
Please upload those new dumps again, as they seem to be different to the last ones.

Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL:
 - The Stop 0xA message indicates that a kernel-mode process or driver attempted to access a memory location to which it did not have permission, or at a kernel interrupt request level (IRQL) that was too high. A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own. This Stop message is typically due to faulty or incompatible hardware or software.

Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL:
 - The Stop 0xD1 message indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high. Drivers that have used improper addresses typically cause this error.


So there we are back with the drivers - which were updated in the meantime. Hence we are left to conclude that a) either it wasn't a driver after all; or b) the solution would be not to upgrade the faulty driver but to roll it back to an earlier stable version. When it comes to drivers, "newer" does not automatically mean "better". Which is why I personally only update drivers when an incident forces me to.

If there were only the last STOP error (0xD1 - ipnat.sys) I'd say something was stopping one opf your programmes from establishing an internet connection. Do you happen to remember what applications you were running when it occurred? You didn't have a BSOD for quite a while, so chnaces are we might isolate one particular programme you didn't run for a while and everything was fine; then you ran it again and - BSOD.

Also: are you using the Windows firewall? Disable it and install a third-party firewall like OnlineArmor, Zone Alarm or Comodo - provided you really need a software firewall.
If you already run a third-party firewall, make sure all your applications that require internet access are listed and configured; in case of doubt, uninstall, reboot and reinstall the firewall software in order to reconfigure.
0
 
jns_johnsonAuthor Commented:
Hi,

Attached are the latest minidumps.  Have had the following stop messages since my last post: Stop: 0x0000000A, Stop: 0x000000D3 (win32k.sys mentioned at bottom).

Its hard to identify a particular program that has been running when the blue screens occur, pretty sure nothing other than the startup programs have been running.

I am using ZoneAlarm, not the Windows firewall, I will check now to see if all applications that require internaet access are configured correctly.

Thanks.

Mini022109-01.txt
Mini022109-02.txt
Mini022109-03.txt
0
 
justinmoore14Commented:
Hey, I know this is a long shot and you have already done this once, but could you try to run sfc /scannow again. By the way make sure that before you run this you have the XP DISK out of your computer. This is important. The reason I am asking you to try to run it again is because if it is a driver issue one of them may have screwed up some of your system files (Hints the different BSOD), but is a two part problem (Drivers needed to be updated & System files fixed).

Also, I am still looking at your Minidump files. Did you have any luck with checking on the internet access of the applications?? Hope this helps.


Justin
0
 
jns_johnsonAuthor Commented:
Hi,

I have tried sfc /scannow from command prompt, it asked my to insert the xp disk to cache certain files but did not seem to pick up any errors, if it was meant to?

Have also had a look at the Zone Alarm program configurations for allowing internet access, there are a few programs that have access denied but none of these should require internet access to function. Is there anyway to work out which prgram might be causing the problem?

The computer has been running fine for over 24 hours now and I have been trying to use all the programs I would normally use to get it to go to blue screen, will post back if/when it happens.

Many thanks for your help.
0
 
justinmoore14Commented:
Ok, well that is a good thing at least.

Just for further troubleshooting if you don't mind can you post the names of the Apps that have a label of access denied.

Also, I will let you know if I find anything of us in your Mini dump files.


That's fine just keep us posted. :)


Justin
0
 
torimarCommented:
Those minidumps originate from 3 different(!) STOP errors.
Such a wide range of causes usually would indicate either hardware issues or general system corruption.

But I had another idea:
So far, we have been looking into your hardware drivers expecting the culprit there.
But not only hardware, software uses drivers too, like security suites, firewalls and virus scanners for instance.

There have been loads and loads of complaints about AVG 8 when it appeared. In fact, they made me switch to Avast! on all my Windows installations a year ago. From time to time I still hear reports about issues with AVG.
You are running AVG, and one of the minidumps directly points at one of AVG's drivers. What if you tried a different virus scanner, completely uninstalling AVG? At least until the BSODs return to tell us it wasn't AVG after all.

Also, you say you haven't had any crashes of late: Do you happen to remember whether you updated the AVG engine before this period of relative peace?
That might be an explanation.

0
 
jns_johnsonAuthor Commented:
Actually now you mention it I have only been getting blue screens since switching from Norton Internet Security to AVG 8, although AVG was running for at least 6 months or so before the BSODs.

I will try uninstaling it and using Avast! instead if thats one reccomend?
0
 
torimarCommented:
I have been overly pleased with Avast. No issues whatsoever.
0
 
jns_johnsonAuthor Commented:
I have now installed Avast, left it on last night to do a complete system scan to find today it has BSOD Stop: 0x000000D3 (win32k.sys), restarted the computer and about 5 minutes later I got another blue screen, Stop: 0x0000000D1.


0
 
torimarCommented:
Bad news indeed.

I'm close to admitting to run out of ideas.
There is one small last chance: reconfigure your system to save complete memory dumps on crashing. My Computer > Properties > Advanced > Startup and Recovery.

Then wait for the next BSOD. The dump will be huge, exactly as large as the amount of installed RAM on your system. Zip it and upload to: http://www.ee-stuff.com
(You may login with your normal EE account data, then switch to the "expert area" for uploading).

I cannot promise anything, but if there is a way to trace the history of the memory address causing the crash, then this is it. Unfortunately, there is no warranty of a distinct driver or process name emerging from this backtrace.
0
 
torimarCommented:
ps:
Please do not lose out of sight the option that all this might indeed be due to hardware failure.

I am unaware of methods to test your motherboard for defects, but I know for sure that the only secure method of testing the integrity of your RAM is to replace it with known good RAM - there is no guarantee memtest+ will detect all faults, even if you let it run for 7-8 hours non-stop (which you should do).
0
 
justinmoore14Commented:
Ok, I agree with Torimar about running out of ideas, as well as this may be an hardware issue. However, with that being said I might would try the following. First, I would try to uninstall Zone Alarm and leave the Windows Firewall Disabled. You probably have a lot of setting in Zone Alarm so I am not sure if it is worth it to you or not. Leave Zone Alarm Uninstalled to see if you get another Blue Screen. Second Restart Your Computer. Third if all possible when you go to bed tonight disconnect your computer from the internet (Since your computer is disconnected from the internet you won't have to worry about the firewall being uninstalled). Hope this helps.


Justin
0
 
justinmoore14Commented:
Jns_johnson, any update on this??


Justin
0
 
jns_johnsonAuthor Commented:
Hi, Sorry not to have responed for a while I have been very busy.  It has actually been runing fine for about a week now, unitl just now when I got a BSOD, 0x0000000D1 -  deltaII.sys, which i believe is my soundcard.

I have not yet tried to uninstall ZoneAlarm or set the system to save complete memeory dumps (willl this mean i have to have at least 4gb of free space on my c:drive? - its currently very full, maybe i can get the dump to save to another location?).  I will try and uninstall Zone Alarm tonight, although it could be another week before I get a blue screen, is there an alternative firewall I could use? It would be annoying to stay offline indefinitely waiting for the BSOD.

Thank you both for your help.
0
 
justinmoore14Commented:
Jns_johnson, no problem we are all busy right now, I just was hearing from you alot and then nothing and just wanted to see how things were. :)

As far as Zone Alarm goes, you could use the Windows Firewall temporarily (Ya, I know you probably like Windows Firewall about like the rest of us do). Yes, I do agree it could be very annoying to stay offline and wait for another blue screen, but in actuality if you do use the Windows Firewall you probably will be fine for at least a week to do the test.

Speaking of your HDD being that full just how much free space do you have anyway?? Also, what size is your page file??


Justin
0
 
jns_johnsonAuthor Commented:
Ok I wiil try the Windows Firewall and see what happens.

My C: drive partition (where windows is installed) is 30gb, currently 893 mb free space.  The page file is set to 2046 mb.

Thanks.
0
 
justinmoore14Commented:
Do you have your page file on the other partition??


Justin


0
 
justinmoore14Commented:
Forgot to add sorry, I will be willing to halfway bet this is why you are getting the blue screens. It sounds like you have two partitions. If you have the space I would definitely temporarily move any data that you can over to the other partition to get at least 3GB free. I would try this before uninstalling Zone Alarm as this could be your problem after all.


Justin
0
 
jns_johnsonAuthor Commented:
No the page file is on the C: partition.  I have a total of 5 partitions on two 250gb drives.

The problem I have with my C: drive is that its constantly running out of space and I have now reached the point where I have moved as much as I can to another drive, all that is remaing is the majority of my Program Files (a few larger programs I have reinstalled on my D: partition) and Windows.  Is there any way to increase the size of the C: partition, taking space form another partition?
0
 
justinmoore14Commented:
Ok first question, just out of curiosity why are you constantly running out of space (With that many other partitions). Are you installing that many new programs, are you installing the program and all the extras just to C:, or are you installing them to D:.

Second question, I take it that you have system restore turned on?? Look and see how much disk space that is actually allocated to this. Are you actually using system restore (If not and have no plans to I would definitely turn this off).

Third question, have you looked to see what folder is taking up so much space. Ex. Program Files lets say 5Gb, Windows Folder lets say 3Gb.


There are ways to expand a partition although it is risky. By that I mean about 90% of the time it will go as planned, but there is always that chance that it could go south. There are also numerous programs out there that will allow you to do this just Google Partitioning Software. Here are a few examples and while these are both paid ver. that is not to say there is not a free one out there. Hope this helps.

Partition Magic

http://shop.symantecstore.com/store/symnahho/en_US/DisplayProductDetailsPage/productID.44316200/pgm.6037100/ThemeID.106300/Currency.USD

Acronis Hard Disk Partitioning

http://www.acronis.com/promo/ADD/disk-director-014.html?source=us_google&keyword=partition+software&gclid=CJz076jGlpkCFQIyxwod2UV3ZQ



Justin
0
 
jns_johnsonAuthor Commented:
Thanks for the partition software info, I will look into it.

My Program Files is 15gb, 5gb of which is for Steinberg which is the manufacturer of the audio program I use (the primary function for this pc is audio editing/sequencing so there are a lot of VST plug-in programs installed some of which are quite large). The Windows folder is 5gb, Documents & Setting is 2.6gb. I presume the rest is allocated to page file.

I used to install programs to the C: drive till it started running low on space when i switched to the D: drive. Now I have moved some of the larger programs to the D: drive to try and free up more space. I will try and free up at least 3gb for the memory dump. Not sure why I keep getting low on space, I even moved the TMP folder to the D:drive.  I am often working with quite large audio files which may create temporary files when opened with certain programs.

System restore is off on all drives.


0
 
justinmoore14Commented:
The rest should not all be allocated to the page file, because you are still missing about 6GB (Notice that this will only give you up to 28GB). I say that because more then likely you can't use the full 30GB anyway, but it could still be something like 29GB. I would definitely look around in some of the other folders to see where all your space is going.

As far as you continuing to run out of disk space, I would think this has to do with the Audio files you are working with (Especially if you haven't installed anything else recently). I would open up the audio program and see where it has it's temp location set to. Then go to that location and see what the file size is. It may not be putting the files in the TMP folder anyway, it could be placing them inside of the root of its own folder.

Also, I wouldn't worry about doing the memory dump as of right now. The reason I said at least 3GB is because you have a 2GB page file. Since you only have about 893MB free if you ever go past that point with the page file (Lets say you open an app that pages a lot of its info) you will most definitely get a blue screen. Which it is basically telling you hey I don't know what to do with the rest of this information from this app. You never wont a page file bigger then your available HDD space.


Hope this helps.


Justin
0
 
torimarCommented:
I agree with Justin. Had we known earlier there is so few free space on your system drive, this might have shortened the troubleshooting time quite a bit.

Here's what you can easily move to another drive (if not done so already):
- pagefile
- My Documents
- TMP/TEMP directory
- temporary internet files
- browser cache

Use CCleaner to regain as much space as possible: www.ccleaner.com

Use Spacemonger to get a visual demonstration on what folders consume which amount of space: http://www.sixty-five.cc/sm/v1x.php

Some applications (especially smaller ones) may be relocated from Program Files to another drive without reinstalling; they either don't use the registry or recreate the registry entries to fit their location. Others may be moved with this tool: http://www.funduc.com/app_mover.htm
Use the demo version to move just the most spacehungry two or three applications.
0
 
jns_johnsonAuthor Commented:
Thanks for recommending Spacemonger, much easier way of looking at the folders.
The largest file on my C:drive is called hiberfil.sys, 3.2gb. Pagefile.sys is the next largest at 2.1gb.
Will have ago at moving some of the larger applications.

I have been using CCLeaner periodically, will do another clean again now.  I also moved the TMP/TEMP a while ago.

Is it ok to have the pagefile on a different drive to Windows? I have heard elsewhere this is not advisable.

Thanks again for your help. Had 3 more BSODs in the last 24 hours. When it rains it pours!
0
 
torimarCommented:
It's ok to move the pagefile to another drive. Sometimes you even find it recommended.

I take it you have around 4GB of RAM? Then you will not have to care about optimising your pagefile anyhow, because it will hardly, if ever, be used.

"Hiberfil" is the hibernation file which keeps the complete contents of your memory when you suspend your system to disk instead of switching it off.
Do you use hibernation i.e. "suspend to disk"? If not, this can completely be activated, thus freeing 3.2 GB all at once.
0
 
torimarCommented:
Sorry, meant "deactivated" in the last sentence.
0
 
torimarCommented:
Here's how you disable hibernation:
Go to Control Panel, select Performance and Maintenance, Power Options, Hibernate tab, and uncheck the Enable hibernation box.
0
 
jns_johnsonAuthor Commented:
Brilliant, I have never used the hibernation so have deactivated it, now I have got almost 4gb free on the c:drive.

Do you think just having more free space will stop the blue screens, or should I now enable full memory dumps?
0
 
torimarCommented:
It might very well have been a space/pagefile issue. Windows will behave in utterly strange ways when running out of space.
I guess we'll have to wait and see.

Enabling full memory dumps will mean that your complete RAM (at least 3.2 GB!) will be dumped to disk. Under the given conditions, this will again cost you all your free space and may result in weird additional problems. I shouldn't recommend this unless you have at least 6 GB of free space.

Here's what I suggest:
As soon as you have a bit of time, start defragmenting the drive that is meant to hold your pagefile.
These are some good free defragmenting tools:
Defraggler: www.defraggler.com
Power Defragmenter: http://my.opera.com/rejzor/blog/power-defragmenter-3-0-released

Afterwards let the pagefile be created there.
Once it's gone from the system drive, defragment the system drive. Then let's hope and pray :)
0
 
justinmoore14Commented:
I agree with Torimar, it is usually beneficial to have your page file on a separate disk anyway. Look at it this way, if you disk has to access the data on a hdd and the page file all at once this can't happen. The head of a HDD can only be in one place at one time, thus it either has to go to the data first or the page file first, which slows performance. Anyway, that is my two cents.

You said (I also moved the TMP/TEMP a while ago) what are we up to now on the free space. In other words you said you had 3 more blue screens, was your page file still bigger than the amount of free space you had available.

Also, I to think you should disable hibernation if you are not using it (Especially if you turn the machine off when you are done with it). It is just wasting space on your 30GB HDD. The only thing you might want to keep in mind is if you have a data cable from the UPS connected to your computer (If it is on one) you may want to check its setup and make sure it does not require you use Hibernation if you loose power and the battery goes dead. In other words, on some of the ups when you loose power and they safely shut down your computer depending on how you have it set up it wont completely shutdown your computer it just put it in hibernation mode.


Justin
0
 
justinmoore14Commented:
Sorry guys, I was typing this post as y'all were posting. I hope no more Blue Screens for you. Just let us know.



Justin
0
 
justinmoore14Commented:
Just wanted to check and see if it ever stopped pouring, and to see if things had mellowed out for now? :)



Justin
0
 
jns_johnsonAuthor Commented:
Computer is defintely running smoother but I did have another blue screen on Saturday.

Haven't tried to move the page file, will give that a go and see if it helps.  Also haven't tried uninstalling ZoneAlarm.  Which would you aidvise I tried first?

Thanks.
0
 
justinmoore14Commented:
I would definitely move the page file first. I probably wouldn't fool with uninstalling ZoneAlarm at this point. Also, after you have moved the page file will you give us another count on the total amount of free space again?


Justin
0
 
jns_johnsonAuthor Commented:
Ok will do.  

One question, pagefile currently allocated is 2064mb yet it says recommended 4989mb, is this right?

Also, should I defragment the drive on which i am going to move it on to?

Thanks again.
0
 
justinmoore14Commented:
This typically depends on how much ram you have and is usually 1 and a half times the amount of ram you have. The link below may give you some more useful information if you are interested

http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/core/fnec_evl_wafw.mspx?mfr=true


Also, yes I would definitely defragment the HDD you are going to move the page file to before actually moving it to that drive. You can use Torimar suggestion above for defragmenting. Hope this helps.


Justin
0
 
justinmoore14Commented:
Sounds good...


Thanks for cleaning this one up as well LeeTutor,


Justin
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 24
  • 23
  • 12
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now