Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › x64 users help please
New Posts  All Forums:Forum Nav:

x64 users help please - Page 5

post #41 of 58
Thread Starter 
Quote:
Originally Posted by XFreeRollerX View Post
Have you considered going back to stock clocks and testing from there? Load CMOS defaults and start over... you probably screwed a setting past oblivion, because from what I am seeing.... you either are not telling everything correctly, or you have faulty hardware somewhere in the mix. Regardless, I would go back to defaults and see if you still BSOD
Throughout more testing I found something weird, I used the Pentium system first as that is more sensitive to the BSOD.

XP x64 RTM SP1 = BSOD at "loading Windows" before it even formats the HDD
XP x64 RTM SP2 = BSOD shortly after it does it's first restart, when it enters GUI mode.
SP x64 SP2 (my updated slipstreamed copy) = No BSOD in setup, no bios settings were changed at all and the slipstreamed SP2 copy lasted longer in stress test before BSOD than the others did.

*Scratches head*
     
CPUMotherboardGraphicsRAM
Core i7 6700k @ 4.5 GHz Asus Sabertooth Z170 S ZOTAC GTX 1070 AMP! 8GB G.SKILL Ripjaws V 16GB DDR4 2400 @ 2800 
Hard DriveHard DriveHard DriveHard Drive
Samsung SM951 256GB NVMe Samsung 850 EVO 1TB Toshiba 2TB 7.2K RPM Silicon Power S60 120GB 
CoolingOSMonitorKeyboard
Noctua NH-D15S Windows 10 Pro x64 Acer G257HU Logitech G910 
PowerCaseMouseMouse Pad
EVGA SuperNOVA 750W G2 Cooler Master HAF XB EVO Steelseries Rival Some cheap generic crap 
AudioAudio
Asus Xonar DGX Kingston HyperX Cloud Revolver 
CPUMotherboardGraphicsRAM
Core i7 4710MQ Eurocom X3 R2/Clevo P157SM-A GeForce GTX 965M 4GB @ 1178/1353 MHz 16GB DDR3L 1866 @ 2133 11-11-11-31-2T 
Hard DriveHard DriveCoolingOS
[SSD] Mushkin ECO2 240GB [HDD] HGST 1TB 7.2K RPM SATA III Stock Windows 10 Pro x64 
MonitorKeyboardPowerCase
15.6" 1080P LCD Stock Stock 180W Stock 
MouseAudio
Touchpad/Microsoft Optical Mouse Sound Blaster X-Fi MB3 
  hide details  
Reply
     
CPUMotherboardGraphicsRAM
Core i7 6700k @ 4.5 GHz Asus Sabertooth Z170 S ZOTAC GTX 1070 AMP! 8GB G.SKILL Ripjaws V 16GB DDR4 2400 @ 2800 
Hard DriveHard DriveHard DriveHard Drive
Samsung SM951 256GB NVMe Samsung 850 EVO 1TB Toshiba 2TB 7.2K RPM Silicon Power S60 120GB 
CoolingOSMonitorKeyboard
Noctua NH-D15S Windows 10 Pro x64 Acer G257HU Logitech G910 
PowerCaseMouseMouse Pad
EVGA SuperNOVA 750W G2 Cooler Master HAF XB EVO Steelseries Rival Some cheap generic crap 
AudioAudio
Asus Xonar DGX Kingston HyperX Cloud Revolver 
CPUMotherboardGraphicsRAM
Core i7 4710MQ Eurocom X3 R2/Clevo P157SM-A GeForce GTX 965M 4GB @ 1178/1353 MHz 16GB DDR3L 1866 @ 2133 11-11-11-31-2T 
Hard DriveHard DriveCoolingOS
[SSD] Mushkin ECO2 240GB [HDD] HGST 1TB 7.2K RPM SATA III Stock Windows 10 Pro x64 
MonitorKeyboardPowerCase
15.6" 1080P LCD Stock Stock 180W Stock 
MouseAudio
Touchpad/Microsoft Optical Mouse Sound Blaster X-Fi MB3 
  hide details  
Reply
post #42 of 58
Quote:
Originally Posted by Chozart View Post
aleiro: you're incorrect. 32-Bit Windows XP can only address 4GB at the most (minus some stuff that's needed for overhead and such), but 64-bit Windows XP can address a whole lot more (128GB I believe).

yep, 128GB:
http://msdn.microsoft.com/en-us/library/aa366778.aspx
the OS only allows 3.25gb of ram to be addressed. It is how the os was designed to protect memory space. yes the limit is 4gb but that is for everything and i didnt debate that. You can use a maximum of 3.25gb of ram, its on the msdn website if you care to look for it. Its under memory protection or something.
    
CPUMotherboardGraphicsRAM
Intel 3930k @ stock  Asus P9x79ws EVGA 670 + EVGA 560 Ti 16gb Gskill 2133 @ 1.6v 
Hard DriveOptical DriveOSMonitor
Samsung 830 256Gb + 3.75 Tb ya Win8 5 - 24'' Dell U2412M 
KeyboardPowerCaseMouse
nope... entirely overrated Seasonic 1250w p182 of course... 
Mouse Pad
no 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Intel 3930k @ stock  Asus P9x79ws EVGA 670 + EVGA 560 Ti 16gb Gskill 2133 @ 1.6v 
Hard DriveOptical DriveOSMonitor
Samsung 830 256Gb + 3.75 Tb ya Win8 5 - 24'' Dell U2412M 
KeyboardPowerCaseMouse
nope... entirely overrated Seasonic 1250w p182 of course... 
Mouse Pad
no 
  hide details  
Reply
post #43 of 58
Scroll down on the link I gave you. You'll see this (format adjusted):

Quote:
Originally Posted by MS
Physical Memory Limits: Windows XP
The following table specifies the limits on physical memory for Windows XP.

Limit in 32-bit Windows: 4 GB
Limit in 64-bit Windows: 128GB
Again, 128GB is the limit in 64-bit Windows, which we're talking about here.

Your comments about 3.25GB/4GB ONLY applies to 32-bit Windows.
    
CPUMotherboardGraphicsRAM
E8400 @ 3.8 GHz DFI LANPARTY DK X38-T2R eVGA 8400GS 2GB Mushkin DDR2 800 (single stick) 
Hard DriveOptical DriveOSMonitor
250GB WD SATA None Windows XP Pro 32-bit HP Pavilion f1703 
KeyboardPowerCaseMouse
N/A Corsair HX520 Coolermaster Cavalier N/A 
Mouse Pad
N/A 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
E8400 @ 3.8 GHz DFI LANPARTY DK X38-T2R eVGA 8400GS 2GB Mushkin DDR2 800 (single stick) 
Hard DriveOptical DriveOSMonitor
250GB WD SATA None Windows XP Pro 32-bit HP Pavilion f1703 
KeyboardPowerCaseMouse
N/A Corsair HX520 Coolermaster Cavalier N/A 
Mouse Pad
N/A 
  hide details  
Reply
post #44 of 58
Quote:
Originally Posted by Chozart View Post
Scroll down on the link I gave you. You'll see this (format adjusted):



Again, 128GB is the limit in 64-bit Windows, which we're talking about here.

Your comments about 3.25GB/4GB ONLY applies to 32-bit Windows.
it started with post 31 or so... go back and take a look. As for my point about the OS being specifically programed to use only 3.25gb to protect the memory map:

'The reduction in available system memory depends on the devices that are installed in the computer. However, to avoid potential driver compatibility issues, the 32-bit versions of Windows Vista limit the total available memory to 3.12 GB. See the "More information" section for information about potential driver compatibility issues.

If a computer has many installed devices, the available memory may be reduced to 3 GB or less. However, the maximum memory available in 32-bit versions of Windows Vista is typically 3.12 GB.'


this is for vista and i couldnt find the place i read it for xp but it is the same (http://support.microsoft.com/kb/929605)

So to end the debate ya you could argue that it can support 4gb but it doesnt use that much nor will it map it either
    
CPUMotherboardGraphicsRAM
Intel 3930k @ stock  Asus P9x79ws EVGA 670 + EVGA 560 Ti 16gb Gskill 2133 @ 1.6v 
Hard DriveOptical DriveOSMonitor
Samsung 830 256Gb + 3.75 Tb ya Win8 5 - 24'' Dell U2412M 
KeyboardPowerCaseMouse
nope... entirely overrated Seasonic 1250w p182 of course... 
Mouse Pad
no 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Intel 3930k @ stock  Asus P9x79ws EVGA 670 + EVGA 560 Ti 16gb Gskill 2133 @ 1.6v 
Hard DriveOptical DriveOSMonitor
Samsung 830 256Gb + 3.75 Tb ya Win8 5 - 24'' Dell U2412M 
KeyboardPowerCaseMouse
nope... entirely overrated Seasonic 1250w p182 of course... 
Mouse Pad
no 
  hide details  
Reply
post #45 of 58
I am not talking about the 32-bit version, and neither is anybody else. The topic of this thread is the 64-bit version of Windows XP. I know 32-bit is limited to ~3.something GB, but that's not the topic of this thread.
    
CPUMotherboardGraphicsRAM
E8400 @ 3.8 GHz DFI LANPARTY DK X38-T2R eVGA 8400GS 2GB Mushkin DDR2 800 (single stick) 
Hard DriveOptical DriveOSMonitor
250GB WD SATA None Windows XP Pro 32-bit HP Pavilion f1703 
KeyboardPowerCaseMouse
N/A Corsair HX520 Coolermaster Cavalier N/A 
Mouse Pad
N/A 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
E8400 @ 3.8 GHz DFI LANPARTY DK X38-T2R eVGA 8400GS 2GB Mushkin DDR2 800 (single stick) 
Hard DriveOptical DriveOSMonitor
250GB WD SATA None Windows XP Pro 32-bit HP Pavilion f1703 
KeyboardPowerCaseMouse
N/A Corsair HX520 Coolermaster Cavalier N/A 
Mouse Pad
N/A 
  hide details  
Reply
post #46 of 58
I dunno where "we" are at with this yet.. but I was asked to RE: by pm.

my on x64 and OC'ing.

..As stated in the opening post, I too have noticed lower OC's using x64. This in part [i feel] is due to the larger bit structure. It makes sense to think that you are effectively moving more information through the system at once.. that usually takes a toll somewhere.

To cope: I have been raising the NBv and vcores. There is nothing else to do really [unless you are plagued by another piece of hardware].. the system knows when its stable..you just have to 'play ball' until it gets there, through careful adjustment. I too run/ran a dual-boot XP/x64 just for the purposes of testing the OS's against each other. While I did get better results in all of my benchmarks and real world tests, matching the same OC is still touchy.

The NB takes a tad higher voltage load, gaming under x64..and tRAS timings could not be set the same from one OS to the other. A few other quirks.. Orthos seems to produce a higher load temp under x64..[and I thought 100% utilitzation, was 100% ] and a lower vdroop [as measured on a P5B-DLX and a P5K-vanilla].

My suggestions to you- Run a RegCleaner through a few times..then make sure all of your drivers are up to date..all hardware is seen as functioning correctly by the Hardware manager.. then go through your RAM timings and raise the NBv. If you have a good idea of what your cpu requires for vcore..stick to it! Look for stability in other settings first.

..do you mind re-capping your current settings again..please?
post #47 of 58
what bsod do you get ?
Sunfire
(13 items)
 
  
CPUMotherboardGraphicsRAM
E6300 @3.1 ASUS P5B Galaxy 8800gt 512 4gb g skill pc8000+ 4gb 6400 ballistix 
Hard DriveOptical DriveOSMonitor
500gb+640gb LG super multi Vista home premium 64bit Dell S2309W 
KeyboardPowerCaseMouse
Logitech G15 Corsair HX520 Antec P182 G5 
Mouse Pad
Steelseries pad 
  hide details  
Reply
Sunfire
(13 items)
 
  
CPUMotherboardGraphicsRAM
E6300 @3.1 ASUS P5B Galaxy 8800gt 512 4gb g skill pc8000+ 4gb 6400 ballistix 
Hard DriveOptical DriveOSMonitor
500gb+640gb LG super multi Vista home premium 64bit Dell S2309W 
KeyboardPowerCaseMouse
Logitech G15 Corsair HX520 Antec P182 G5 
Mouse Pad
Steelseries pad 
  hide details  
Reply
post #48 of 58
Quote:
Originally Posted by CL3P20 View Post
I dunno where "we" are at with this yet.. but I was asked to RE: by pm.

my on x64 and OC'ing.

..As stated in the opening post, I too have noticed lower OC's using x64. This in part [i feel] is due to the larger bit structure. It makes sense to think that you are effectively moving more information through the system at once.. that usually takes a toll somewhere.

To cope: I have been raising the NBv and vcores. There is nothing else to do really [unless you are plagued by another piece of hardware].. the system knows when its stable..you just have to 'play ball' until it gets there, through careful adjustment. I too run/ran a dual-boot XP/x64 just for the purposes of testing the OS's against each other. While I did get better results in all of my benchmarks and real world tests, matching the same OC is still touchy.

The NB takes a tad higher voltage load, gaming under x64..and tRAS timings could not be set the same from one OS to the other. A few other quirks.. Orthos seems to produce a higher load temp under x64..[and I thought 100% utilitzation, was 100% ] and a lower vdroop [as measured on a P5B-DLX and a P5K-vanilla].

My suggestions to you- Run a RegCleaner through a few times..then make sure all of your drivers are up to date..all hardware is seen as functioning correctly by the Hardware manager.. then go through your RAM timings and raise the NBv. If you have a good idea of what your cpu requires for vcore..stick to it! Look for stability in other settings first.

..do you mind re-capping your current settings again..please?
He/She makes a lot of sense here.

To re-iterate the temperature difference, you are utilizing different/more transistors in 64-bit calculatiions and 32-bit emulation for non-native codebase.

As far as the NB voltage goes, I have personally seen this be directly affected by amount of RAM/Ram usage in a 64-bit environment.

When you are running the standard sub-4gb, you are staying within a set range. Go into 64-bit, and you are now open to more ram, more throughput, more stress. You can see this by going to stock settings and setting NB voltage to AUTO. The only way for me to really stress ram is to kick off a large 3d scene render, turn on lavalys, nvidia monitor, pcProbe, etc. and check out the NB voltage. Once you've got more than 4 active, the voltage will increase ever so slightly.. 8 gigs, gives this more of an effect. (seen this on 680i, 965, x38)

That being said, all these chipsets are tested up to at least 8GB nowadays, so the voltage shouldn't be flexing like that, i dont think..

It would be interesting to test this concept on a 32-bit server environment using Physical Address Extensions to see how much of a difference the 64-bit instructions make, but sufficient monitoring options are not around for the Dell PowerEdge in my rack (serverworks chipsets FTL)
Jesus PC v5.3
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7-950 Gigabyte X58A-UD3R 5850 GSkill 1600 MHz 4x4GB 
Hard DriveOptical DriveOSMonitor
3x1200.12 500GB RAID 0, 2x2TB Deskstar RAID 1 Samsung Writemaster SATA Gentoo, Windows 7 x64 3x 21.5" Samsungs 
PowerCaseMouse
Thermaltake 750W RocketPwn G500 
  hide details  
Reply
Jesus PC v5.3
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7-950 Gigabyte X58A-UD3R 5850 GSkill 1600 MHz 4x4GB 
Hard DriveOptical DriveOSMonitor
3x1200.12 500GB RAID 0, 2x2TB Deskstar RAID 1 Samsung Writemaster SATA Gentoo, Windows 7 x64 3x 21.5" Samsungs 
PowerCaseMouse
Thermaltake 750W RocketPwn G500 
  hide details  
Reply
post #49 of 58
Thread Starter 
@ CL3P20 As of right now (problems' still there),

PCI-E: 100Mhz
NB Volts: Stock
FSB Volts: Stock
PCI-E Volts: Stock
CPU Vcore: 1.36v idle and load
CPU Vcore Loadline Control: Enabled
Performance Mode: Extreme
CPU Clock: 3400Mhz
FSB: 425Mhz
Memory Multiplier: 2.4x
CPU Multiplier: 8x
RAM Speed: 1020Mhz
RAM Timings: 5-5-5-15
RAM Volts: 2.1v

This all 24 hours stable in XP x86, in XP x64 its lucky to break 15 minutes untill CPU vcore is 1.408v. My load temps with the same vcore and speed are the same as they are in x86 reguardless if x86 or x64 version of Prime95 is used, temps don't budge for me. Memtest 86+ is 21 hours stable, changing up FSB and/or NB volts does nothing but make the BSOD more aggressive, PCI-E speed and volts do nothing, RAM volts and timings do nothing. Pentium system gets the same problem but has an even bigger vcore difference between the two OS and I still get no stop error, just a BSOD, while x86 stable. I asked a number of people here and they all replied XP x64 has no difference with overclocking, and if unstable theres no BSOD, a normal stop error.

@carl25 I get one BSOD and always one BSOD which is MACHINE_CHECK_EXCEPTION with a purple square at the bottom right of the screen. Always the same BSOD and purple square at the same spot, never anything else. I will try and take a pic with the camera later today. The Pentium 4 has the same BSOD saying IRQL_NOT_LESS_OR_EQUAL instead of machine check.
     
CPUMotherboardGraphicsRAM
Core i7 6700k @ 4.5 GHz Asus Sabertooth Z170 S ZOTAC GTX 1070 AMP! 8GB G.SKILL Ripjaws V 16GB DDR4 2400 @ 2800 
Hard DriveHard DriveHard DriveHard Drive
Samsung SM951 256GB NVMe Samsung 850 EVO 1TB Toshiba 2TB 7.2K RPM Silicon Power S60 120GB 
CoolingOSMonitorKeyboard
Noctua NH-D15S Windows 10 Pro x64 Acer G257HU Logitech G910 
PowerCaseMouseMouse Pad
EVGA SuperNOVA 750W G2 Cooler Master HAF XB EVO Steelseries Rival Some cheap generic crap 
AudioAudio
Asus Xonar DGX Kingston HyperX Cloud Revolver 
CPUMotherboardGraphicsRAM
Core i7 4710MQ Eurocom X3 R2/Clevo P157SM-A GeForce GTX 965M 4GB @ 1178/1353 MHz 16GB DDR3L 1866 @ 2133 11-11-11-31-2T 
Hard DriveHard DriveCoolingOS
[SSD] Mushkin ECO2 240GB [HDD] HGST 1TB 7.2K RPM SATA III Stock Windows 10 Pro x64 
MonitorKeyboardPowerCase
15.6" 1080P LCD Stock Stock 180W Stock 
MouseAudio
Touchpad/Microsoft Optical Mouse Sound Blaster X-Fi MB3 
  hide details  
Reply
     
CPUMotherboardGraphicsRAM
Core i7 6700k @ 4.5 GHz Asus Sabertooth Z170 S ZOTAC GTX 1070 AMP! 8GB G.SKILL Ripjaws V 16GB DDR4 2400 @ 2800 
Hard DriveHard DriveHard DriveHard Drive
Samsung SM951 256GB NVMe Samsung 850 EVO 1TB Toshiba 2TB 7.2K RPM Silicon Power S60 120GB 
CoolingOSMonitorKeyboard
Noctua NH-D15S Windows 10 Pro x64 Acer G257HU Logitech G910 
PowerCaseMouseMouse Pad
EVGA SuperNOVA 750W G2 Cooler Master HAF XB EVO Steelseries Rival Some cheap generic crap 
AudioAudio
Asus Xonar DGX Kingston HyperX Cloud Revolver 
CPUMotherboardGraphicsRAM
Core i7 4710MQ Eurocom X3 R2/Clevo P157SM-A GeForce GTX 965M 4GB @ 1178/1353 MHz 16GB DDR3L 1866 @ 2133 11-11-11-31-2T 
Hard DriveHard DriveCoolingOS
[SSD] Mushkin ECO2 240GB [HDD] HGST 1TB 7.2K RPM SATA III Stock Windows 10 Pro x64 
MonitorKeyboardPowerCase
15.6" 1080P LCD Stock Stock 180W Stock 
MouseAudio
Touchpad/Microsoft Optical Mouse Sound Blaster X-Fi MB3 
  hide details  
Reply
post #50 of 58
Quote:
Originally Posted by GigaByte View Post
@ CL3P20 As of right now (problems' still there),

PCI-E: 100Mhz
NB Volts: Stock
FSB Volts: Stock
PCI-E Volts: Stock
CPU Vcore: 1.36v idle and load
CPU Vcore Loadline Control: Enabled
Performance Mode: Extreme
CPU Clock: 3400Mhz
FSB: 425Mhz
Memory Multiplier: 2.4x
CPU Multiplier: 8x
RAM Speed: 1020Mhz
RAM Timings: 5-5-5-15
RAM Volts: 2.1v

This all 24 hours stable in XP x86, in XP x64 its lucky to break 15 minutes untill CPU vcore is 1.408v. My load temps with the same vcore and speed are the same as they are in x86 reguardless if x86 or x64 version of Prime95 is used, temps don't budge for me. Memtest 86+ is 21 hours stable, changing up FSB and/or NB volts does nothing but make the BSOD more aggressive, PCI-E speed and volts do nothing, RAM volts and timings do nothing. Pentium system gets the same problem but has an even bigger vcore difference between the two OS and I still get no stop error, just a BSOD, while x86 stable. I asked a number of people here and they all replied XP x64 has no difference with overclocking, and if unstable theres no BSOD, a normal stop error.

@carl25 I get one BSOD and always one BSOD which is MACHINE_CHECK_EXCEPTION with a purple square at the bottom right of the screen. Always the same BSOD and purple square at the same spot, never anything else. I will try and take a pic with the camera later today. The Pentium 4 has the same BSOD saying IRQL_NOT_LESS_OR_EQUAL instead of machine check.
The Operating system makes no difference i had Vista 32 bit and Vista 64 bit with the same setup i got the same overclock ure BSOD obviously mean something is wrong. IRQL_NOT_LESS_OR_EQUAL is a driver related error.

MACHINE_CHECK_EXCEPTION found some info on it.

0x0000009C: MACHINE_CHECK_EXCEPTION

This is a hardware issue: an unrecoverable hardware error has occurred. The parameters have different meanings depending on what type of CPU you have but, while diagnostic, rarely lead to a clear solution. Most commonly it results from overheating, from failed hardware (RAM, CPU, hardware bus, power supply, etc.), or from pushing hardware beyond its capabilities (e.g., overclocking a CPU).


Run MEMTEST86 for at least two passes (99% of the time, if it passes twice, the memory is perfectly fine). If the memory is showing errors, first try the following before replacing it:

Increase the memory voltage in the Bios by .1V or .2V (start out with .1). Run Memtest again; if it passes this time, you are fine. My memory was not showing errors, but I increased the voltage by .1V and it fixed the problem for me.

If something is overclocked, set it back to norms. This error can be caused by a pissed off CPU (overheating or just generally disgruntled). If not, flash your BIOS to the latest version.

Remove and/or disable any wireless cards or devices in your system.

Uninstall all Nvidia drivers on your system (chipset and graphics). When reinstalling the drivers, DO NOT install the IDE SW driver. Make sure your system is still working at this point by rebooting. If so, install the 77.XX Nvidia graphics drivers if you have an Nvidia card, and work your way up to the 9XXX series until you find instability.

Disable your IDE channels in the bios. This problem has been known to occur due to DVD and CDROM IDE conflicts.

Hope this helps man

Personally id obviously do memtest and put everything back to stock to try resolve this issue.

Mite guess its a hardware fault.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Windows
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › x64 users help please