EVIL SCOTSMAN - Please Read

[bflagg]

pappavis... does it still crash on a IDE Drive setup also?

(I'm supprised "Dr Evil" didn't ask..)

[Guest EVIL-SCOTSMAN]

dr evil didnt ask, cuz as pappa said i r god, i know all :p

 

except where i put my weed last night before i went to bed, i wake up, i can smell it but cant find it :(

 

 

EDIT:

nevermind, i found it in my 2 year old sons mouth :)

 

joke before some of you lot call the nspcc, I R childless

[pappavis]

Hi Evil.

 

As you probably have read from one of my previous posts i have bought the Asrock 939Dual-SATA2 mobo and Athlon64 3200+ processor. Stuck inside it used to be 2*512Mb DDr400 memory modules. These 2*512Mb DDR400 is what i have borrowed from my 100% working Athlon XP3200+ system which is my current lo-mac and internet rig. Also connected is a Samsung Spinpoint 160Gb Sata-I harddisk drive, and an 4-years old DVD-drive connected as secondary master.

 

The crash on startup (see previous posts) which i ussed to have was (probably) due to bad memory modules.

 

Problem is, i cant get WinXP to install but WinME does install without a hitch:rolleyes:.

 

The mobo, and mobo config is as follows:

When rebooting, pressing F2 gets one into the mobo config settings screen, i remained with all settings (cpu, MBR, etc etc) on default. Though it show the memory incorrectly to be DDR333 and not DDR400.

Chipset setup: all default.

 

When installing winXP these happens.

1. Reboot computer.

2. WinXP starts CD-rom and boots into the DOS thingy, copying files for setup.

3. I press F6 to install the RAID driver, then selects the WinXP/Win2003 RAID driver, its copied from floppy disk.

4. Some more copying, then i must press ENTER to continue installation.

5. Right then after pressing enter, <<spontaneous reboot>>, or sometimes i can continue without crash to..

6. I press F8 to accept the license agreement.

7. I select installation partition.

8. I press ENTER so the start copying files onto the install could start.

9. Now, right after (8), BLUE screen crash with message about IRQL_NOT_INLINE.

 

WTF?

 

Worth mentioning: <<edited>>

1. WinME install without a hitch on the exact same hardware specs and harddisk.

2. I have tryd to change the frontside bus speed to 1000Mhz etc but that doesnt help, the errors of 5 to 8 remains.

 

Any ideas?? TIA!!

[Yellonet]

Hi Evil.

 

As you probably have read from one of my previous posts i have bought the Asrock 939Dual-SATA2 mobo and Athlon64 3200+ processor. Stuck inside it used to be 2*512Mb DDr400 memory modules. These 2*512Mb DDR400 is what i have borrowed from my 100% working Athlon XP3200+ system which is my current lo-mac and internet rig. Also connected is a Samsung Spinpoint 160Gb Sata-I harddisk drive, and an 4-years old DVD-drive connected as secondary master.

 

The crash on startup (see previous posts) which i ussed to have was (probably) due to bad memory modules.

 

Problem is, i cant get WinXP to install but WinME does install without a hitch:rolleyes:.

 

The mobo, and mobo config is as follows:

When rebooting, pressing F2 gets one into the mobo config settings screen, i remained with all settings (cpu, MBR, etc etc) on default. Though it show the memory incorrectly to be DDR333 and not DDR400.

Chipset setup: all default.

 

When installing winXP these happens.

1. Reboot computer.

2. WinXP starts CD-rom and boots into the DOS thingy, copying files for setup.

3. I press F6 to install the RAID driver, then selects the WinXP/Win2003 RAID driver, its copied from floppy disk.

4. Some more copying, then i must press ENTER to continue installation.

5. Right then after pressing enter, <<spontaneous reboot>>, or sometimes i can continue without crash to..

6. I press F8 to accept the license agreement.

7. I select installation partition.

8. I press ENTER so the start copying files onto the install could start.

9. Now, right after (8), BLUE screen crash with message about IRQL_NOT_INLINE.

 

WTF?

 

Worth mentioning: <<edited>>

1. WinME install without a hitch on the exact same hardware specs and harddisk.

2. I have tryd to change the frontside bus speed to 1000Mhz etc but that doesnt help, the errors of 5 to 8 remains.

 

Any ideas?? TIA!!

If you only have one harddrive you don't need any RAID drivers.

 

Sounds like RAM problem with the bluescreen and reboots.

Before I had 2 x 256 MB PC2700 memory, and every time I tried to install XP I got a bluescreen at some point of the install and had to do everything again... it turned out that one of the modules apparently had passed a test it shouldn't have as it was only really a PC2100 but marked as a PC2700, when I turned down the speed of the RAM all problems went away.

 

Try lowering the speed of you RAM to 133 MHz but keep the FSB at 200 and the multiplier at 11.

[Guest EVIL-SCOTSMAN]

first off, if its showing wrong memory speed, are you using the latest bios ? as my asus board used to show wrong speed til i flashed.

 

if your motherboard only has 2 memory slots and you have filled both, then yes the memory will be at its correct speed, as athlon64s (unless its the san diego core) cannot handle 400mhz with all memory slots full, so if your last pc had 4 slots and you only used 2, then you would get 400mhz, now if this new board has 2 slots and you have used them both, then 333mhz is the max without overclocking that you will get

 

now for the irq part, go into your bios and turn off all the crap that you can to free up irq's, i had exact same problem with my board, too many features, too little irqs, which resulted in irq bsod's.

turn off raid as you dont need it, turn off parallel port as you sure as hell probably wont need that unless you have uber old printer or such like, if you dont use firewire and your board has it, turn it off, also same with any game/midi ports.

 

basically turn off everything that you dont need in the irq list, also set irq to auto and that will make windows decide roughly which irqs instead of the bios deciding.

 

with 1 hdd, you dont need to be pressing f6 for raid drivers, i use spinpoint in my pc and it works fine with windows drivers til i put in the chipset, if i install nvidia storage drivers, meh pc goes tits up, so i never install them no more, i just use the smbus and ethernet drivers from the nf4 installer.

 

yellownet, 2 different speeds of ram installed on one pc, by rights you wouldnt need to turn down the speed, as soon as the mobo detects them the pc2700 will auto detune to run at the same speed as the 2100, i used to mix ram speeds all the time and it would auto detune to the slower ram stick.

 

EDIT:

your board has 4 slots so it should run at 400mhz. manually set the memory to 400mhz and dont use the auto function as default options never ever set things to there proper speeds. also make sure its the latest bios you are using, you will need another pc to download the bios and put it on a startup disc along with the flash tool. so 3 items you need, startup floppy, bios and bios flash tool. since you cant use the windows utility to flash the bios.

 

also, if this is an old harddrive that you used in another pc, get rid of the partition and mbr, and then recreate the mbr and partition, windows cd will not do this, you will need another tool.

 

was the irq error, inline or was it this.

 

irq not less or equal.

 

was it similar to that ? if it was the one i wrote, then disabling irq stuff in your bios should fix it.

 

also a long shot, but go into the bios and check the temps of your cpu for 5-10 minutes, if they stable then cool, but it maybe overheating due to the cpu not being seated or not pasted correctly and just by chance its overheating and shutting down at the same spot.

 

unlikely but you never know.

[Yellonet]

yellownet, 2 different speeds of ram installed on one pc, by rights you wouldnt need to turn down the speed, as soon as the mobo detects them the pc2700 will auto detune to run at the same speed as the 2100, i used to mix ram speeds all the time and it would auto detune to the slower ram stick.

They were (supposed to be) the same speed but one of the sticks were faulty and didn't work in it's intended speed.

Not sure how the speed detection works but the motherboard detected both as DDR333. Took a while before I figured out that one of them were faulty :(

[Guest EVIL-SCOTSMAN]

ya, unless they were exact same speed then you can run into problems on certain boards, the majority wouldnt have a problem unless the stick itself was physically messed up, and with ram, its either, its working properly or its messed up. also a lot of mobos tend to dislike certain ram types and certain configs.

 

if there is one thing i hate, its ram that you have to test for hours and days to see if its bust. its never a quick and easy thing unless the ram fails within seconds on ram tests and mem86. but yea, what you said happen can happen in the odd case if the board doesnt like that particular ram.

[Yellonet]

ya, unless they were exact same speed then you can run into problems on certain boards, the majority wouldnt have a problem unless the stick itself was physically messed up, and with ram, its either, its working properly or its messed up. also a lot of mobos tend to dislike certain ram types and certain configs.

I bought them together and they have the exact same markings, but one works in 166 MHz and the other don't.

My guess is that it somehow slipped passed the speed check and was wrongly marked as PC2700 when it should have been a PC2100.

I think all RAM is made the same, just as CPU's, and get their 'mark' depending on the frequenzy they can handle.

[Guest EVIL-SCOTSMAN]

na, all ram and cpus are not made the same, they vary from week to week.

 

sometimes you get a really good set that were made for example on the 6th week of 2005 then they change slightly in the following weeks and may not be as good as the ones that went before it.

 

same with cpus, some exact same cpus say fx53 for example, there multiplyer was unlocked before, but after a certain week they got locked and rebranded. fx55 even, as one week it had the older core and now they have the san diego cores, but there both called the fx55 and the san diego core kill the older core.

 

but there still the same speed and same frequency.

 

basically there is slight differences from week to week in ram and cpu's. no 2 will ever be the same unless made from the same batch at the very same time, thats why they sell dual channel kits, both are 2 sticks of ram that were made at the same time and were kept together for ease of use as they are physically identical.

[pappavis]

Thus far no joy. I have changed the HTT-thingy setting to 200Mhz (at 1000mhz is max), memory to DDR133, disconnected the SATA drive.

Only using 1 memory module now a Infeneon DDR400 256Mb.

 

GRRRR, i wasnt made for this cr*p! I wanna put the things together, switch on and all must work.

 

tech support is all that i need, prob is i bought all components from differnt shops so i cant take anything back to 1 central place for testing..

 

Evil, i read your comments with interest, gonna tweak some more.

[Guest EVIL-SCOTSMAN]

ok, why did you change the hyper transport technology thingy, and also why did you change your memory to 133 ?

 

am confused, in the memory part, set your memory manually to 400mhz, if it doesnt disply 400mhz manually then "YOU NEED A BIOS FLASH" as that is a common problem.

 

memory not displaying its proper speed after being set manually on a new motherboard 9 times out of 10 is due to a bios flash being needed.

 

your board will come with a windows bios program that you can flash while still in windows, but as you cannot get that far then you will have to get the newest non beta bios for your motherboard and then create a startup floppy disc, and copy the bios file and the bios flash tool to that floppy, or you can create a startup floppy, and then on another floppy put the bios and the bios flash tool. Then you will have to flash from startup after it boots from the startup floppy.

 

chances are a bios flash will sort out your memory problem, as for the irq problem, well do as i suggested, disable all uneeded connections like parallel port, serial port, firewire and midi port if your board has one. Thos options will be in your bios and will probably be under onboard devices or something like that, just disable them, keep your nvidia lan as thats your ethernet connection enabled, disable anything that says lan boot rom, as you probably will not need that.

 

for now, if i was you and going by what you have said, i would first of all flash my bios to the newest non beta version, then go from there.

 

also never leave things on auto, as they will 99.9% of the time, never give you the proper speed of the device that is set to auto.

 

also leave your htt at auto or the highest it will go, auto is cool for that, auto isnt good for cpu or ram.

 

read the manual for the motherboard, as you may have the sticks of memory in the wrong configuration, and maybe thats why it isnt working properly, but i really suggest a bios flash if you think you can do that.

I know alot of people dont feel comfortable flashing a bios, but if anything goes wrong, it will probably have the asus crash free bios, where if the flash goes wrong, then you can just put in the motherboard cd when you next restart your pc, and it will auto reflash to the bios that it left the factory with. So basically you cannot mess it up if something goes wrong, not like older pc's where if the flash went wrong, then you either had to get a new bios chip or a new motherboard. Its not like that anymore with new motherboards.

 

EDIT:

 

whats the motherboard BIOS revision that you are using now ? if you can tell me that, i maybe able to tell you if a newer bios is available and if it sorts any of the problems you are having.

[pappavis]

Hoi all.

 

BTW, this thread is public coz i hope other peeople could bebefit from this discussion.

 

I have managed to reinstall WinME on the machine. THen i downloaded the latest BIOS version 1.6 from the Asrock website, flashed it and rebooted.

I then disabled in BIOS all parallel, MIDI, gameport, serialport and... now time to catch some sleep.. :P

[Yellonet]

na, all ram and cpus are not made the same, they vary from week to week.

 

sometimes you get a really good set that were made for example on the 6th week of 2005 then they change slightly in the following weeks and may not be as good as the ones that went before it.

That has to do with what material goes into the chips and that the machines that make them are different. What I meant was that they are manufactured in the same way.

 

same with cpus, some exact same cpus say fx53 for example, there multiplyer was unlocked before, but after a certain week they got locked and rebranded. fx55 even, as one week it had the older core and now they have the san diego cores, but there both called the fx55 and the san diego core kill the older core.

 

but there still the same speed and same frequency.

Of course not all CPU's are made the same.

Again, what I meant was that what a CPU will sell as depending on how high frequenzy it can handle, and that depends on if it was manufactured good or bad. If there are difference cores they're not really the same even if they have the same name.

 

Anyway, I bought two sticks of RAM and on could be used in it's 'sell' speed and the other couldn't.

[Yellonet]

ok, why did you change the hyper transport technology thingy, and also why did you change your memory to 133 ?

 

am confused, in the memory part, set your memory manually to 400mhz, if it doesnt disply 400mhz manually then "YOU NEED A BIOS FLASH" as that is a common problem.

Are you sure that it should display "400 MHz"? My BIOS displays the real frequenzy, 200 MHz.

[pappavis]

A quick post, i run WinME wihout a problem. WTF?!?

 

This is what i have done so far, with getting winXP, and Win2k to install. Same procedure for both:

1. Disabled parallel, serial ports, audio, LAN,.

2. Use only 1 DDR400 512Mb DIMM (Infeneon) from my current XP3200+ setup.

3. Underclocked memory speed to DDR333.

4. I left memory vooltage, cpu voltage etc and that 2-2-2-2 things alone (wtf are those?) . It stays on [Auto].

5. Memory burzst i have changed to 2.

6. Then reboot into WinME without a problem.

7. Inserted winXP CD, enter serial number, it copies files, it reboots the comp.

8. When its restarting I ignore RAID (the press F6 for RAID) drivers.

9. I press ENTER to start the install.

10. I accept the licnse agreement.

11. I select the installation drive.

12.1 WinXP: spontaneous reboot.

12.2 Win2k: BLSOD with IRQL_NOT_INLINE .

 

Remarks:

1. Other things such as the 2T etc i left alone, coz when i do change anything on it the machine just wont show up the POST screen. I have to remove power, wait a few secs then i can get to POST and then it asks me if i wanna revert to defaults.

2. I have tried install with a total of 7 DIMMs in various configurations and memory banks.

3. The dimms are 2*512MB DDR333, 4*256Mb DDR400 also tried with 1*512MB DR400.

4. While applying (3) cahnged memory speed to DDR166, DDR333 etc.

5. Mixed/or matched the DIMMS in all thinkable combinations with each other.

6. Tried to get a Dual Channel with DIMMS of same capacity and speed, even DDR333 with a DDR400 gave dual channel.

7. While trying all the above, WinME was running and starting without a problem, while both WinXP and Win2k dont wanna get past their IRQL_NOT_INLINE error.

8. I have evendisabled SATA controller, IDE controller but then i cant boot the machine, thinking that perhaps the IDE controller causes a IRQ conflict.

9. While trying all of the above, per infividual step, rebooted the comp. I have probably rebooted 560 times in the past 12 hours, in an effort to get WinXP to install.

 

I am getting really pissed off.

 

See here winME running without a problem, using mixed DIMMs of DDR400 and DDR333. Even RealVNC runs on it without a problem.. I had to reanable the LAN for this.

 

This is what Cpu-z reported:
CPU-Z Report	



CPU-Z version 1.31.	

CPU(s)	
Number of CPUs	1
Name	AMD Athlon 64 3200+
Code Name	Venice
Specification	AMD Athlon(tm) 64 Processor 3200+
Family / Model / Stepping	F F 0
Extended Family / Model	F 2F
Brand ID	4
Package	Socket 939
Core Stepping	DH-E3
Technology	90 nm
Supported Instructions Sets	MMX, Extended MMX, 3DNow!, Extended 3DNow!, SSE, SSE2, SSE3, x86-64
CPU Clock Speed	2000.1 MHz
Clock multiplier	x 10.0
HTT Bus Frequency	200.0 MHz
L1 Data Cache	64 KBytes, 2-way set associative, 64 Bytes line size
L1 Instruction Cache	64 KBytes, 2-way set associative, 64 Bytes line size
L2 Cache	512 KBytes, 16-way set associative, 64 Bytes line size
L2 Speed	2000.1 MHz (Full)
L2 Location	On Chip
L2 Data Prefetch Logic	yes
L2 Bus Width	128 bits

Mainboard and chipset	
Motherboard manufacturer	
Motherboard model	939Dual-SATA2, 1.00
BIOS vendor	American Megatrends Inc.
BIOS revision	P1.50
BIOS release date	12-6-2005
Chipset	ALI M1695 rev. 00
Southbridge	ALI M1563 rev. 70
Sensor chip	Winbond W83627HF


Memory	
DRAM Type	DDR-SDRAM
DRAM Size	1536 MBytes
DRAM Frequency	200.0 MHz
FSB:DRAM	CPU/10
CAS# Latency	2.5 clocks
RAS# to CAS#	3 clocks
RAS# Precharge	3 clocks
Cycle Time (TRAS)	15 clocks
Bank Cycle Time (TRC)	22 clocks
DRAM Idle Timer	256 clocks

Software	
Windows version	Microsoft Windows Millennium Edition 
DirectX version	7.0a

[pappavis]

This is a CPU-Z info from the WinME installtion:

 

[pappavis]

UPDATE: Motherboard was probably faulty. Now all is well :wink:.

 

I just went out to the local computershop (4 minutes walk from me) , they had a Asrock 939Dual-Sata2 mobo in stock. Bought one. Installed the EXACT same memory etc as the initial and !WOW! no more crashes, win2k is installing now :)

 

So far all settings are on [Auto] just to see that it works.

 

Bloody hell, i wasted 1 week since last thursday, ahh well..:eek:

[Yellonet]

UPDATE: Motherboard was probably faulty. Now all is well :wink:.

 

I just went out to the local computershop (4 minutes walk from me) , they had a Asrock 939Dual-Sata2 mobo in stock. Bought one. Installed the EXACT same memory etc as the initial and !WOW! no more crashes, win2k is installing now :)

 

So far all settings are on [Auto] just to see that it works.

 

Bloody hell, i wasted 1 week since last thursday, ahh well..:eek:

Good to hear it worked out and you're a wasted week and/or a PC experience wiser ;)

 

What brand was the faulty motherboard?

[Guest EVIL-SCOTSMAN]

Are you sure that it should display "400 MHz"? My BIOS displays the real frequenzy, 200 MHz.

 

all depends on bios, mine displys 133 all the way upto 533 or 633 i cant remember.

 

good to hear that you got it figured, pain in the ass trying to figure it out tho, i been there a few times, and at the moment am kinda there myself. my pc refuses to shutdown properly.

 

not sure if its acpi problem or software, but its locking up on shutdown screen, even after formats and hardware has been taken out to see if that was the cause.

 

5 months on and am still trying to figure it out, sometimes it does shutdown other times it wont.

 

but its good to hear that the board was faulty,xp was probably calling on a piece of hardware that win me didnt ask for, thus the channel/road to that particular hardware was faulty and locking up the pc.

 

goood to hear anyway

 

MERRY XMAS you 2

[Yellonet]

all depends on bios, mine displys 133 all the way upto 533 or 633 i cant remember.

 

good to hear that you got it figured, pain in the ass trying to figure it out tho, i been there a few times, and at the moment am kinda there myself. my pc refuses to shutdown properly.

 

not sure if its acpi problem or software, but its locking up on shutdown screen, even after formats and hardware has been taken out to see if that was the cause.

 

5 months on and am still trying to figure it out, sometimes it does shutdown other times it wont.

 

but its good to hear that the board was faulty,xp was probably calling on a piece of hardware that win me didnt ask for, thus the channel/road to that particular hardware was faulty and locking up the pc.

 

goood to hear anyway

 

MERRY XMAS you 2

What board is that? A friend of mine had an Abit motherboard that was faulty... the PC would hang at shutdown or take a really long time shutting down, then it just got worse, problems that came and went.. programs that wouldn't install correctly, all kinds of crap. It all went away when he got a new board.

 

I've had a non-working Abit board myself... don't buy them anymore.

[Guest EVIL-SCOTSMAN]

asus a8n sli deluxe, its nforce4 chipset problems, ive come across other people who have same problem, and its all over the nforce4 boards.

 

this is the 2nd one, and it did it on the fist aswell, i think its nforce4 drivers or chipset probs or dualcore prob.

 

pc works perfect apart from that, ive had 5 months of testing, and no matter what i do it still does it, so am just gonna start enjoying the pc instead of looking for a problem that i aint never gonna be able to fix in a hurry.

[Yellonet]

Ouch... that sucks.

[Guest EVIL-SCOTSMAN]

standby/hibernate be my friend :)

[Yellonet]

Hehe...