Author Topic: Skuzzy And Computer Guru"s (Read 1168 times)

boxboy28 · « **Reply #15 on:** January 28, 2003, 12:23:54 PM »

well i did set it up so i could get the BSOD and its sum crazy bellybutton long ansty looking thing! How do i search for the Error code on the net? where do i go?

Im gonna mess with the RAM and stuff to tonight!

WILL DO GTS let me get home!

qts · « **Reply #16 on:** January 28, 2003, 02:28:48 PM »

Tell us what it says. The bit that's critical is the bit which says 'STOP ...'. You can then look up the STOP code on MS's website.

boxboy28 · « **Reply #17 on:** January 28, 2003, 06:27:42 PM »

alright here 1 of the 4 different error codes i have encountered!

STOP: 0x000000D1(0xE246A2E0,0x00000002,0x00000000,0xF6C5085)

smwdm.sys - adress F6C25285 base at F6BE000, date stamp 3d78f68e

(all in one tuner when tring to wat TV)

stop 0x0000008E(0x00000005,0xB0a662CA,0xAAE297C,0x00000000)

Pcc_PFW.SYS adress B01662CA base at B063000, date stamp 3d36cc8C

these error code i cant find a thing about ive hed 2 different ones as well but il gonna pull memeory chips and swap them like suggested above right not to see whats up!

Box

PS guys thats for all your help it is most appreiceated!

Skuzzy · « **Reply #18 on:** January 28, 2003, 06:42:52 PM »

Tha particular error came from the sound card driver.

Shane · « **Reply #19 on:** January 28, 2003, 07:48:36 PM »

Quote

Originally posted by Skuzzy
Tha particular error came from the sound card driver.

does the all-in-wonder also function as a sound card? if so, perhaps he needs to disable the onboard sound?

WxMan · « **Reply #20 on:** January 28, 2003, 08:36:22 PM »

The P4PE will work fine with one stick of memory

boxboy28 · « **Reply #21 on:** January 28, 2003, 09:28:53 PM »

Well i dont think it can function as thsound card but i pulled the memory sticks swaped em and tried ever differnt config i could but thats not working either. Sound like this onboard sound toejam is the problem!
Skuzzy i have noticed that the mouths and sound are off sound is way before the mouths are when veiwing TV (looks like a bad karate movie)

ill keep ya all informed:confused:

mrsid2 · « **Reply #22 on:** January 29, 2003, 02:03:08 AM »

Boxboy search and install latest drivers for your sound and video.

Random reboots however would make me suspect a heat related problem.. Do you have sufficient air circulation in your box? Is the heatsink/fan combo secured?

What temps is your system showing? I had big instability problems once that were caused by the chipset heating to much.

San · « **Reply #23 on:** January 29, 2003, 03:11:38 AM »

Here are the stop code errors off Microsoft’s site

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.
Interpreting the Message
This Stop message has four parameters:
1.   Memory referenced.
2.   IRQL at time of reference.
3.   Type of access (0x00000000 = read operation, 0x00000001 = write operation).
4.   Address that referenced memory.
Resolving the Problem
For additional troubleshooting suggestions that apply to all Stop errors, see "Stop Message Checklist" later in this appendix.
·   Stop 0xD1 messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
For more information about Stop 0xD1 messages, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources. Search using keywords winnt, 0x000000D1, and 0xD1.

"STOP 0x0000008e" Error Message During Windows XP Setup
The information in this article applies to:
·   Microsoft Windows XP Professional
·   Microsoft Windows XP Home Edition
This article was previously published under Q315335
SYMPTOMS
When you install Microsoft Windows XP, you may receive a STOP error message similar to one of the following during Setup:
STOP 0x0000008e
or

STOP 0x00000050 PAGE_FAULT_IN_NON_PAGED_AREA
Additionally, if you troubleshoot by removing all unnecessary hardware devices that are installed on the computer, and then running Setup, you may receive an error message similar to the following:
Setup cannot copy the file Setupdd.sys.
CAUSE
This behavior can occur if one of the following conditions is true:
·   One or more of the random access memory (RAM) modules that are installed on your computer are faulty.
·   The RAM configuration is incompatible with Windows XP.
RESOLUTION
To troubleshoot and resolve this behavior, follow these steps:
1.   Remove some of the memory modules that are installed on the computer. Leave at least the amount of RAM required for the computer to start and run Windows XP.

The recommended amount of RAM to run Windows XP is 128 megabytes (MB). The minimum is 64 MB and the maximum is 4 gigabytes.

For example, if two 256-MB memory modules are installed on your computer, remove one of the memory modules.
2.   Restart the computer, and then run Setup.
3.   If you again receive the error message that is described in the "Symptoms" section of this article, proceed to step 4.
4.   Remove a different memory module, or install the RAM in a different memory slot.
5.   Restart your computer, and then rerun Setup.

You may need to restart your computer several times in order to identify the specific memory modules that are not working correctly.
MORE INFORMATION
For information about how to add and remove RAM, contact the manufacturer of the computer or see the documentation that is included with your computer.

For additional information about Windows XP Setup, click the article numbers below to view the articles in the Microsoft Knowledge Base:
306824 Release Notes for Windows XP Setup Contained in the Home.txt File
286463 Release Notes for Windows XP Setup Contained in the Pro.txt File
286647 Windows XP Read1st.txt File Contents
For information about how to contact your hardware manufacturer, click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base:
65416 Hardware and Software Third-Party Vendor Contact List, A-K

60781 Hardware and Software Third-Party Vendor Contact List, L-P

60782 Hardware and Software Third-Party Vendor Contact List, Q-Z
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

Boxboy

I think the fastest way to resolve this would be to Download and run memtest like Bloom said. If its not your ram, (and your temps are ok) leave a good stick of ram in, download Sandra from here http://www.sisoftware.co.uk/?location=update I would then remove everything but the video card run the Sandra burn in wizard for 10 to 15 min if it makes it with no lock up then start putting stuff back in one at a time make sure you run Sandra after each item goes in.

Is there any chance you could have missed a standoff when you installed the motherboard a shorted motherboard can cause this also.

boxboy28 · « **Reply #24 on:** January 29, 2003, 08:39:27 AM »

all temps are fine nothing to suggest other wises the case is open and its in a cold basement.

I cant get that memtest to run i tried it last night after i was pulling the ram out.

All stand offs are installed, im not to sure what you mean about possible missing one. Hell i could have shorted the board buut i dont think i did(im very safe about the static E)

Well tonight ill try to get that memtest to run and if it passes then its on to SANDRA.

Thanks Box

mrsid2 · « **Reply #25 on:** January 29, 2003, 10:41:12 AM »

Boxboy you just told on another thread that you didn't reinstall your OS after swapping motherboards. Was that in this machine?

If so, I'd expect that's the root of your problems.

boxboy28 · « **Reply #26 on:** January 29, 2003, 11:14:44 AM »

no completely diff machine

San · « **Reply #27 on:** January 29, 2003, 01:39:20 PM »

Most cases come with a few stand offs pre installed. When you install your motherboard and line up all the stand offs, if you have an extra standoff that does not line up with a hole its easy to miss it. This will short the motherboard to the case.

boxboy28 · « **Reply #28 on:** January 30, 2003, 06:35:40 PM »

well i tried every thing! sandra the memory test all that stuff.!!!!!!

I said fuggit and i went and bought a sound blaster AUDIGY2 put it in (had a few problems) once i got it all set up all test have been succesful. I had a feeling it was the onboard sound and them so far seems to prove it!

So for all our future referances onboard sound SUCKs ! if your having a problem its most likely the source! i have never ever had good luck with them before or even still!

TY for all the help guys it just pisses me off that after all this its just a sound card issue!

to all those who have tried to help!

BOX

mrsid2 · « **Reply #29 on:** January 31, 2003, 12:30:22 AM »

Box in my experience sounblasters are the ones that suck. They cost way too much, have often crappy sound quality and cause a huge flood on the pci bus which can hinder performance on many motherboards.

Some onboard soundsets are extremely high quality, like the Nforce APU which I'm using now. It's extremely cpu efficient, has quality matching the best soundblaster can offer and comes with no extra price. I'd say that's quite a good deal.

So 'future reference' couldn't be more far off in this case.