stop 0x0000024 BSOD

[QueBert]

The BSOD isn't saying ntfs.sys just the stop number, but I ran MS's minidump analyzer and it's the file behind it. I ran chkdsk on all my partitions and it found problems on a partition, but it's not the one Vista is on, might even have been on my external drive.

any ways, I installed Vista x64 today, I had XP telling me last weekend my E: NFTS was corrupt and needed to be fixed, I ran chkdsk it did it's thing and everything seemed okay. I've had this BSOD 2x on my new Vista install already. Google is turning up too many suggestions on what to do, MS's offical page about this seems weird (don't know how else to explain it) They make it sound like the ntfs.sys file needs to be replaced but they're talking about xfering the drive to a new system and doing all sorts of stuff.

I'm going to run Spinrite tonight on the drive to make sure it's not bad, I'll try to dig up another IDE cable. System is new, was built a few months ago and has ran pretty well. I'm not taking this lightly as it might be a bad HD or hardware problems, but none of the links I'm finding on google seem to break down how serious this is. I'm going to do a full backup tomorrow but if it's a software issue causing it, or the ntfs.sys file is bad a backup-restore won't help things.

Is it not possible to simply to boot to a UBCD and delete the ntfs.sys and copy the file off my Vista DVD?


System wise

p35 MB
Audigy 2
Nvidia 8600
Seagate 500gb IDE


right now I just noticed in my system devices SM BUS controller doesn't have drivers installed, going to go look that up.

Drivers I put the sound/video and nothing else.



I would appreciate any insight here I'm not 100% confident with reading 20 different things to go on Google.

 

[mechBgon]

You might want to run Memtest86+ overnight to confirm your RAM is stable, if you haven't done so already. If it's fancy RAM intended for above-normal voltages, make sure to go into your BIOS and manually set the voltage to the intended spec.

 

[QueBert]

the specs on my mem are iffy, it's Crucial memory but made for Newegg (has an Egg logo on it) can't find much about it, they have little LED's on them and I was told by a few to run it at some outrageously high v like 2.1. Sounds like too much to me, I can definitely run memtest tonight and try pushing the mem voltage up a hair in my BIOS. I did not think this could be a memory issue with all the NTFS links but it can't hurt to make sure I suyppose.

thanks for the quick reply

 

[dclive]

Originally posted by: QueBert
The BSOD isn't saying ntfs.sys just the stop number, but I ran MS's minidump analyzer and it's the file behind it. I ran chkdsk on all my partitions and it found problems on a partition, but it's not the one Vista is on, might even have been on my external drive.

any ways, I installed Vista x64 today, I had XP telling me last weekend my E: NFTS was corrupt and needed to be fixed, I ran chkdsk it did it's thing and everything seemed okay. I've had this BSOD 2x on my new Vista install already. Google is turning up too many suggestions on what to do, MS's offical page about this seems weird (don't know how else to explain it) They make it sound like the ntfs.sys file needs to be replaced but they're talking about xfering the drive to a new system and doing all sorts of stuff.

I'm going to run Spinrite tonight on the drive to make sure it's not bad, I'll try to dig up another IDE cable. System is new, was built a few months ago and has ran pretty well. I'm not taking this lightly as it might be a bad HD or hardware problems, but none of the links I'm finding on google seem to break down how serious this is. I'm going to do a full backup tomorrow but if it's a software issue causing it, or the ntfs.sys file is bad a backup-restore won't help things.

Is it not possible to simply to boot to a UBCD and delete the ntfs.sys and copy the file off my Vista DVD?


System wise

p35 MB
Audigy 2
Nvidia 8600
Seagate 500gb IDE


right now I just noticed in my system devices SM BUS controller doesn't have drivers installed, going to go look that up.

Drivers I put the sound/video and nothing else.



I would appreciate any insight here I'm not 100% confident with reading 20 different things to go on Google.

Read my .sig, debug the dump, post the results of '!analyze -v'

 

[nullpointerus]

EDIT: It's best to debug the BSOD first, but at some point you should do the following:

Originally posted by: QueBert

...

System wise

p35 MB
Audigy 2
Nvidia 8600
Seagate 500gb IDE

...

right now I just noticed in my system devices SM BUS controller doesn't have drivers installed, going to go look that up.

SM Bus --> need chipset drivers

You need the Intel INF Update Utility, probably the latest version:

http://downloadcenter.intel.co...ing%20Systems&lang=eng

 

[mechBgon]

Originally posted by: QueBert
the specs on my mem are iffy, it's Crucial memory but made for Newegg (has an Egg logo on it) can't find much about it, they have little LED's on them and I was told by a few to run it at some outrageously high v like 2.1. Sounds like too much to me, I can definitely run memtest tonight and try pushing the mem voltage up a hair in my BIOS. I did not think this could be a memory issue with all the NTFS links but it can't hurt to make sure I suyppose.

thanks for the quick reply

Another problem solved by proper application of teh voltagez: http://forums.anandtech.com/me...id=34&threadid=2148267

If the RAM is a rebadge of Crucial's Tracer, that's rated for 2.2 volts as well. Could be some other issue, but Memtest86+ will probably help you determine if it's the RAM. Anyway, good luck! :beer:

 

[robisbell]

I'd run UBCD and run the diagnostic on the drives.

 

[QueBert]

thanks dclive, I followed your sig, maybe you can shed some light, ANY help would be greatly appreciated man!

 

[QueBert]

Originally posted by: mechBgon

Originally posted by: QueBert
the specs on my mem are iffy, it's Crucial memory but made for Newegg (has an Egg logo on it) can't find much about it, they have little LED's on them and I was told by a few to run it at some outrageously high v like 2.1. Sounds like too much to me, I can definitely run memtest tonight and try pushing the mem voltage up a hair in my BIOS. I did not think this could be a memory issue with all the NTFS links but it can't hurt to make sure I suyppose.

thanks for the quick reply

Another problem solved by proper application of teh voltagez: http://forums.anandtech.com/me...id=34&threadid=2148267

If the RAM is a rebadge of Crucial's Tracer, that's rated for 2.2 volts as well. Could be some other issue, but Memtest86+ will probably help you determine if it's the RAM. Anyway, good luck! :beer:

2.2 really? I think the default is 1.7 so that's a pretty big difference. I think the might be Tracer re bagged because I remember seeing those Tracers and they had LED's on them.
I will definitely pump the voltage up on them.

 

[dclive]

Remove Kapersky (replace with another AV) and tell us if the dumps continue. Please post dump analysis to the forums so all can learn and see what's done.

 

[QueBert]

thanks Dclive will do, if I run Windows Media Center I get the BSOD every time, well both times I've ran it. With a STOP C2 and Bad_Pool_Caller

 

[dclive]

Post the dump analysis.

 

[QueBert]

*UPDATE*
ran Windows Media Center and added files fine, but when I ran it again and tried to add more files from my E: it BSOD'ed again so I've figured out something is up with my E: this is the latest analysis. Got the same BSOD crash 3 times when adding files from my E, it crashes before it actually starts to add any files.


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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000022,
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------

GetUlongFromAddress: unable to read from fffff8000196a2f0



BUGCHECK_STR: 0x19_22

POOL_ADDRESS: 0000000000000000

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

PROCESS_NAME: ehshell.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff800018b0d0d to fffff8000184dc90

STACK_TEXT:
fffff980`17af5618 fffff800`018b0d0d : 00000000`00000019 00000000`00000022 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff980`17af5620 fffff800`0193d19b : fffff980`00000001 00000000`00000001 00000000`00000000 fffff980`00000000 : nt! ?? ::FNODOBFM::`string'+0x3bc1
fffff980`17af5690 fffff980`00926214 : 00000000`00000000 fffff980`17af59e0 fffff800`01969200 00000000`6d665346 : nt!ExFreePoolWithTag+0x39b
fffff980`17af5750 fffff980`00926b40 : fffff980`17af58b0 fffffa80`02210ab0 fffff880`03dd3aa0 fffff880`0816ba00 : Ntfs! ?? ::NNGAKEGL::`string'+0x36
fffff980`17af5780 fffff980`0091c257 : fffffa80`024fe6c0 fffff880`03dd3bd0 fffff880`03dd3aa0 fffffa80`0492f180 : Ntfs!NtfsCommonClose+0x86d
fffff980`17af5850 fffff980`004e921a : 00000000`00000000 fffffa80`02210ab0 00000000`00000001 00000000`00000003 : Ntfs!NtfsFsdClose+0x2b7
fffff980`17af5950 fffff980`004e9691 : fffffa80`04931040 fffffa80`0492d6c0 fffffa80`02770f00 fffffa80`02210ad0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x20a
fffff980`17af59c0 fffff800`01abcf3e : fffffa80`029e8f20 fffffa80`029e8f20 00000000`0000000a 00000000`001dec28 : fltmgr!FltpDispatch+0xd1
fffff980`17af5a20 fffff800`018597dd : fffffa80`018af8a0 fffffa80`029e8f20 00000000`00000000 00000000`00000000 : nt!IopDeleteFile+0x17e
fffff980`17af5ab0 fffff800`01ab54b1 : fffffa80`0258d500 00000000`00000544 fffffa80`02d05060 fffffa80`02d05060 : nt!ObfDereferenceObject+0x1dd
fffff980`17af5b20 fffff800`01ab4ead : 00000000`00000544 fffffa80`018af8a0 fffffa80`0258d5d0 00000000`00000003 : nt!ObpCloseHandleTableEntry+0x271
fffff980`17af5bd0 fffff800`0184d733 : fffffa80`02d05060 fffff980`17af5ca0 00000000`05d38fd0 fffff980`17af5ca0 : nt!ObpCloseHandle+0x9d
fffff980`17af5c20 00000000`77cb036a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001deed8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77cb036a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+3bc1
fffff800`018b0d0d cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+3bc1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 470c35b4

FAILURE_BUCKET_ID: X64_0x19_22_nt!_??_::FNODOBFM::_string_+3bc1

BUCKET_ID: X64_0x19_22_nt!_??_::FNODOBFM::_string_+3bc1

Followup: MachineOwner
---------

 

[robisbell]

run UBCD and run the diagnostic on the drives.

 

[QueBert]

going to do that tonight while I'm sleeping, takes awhile to run, can check on it in the morning should be done then.

 

[robisbell]

should not take that long.

 

[bwatson283]

yes they can!

 

[dclive]

Run verifier from a command prompt, turn on the default options, reboot, see if you can repro the crash steps, then analyze the latest/just-generated dump and post the '!analyze -v' bits.

 

[QueBert]

Seagate tools found nothing wrong with the drive, I ran the long test. Haven't ran memtest yet (going to do that in a minute)

ran verifier, the default options never got past the last screen asking about drivers, default option there was unsigned drivers and it would tell me none found. I select the all drivers option and it said it needed to reboot. Going to do that and reproduce the crash since I know how to set it off now.

 

[QueBert]

Ok, not sure if I did the Verifier right, but when it told me to reboot and I did I got a BSOD c4 klif.sys error, rebooted again same crash. So I booted last known good config and got to my desktop, windows checked the crash and told me it was the antivirus. Google turned up klif.sys being part of my AV, which I have disabled.

dclive (or anyone who knows) when you said run verifier with default options, the 2nd default is for drivers, if I leave it on the default option it says "no unsigned driver found" so I selected "automatically select all drivers" was that wrong? here is the latest dump. I know my AV caused it, but maybe there's something else here?

thanks again all for the help, I'm off to run memtest, I did bump my mem voltage from 1.7 to 2.0, when I select 2.2 my MB shows the value in red and says it's not advisable to run, not sure if I should push it or not. (mem's rated 2.2)


1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Parameter 1 = 0x1000 .. 0x1020 - deadlock verifier error codes.
Typically the code is 0x1001 (deadlock detected) and you can
issue a '!deadlock' KD command to get more information.
Arguments:
Arg1: 000000000000003d, ERESOURCE address is unaligned.
Arg2: 0000000000000000, 0
Arg3: 0000000000000000, 0
Arg4: fffff98008e44d14, bad resource address passed in.

Debugging Details:
------------------




BUGCHECK_STR: 0xc4_3d

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: smss.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80001c0837d to fffff8000184dc90

STACK_TEXT:
fffff980`12544038 fffff800`01c0837d : 00000000`000000c4 00000000`0000003d 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff980`12544040 fffff800`01c0922e : fffffa80`055ba760 fffff800`0197ab60 00000000`00000009 fffff800`01c19d67 : nt!VerifierBugCheckIfAppropriate+0x3d
fffff980`12544080 fffff800`01c178b4 : 00000000`00000101 fffff800`0193c857 fffffa80`055ba750 00000000`00000002 : nt!ViResourceAcquireSanityChecks+0x2e
fffff980`125440c0 fffff980`08e24707 : 00000000`00000101 00000000`00000001 00000000`00000009 fffff980`12544180 : nt!VerifierExAcquireResourceExclusiveLite+0x14
fffff980`125440f0 00000000`00000101 : 00000000`00000001 00000000`00000009 fffff980`12544180 00000000`00000000 : klif+0xa707
fffff980`125440f8 00000000`00000001 : 00000000`00000009 fffff980`12544180 00000000`00000000 fffff980`08e3a658 : 0x101
fffff980`12544100 00000000`00000009 : fffff980`12544180 00000000`00000000 fffff980`08e3a658 fffff800`0197ab60 : 0x1
fffff980`12544108 fffff980`12544180 : 00000000`00000000 fffff980`08e3a658 fffff800`0197ab60 00000000`00000000 : 0x9
fffff980`12544110 00000000`00000000 : fffff980`08e3a658 fffff800`0197ab60 00000000`00000000 00000000`000001c4 : 0xfffff980`12544180
fffff980`12544118 fffff980`08e3a658 : fffff800`0197ab60 00000000`00000000 00000000`000001c4 00000000`00000076 : 0x0
fffff980`12544120 fffff800`0197ab60 : 00000000`00000000 00000000`000001c4 00000000`00000076 00000000`00000000 : klif+0x20658
fffff980`12544128 00000000`00000000 : 00000000`000001c4 00000000`00000076 00000000`00000000 fffff980`125441b0 : nt!PspCreateProcessNotifyRoutine
fffff980`12544130 00000000`000001c4 : 00000000`00000076 00000000`00000000 fffff980`125441b0 fffff800`0197ab60 : 0x0
fffff980`12544138 00000000`00000076 : 00000000`00000000 fffff980`125441b0 fffff800`0197ab60 fffff800`0197ab60 : 0x1c4
fffff980`12544140 00000000`00000000 : fffff980`125441b0 fffff800`0197ab60 fffff800`0197ab60 00000000`00000000 : 0x76
fffff980`12544148 fffff980`125441b0 : fffff800`0197ab60 fffff800`0197ab60 00000000`00000000 00000000`00000000 : 0x0
fffff980`12544150 fffff800`0197ab60 : fffff800`0197ab60 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff980`125441b0
fffff980`12544158 fffff800`0197ab60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspCreateProcessNotifyRoutine
fffff980`12544160 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff980`12544ca0 : nt!PspCreateProcessNotifyRoutine
fffff980`12544168 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff980`12544ca0 fffff800`018b9b3f : 0x0
fffff980`12544170 00000000`00000000 : 00000000`00000000 fffff980`12544ca0 fffff800`018b9b3f fffffa80`055ba040 : 0x0
fffff980`12544178 00000000`00000000 : fffff980`12544ca0 fffff800`018b9b3f fffffa80`055ba040 fffff980`12544ca0 : 0x0
fffff980`12544180 fffff980`12544ca0 : fffff800`018b9b3f fffffa80`055ba040 fffff980`12544ca0 fffffa80`055ba040 : 0x0
fffff980`12544188 fffff800`018b9b3f : fffffa80`055ba040 fffff980`12544ca0 fffffa80`055ba040 00000000`61506553 : 0xfffff980`12544ca0
fffff980`12544190 fffff800`01a94cc3 : 00000000`000001c4 fffffa80`055ba9b0 fffff880`00088770 fffff880`0079ebe0 : nt! ?? ::FNODOBFM::`string'+0x115cf
fffff980`125441e0 fffff800`01adb53d : fffffa80`055ba040 00000000`000ef088 fffff980`12544501 fffff980`125444b4 : nt!PspInsertThread+0x4d3
fffff980`12544440 fffff800`0184d733 : fffffa80`055af060 00000000`000ef008 00000000`02000000 00000000`02000000 : nt!NtCreateUserProcess+0x60d
fffff980`12544bb0 00000000`77af0d6a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000eefe8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77af0d6a


STACK_COMMAND: kb

FOLLOWUP_IP:
klif+a707
fffff980`08e24707 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: klif+a707

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: klif

IMAGE_NAME: klif.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 476104cc

FAILURE_BUCKET_ID: X64_0xc4_3d_klif+a707

BUCKET_ID: X64_0xc4_3d_klif+a707

Followup: MachineOwner

 

[QueBert]

More problems... I tried to uninstall my AV software, when I go to the add remove programs it sits there for a second and BSOD'ed, got the 024, rebooted and tried to remove it again, got a STOP c2 BAD_POOL_CALLER.
Like I said before, this is a clean Vista install, NO 3rd party software (have disabled AV from MSconfig until I can physically remove it) Driver wise, I have the latest ATI/INTEL/Canon/Creative drivers installed and nothing else. Seagate tools reported my HD is reading fine. I seem to get the errors when it tries to read my E: or parts of my C: I can duplicate the BSOD now every time, it still happens randomly sometimes though.

here is the latest dump, I won't paste the one before that.



1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000113d, (reserved)
Arg3: 0000000000000000, Memory contents of the pool block
Arg4: fffffa800278d180, Address of the block of pool being deallocated

Debugging Details:
------------------

GetUlongFromAddress: unable to read from fffff80001d6a2f0
GetUlongFromAddress: unable to read from fffff80001d6a2f0



POOL_ADDRESS: fffffa800278d180

BUGCHECK_STR: 0xc2_7

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80001d3c475 to fffff80001c4dc90

STACK_TEXT:
fffff980`14ce2688 fffff800`01d3c475 : 00000000`000000c2 00000000`00000007 00000000`0000113d 00000000`00000000 : nt!KeBugCheckEx
fffff980`14ce2690 fffff980`00926206 : 00000000`00000000 fffff980`14ce29e0 00000000`00000009 00000000`00000000 : nt!ExDeferredFreePool+0x9ca
fffff980`14ce2750 fffff980`00926b40 : fffff980`14ce28b0 fffffa80`023427d0 fffff880`04d22aa0 fffff880`04c51600 : Ntfs! ?? ::NNGAKEGL::`string'+0x28
fffff980`14ce2780 fffff980`0091c257 : fffffa80`05b80010 fffff880`04d22bd0 fffff880`04d22aa0 fffffa80`048cc180 : Ntfs!NtfsCommonClose+0x86d
fffff980`14ce2850 fffff980`004e921a : 00000000`00000000 fffffa80`023427d0 00000000`00000001 00000000`00000003 : Ntfs!NtfsFsdClose+0x2b7
fffff980`14ce2950 fffff980`004e9691 : fffffa80`048ce040 fffffa80`048ca330 fffffa80`01cbdf00 fffffa80`023427f0 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x20a
fffff980`14ce29c0 fffff800`01ebcf3e : fffffa80`0497b4c0 fffffa80`0497b4c0 00000000`0000000a 00000000`06cceb28 : fltmgr!FltpDispatch+0xd1
fffff980`14ce2a20 fffff800`01c597dd : fffffa80`018ba360 fffffa80`0497b4c0 00000000`00000000 00000000`00000000 : nt!IopDeleteFile+0x17e
fffff980`14ce2ab0 fffff800`01eb54b1 : fffffa80`053d6600 00000000`00000600 fffffa80`0591d7f0 fffffa80`0591d7f0 : nt!ObfDereferenceObject+0x1dd
fffff980`14ce2b20 fffff800`01eb4ead : 00000000`00000600 fffffa80`018ba360 fffffa80`053d66b0 000007fe`00000003 : nt!ObpCloseHandleTableEntry+0x271
fffff980`14ce2bd0 fffff800`01c4d733 : fffffa80`0591d7f0 fffff980`14ce2ca0 00000000`06ff9e70 00000000`c0000034 : nt!ObpCloseHandle+0x9d
fffff980`14ce2c20 00000000`76f4036a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`06cceb38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f4036a


STACK_COMMAND: kb

FOLLOWUP_IP:
Ntfs! ?? ::NNGAKEGL::`string'+28
fffff980`00926206 90 nop

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: Ntfs! ?? ::NNGAKEGL::`string'+28

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 472149fb

FAILURE_BUCKET_ID: X64_0xc2_7_Ntfs!_??_::NNGAKEGL::_string_+28

BUCKET_ID: X64_0xc2_7_Ntfs!_??_::NNGAKEGL::_string_+28

Followup: MachineOwner
---------

 

[mechBgon]

I'm off to run memtest, I did bump my mem voltage from 1.7 to 2.0, when I select 2.2 my MB shows the value in red and says it's not advisable to run, not sure if I should push it or not. (mem's rated 2.2)

For the record, if you were at 1.7 volts, that was 0.1V below even the "plain vanilla" 1.8V DDR2 standard spec, and 0.5V below what your RAM is rated for. If you do see errors in Memtest86+, you could get some (dare I say) normal DDR2 that runs stable at 1.8V, or heave some more voltage at the stuff you've got (and then test again), despite the motherboard's caution notice. Expect Memtest86+ to take a while... running it overnight is a good option.

 

[QueBert]

overnight is always good, I planned to run it a single 100% run for today so I can use the PC, it doesn't seem to crash much on it's own, well at least I know what NOT to do so I have a good shot at it running sort of decently.

it might have been 1.8 I wasn't paying close attention *DOH* it's @ 2 now and will stay there until I figure something out, I don't want to go messing with changing a bunch of things when I don't even know what's causing my problems in the first place.

Everything on Google is telling me C2 Bad_Pool_Caller is generally a bad driver, I have almost none installed and the ones I do are the most recent. But with my past dealings with Nvidia & Creative's drivers in XP maybe I shouldn't expect Vista 64 bit to be smooth sailing

as far as normal DDR2 @ 1.8 stable, my box had been stable for the most parts for months, I haven't changed anything hardware wise, and everything was bought new in September.

 

[mechBgon]

Originally posted by: QueBert
overnight is always good, I planned to run it a single 100% run for today so I can use the PC, it doesn't seem to crash much on it's own, well at least I know what NOT to do so I have a good shot at it running sort of decently.

it might have been 1.8 I wasn't paying close attention *DOH* it's @ 2 now and will stay there until I figure something out, I don't want to go messing with changing a bunch of things when I don't even know what's causing my problems in the first place.

Everything on Google is telling me C2 Bad_Pool_Caller is generally a bad driver, I have almost none installed and the ones I do are the most recent. But with my past dealings with Nvidia & Creative's drivers in XP maybe I shouldn't expect Vista 64 bit to be smooth sailing

as far as normal DDR2 @ 1.8 stable, my box had been stable for the most parts for months, I haven't changed anything hardware wise, and everything was bought new in September.

In light of that, it seems less likely to be the memory voltage, then. Carry on :beer:

 

[QueBert]

UPDATE, I let Memtest run 2 times with no problems, I reboot and my system shuts down before the POST screen 2 or 3 times, stays off a second and comes back on saying an overclock as failed. I go into my BIOS and set things to default. Only change I've made was memory was 1.8 to 2.0, memories rated @ 2.2 so 2.0 should be fine, but whatever. back on my desktop trying to figure out what to test next.

silly question because this is fat too obvious, but if the problem isn't a bad HD but infact somehow the ntfs.sys is corrupt, why can't I just boot to UBCD with NTFS DOS, delete the ntfs.sys file, pop in my Vista DVD and copy the new one? My hardware seems to all be functioning properly, at least with the tests I've ran.