• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Moved

Jeff7

Jeff7

Lifer
Started a more consolidated thread in tech support; let this one here die.

You're probably going to suggest that I look at the file that is causing it. I'll have to start up a small list,
because out of the 3 times it's done it in the past 2 weeks, it's been a different file every time. I think the first one was a file from nVidia (Geforce4 Ti4200). Second one was a driver for my WinTV-PVR PCI card. The one that just came up today was a USB driver!
My processor and video card are overclocked, however, the FSB is NOT overclocked. Changing that at all affects stability - last time I did it, it pushed the XP1700 to XP2000 speeds. WinXP deleted all user accounts as a result - no admin access, nothing. I had to do safe mode or something like that, and convince it that my files were in fact MINE.
So anyway, any other suggestions to remedy this? The most recent hardware addition was the WinTV-PVR card, and that was maybe a month ago.


Edit: Title changed
 
Well, guess I'll give that a try (I'm an overclocker - never occurs to me to use stock speeds😉) but I don't know why that'd do it. These components have been at these speeds for several months.
 
Sounds like another driver is corrupting pool; writing to memory it doesn't own. Then, the driver that owns that memory comes along and attempts to use that data (which is now invalid), causing the box to crash.

Run verifier.exe from the command line, go to the Settings tab, and enable verifier using Preferred Settings. Reboot for settings to take effect. Verifier will crash the box when a driver corrupts pool and will tell you which driver is at fault.

Then boot to safe mode to disable verifier and replace the driver that verifier caught.

The KB has details on what verifier does. Vendors should run verifier against their drivers before shipping them, but many don't.
 
Two updates:

Originally posted by: NogginBoink

Run verifier.exe from the command line, go to the Settings tab, and enable verifier using Preferred Settings. Reboot for settings to take effect. Verifier will crash the box when a driver corrupts pool and will tell you which driver is at fault.

Then boot to safe mode to disable verifier and replace the driver that verifier caught.

The KB has details on what verifier does. Vendors should run verifier against their drivers before shipping them, but many don't.
Click to expand...

Ok, I ran verifier.exe, but it does not quite look the way you describe it. There is no Settings tab when I load it - there are only radio buttons (think that's the name for them):
Create standard settings
Create custom settings (for code developers)
Delete Existing Settings
Display Existing settings
Display information about the currently verified drivers


2: I ran verifier: Create Standard Settings -> Automatically select all drivers.
Rebooted, got a BSOD. It said that "A driver has caused a DMA error and should be replaced."
However, it did not say what driver or file caused it. All it said at the bottom was:
STOP:0x000000E6 (0x0000001E, 0x00000000, 0x00000000, 0x00000000)

Nothing about which file though.
 
I don't know what the heck that thing did, but not my system is running like a 386 with a meg of RAM. Just loading up Notepad.exe takes about 20 seconds now; the system is extremely sluggish. It seems to have trouble just scrolling pages now.

Edit: Ok, I ran verifier again, this time used the Delete Existing Settings, now system runs normal.
Sorry for going ahead without fully knowing what I'm doing, but that's how I learn. 🙂
 
Originally posted by: Jeff7
I don't know what the heck that thing did, but not my system is running like a 386 with a meg of RAM. Just loading up Notepad.exe takes about 20 seconds now; the system is extremely sluggish. It seems to have trouble just scrolling pages now.

Edit: Ok, I ran verifier again, this time used the Delete Existing Settings, now system runs normal.
Sorry for going ahead without fully knowing what I'm doing, but that's how I learn. 🙂
Click to expand...

Yes, verifier is very expensive to run. Which is why it's off by default. Verifier checks every call a driver makes to certain core OS functions to make sure valid data is being passed in. This is incredibly expensive, but when you've got a misbehaving driver, often it's the only way to find it.

EDIT: I see that the interface for verifier changed between W2K and WXP. Sorry; I was describing the W2K interface, didn't realize it'd changed.
 
try to make sure under System Properties (windows key-break) ->Advanced->Performance->Settings->Advanced->Memory Usage is set for Program Files...system cache doesn't seem to work right with XP...I couldn't use R6PROBE and had a ton of SCSI hangs and crashes...now so far things are smooth as my japanese g/f 😉
 
Ok, got more info; I think I found the trigger: recording video with the WinTV-PVR card. Not watching recorded shows, not watching TV, but just recording. The weird thing about this is that I'd expect it to cause a crash in the PVR's drivers. Nope. The file that crashed was usbuhci.sys. Here's what it said:

STOP: 0x000000D1 (0xD7BCE288, 0x00000002, 0x00000000, 0xF88E0E6F
usbuhci.sys Address: F88E0E6F Base: F88DE000, Datestamp: 3d6ddc30


So whose fault is it? VIA's USB drivers, Hauppauge's WinTV drivers, or both?


Edit: Ok, a little additional info to baffle and confuse: this is sporadic. It doesn't lock up all the time, nor does it do it right away. I recorded 1.5hrs of TV earlier today without problem. However, just an hour ago, I tried to record an hour-long show, and it locked up sometime in the first half hour with the message above.


Edit2: I just bumped the processor back to its default multiplier (FSB was always at 266). It changed something. Now I got a KERNEL_STACK_INPAGE_ERROR with this:
STOP: 0x00000077 (0x00000001, 0xF8AA1B80, 0x00000000, 0xF8AA1C1C)

What are all these STOP addresses? What do they mean?
 
Edit2: I just bumped the processor back to its default multiplier (FSB was always at 266). It changed something. Now I got a KERNEL_STACK_INPAGE_ERROR with this:
STOP: 0x00000077 (0x00000001, 0xF8AA1B80, 0x00000000, 0xF8AA1C1C)
Click to expand...

That's bad.

That indicates the OS tried to page data in from the hard drive and it never got there. Most always hardware problems either in the disk controller or the disk itself; could be the disk controller driver but not likely.
 
Well I did upgrade to the recent 4-in-1's when they came out. Could that be it?
My hard drive is an IBM 60GB 7200rpm drive; think the model is IC35L060AVVA07-0 - just checked IBM's website; seems this is a 120GXP drive. The IBM SMARTDefender utility says the drive is healthy, as does scandisk.
 
More info and a bump. Predictably, it crashed again while recording video off of TV after about 45 minutes or so (estimated by the size of the videofile). I'm at default CPU speed now. Usbuhci.sys crashed again. The address is similar to the first time this file caused the crash. The usbuhci.sys crashes are DRIVER_IRQ_NOT_LESS_OR_EQUAL errors. Here are the two so far, the top one occurred 2 days ago; the second one just today:

usbuhci.sys Address: F88E0E6F, Base at F88DE000, Datestamp 3d6ddc30
usbuhci.sys Address: F8910E6F, Base at F890E000, Datestamp 3d6ddc30

Anyone have any ideas here? Why does the TV card cause a USB driver to crash?
Another curious thing: once the BSOD comes up saying that "the system has been shut down to prevent damage," the sound from the TV keeps playing through the soundcard like nothing happened.

Something curious on the Microcrap Knowledgebase - says here that the latest version of the usbhci.sys file is 5.1.2600.28, and that it is included with DisService Pack 1. However, the version that comes with SP1 seems to be 5.1.2600.1106! It seems there is also a 5.1.2600.4 version of this file. Could it be that I don't have the latest version? Where the heck do I get it??
 
SP1 Removed! New error! Don't like it either - ntfs.sys is the problem now.
PAGE_FAULT_IN_NONPAGED_AREA
STOP: 0x00000050 (0x85E202C1, 0x00000000, 0xF8504524, 0x00000000)
ntfs.sys Address: F8504524 Base at F84A10000, datestamp 3d6de5c1

What the heck is dying here?
 
Update. Did a fresh install of WindowsXP and SP1. I installed the drivers according to the instructions at Hauppauge's website. Now I don't get a BSOD anymore. The system just completely locks after recording video awhile - a dead lock; completely unresponsive to anything.
 
As if it'd do any good, I might as well tell Hauppauge tech support about this. I finally seem to have gotten it working (hopefully). The fresh install of WinXP above didn't include the 4-in-1's. I installed them; that seemed to help a bit initially, but then the system locked up on me again while I was just watching TV. Their FAQ's for solving lockups (which are kind of tough to get to) said to reduce the PCI latency timer to 12 clks. I wouldn't have thought that reducing the latency would help to improve stability. Well, I increased it from 48 to 128. I've now been able to record several hours of TV, and it hasn't locked up yet. Let's hope that did it now. Hauppauge's technical support response was less than helpful - amounted to "reinstall the drivers."
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top