Blue screen when using 2 memory modules !!

Hi,
When I use two memory modules (installed on bank 1 and 2), windows xp fails to install randomly (sometimes at the beginning, sometimes even after a rebooting...) and generates a blue screen of death... !
However, they are correctly visible at boot time.
But when I use only one module, it works fine (I tried with the first and the second module separately). These modules are strictly the same.
What should I do now ?
Just a remark : my FSB is at 100 Mhz. Is it normal ? (newbie question)
Thanks
David
Here is my configuration :
Athlon XP 2600+
2x512 Mb DDR PC2700 (MDT)
120 Gb UDMA6 IDE master on IDE1
80 Gb UDMA5 IDE slave on IDE1
DVD UDMA2 IDE master on IDE2
Firewire disabled
RAID activated (but not used so far)
LAN and Audio enabled

I think 300 watts is a way too SMALL for what your trying to run. Check your label on the power supply and see what your 3.3 volt and 5 volt supply amperage is. Anything less than 200 watts combined or about 28amps on 3.3 and 35 amps on the 5volt is going to give you grief. You need a bigger power supply. Recommend Antec or Enermax as the solution. Antec SL350 or higher.
Newegg has good prices and great service
Antec Power Supplies

Similar Messages

Blue Screen When using Magic Bullet Instant HD in Premiere Pro CC

When using Adobe Premiere Pro CC, using Magic Bullet Instant HD to convert a 720p video to a 1080p. The system will blue screen and the problem dll file seems to be hal.dll.
What is the cause of this?
and how to fix it?
System Specs:
OS: Win 7 Ultimate 64 bit
CPU: i7 3770k 3.5 Ghz
RAM: 16 GB
GRAPHICS: AMD Radeon HD 7700
MOTHERBOARD: ASRock Z77 Extreme6
STORAGE: 1 TB local disk, 3 2TB Expanded driver attached to 3.0 port
Wireless mouse and keyboard

Hi Kris,
I have checked all the three dumps, they all showed the same bugcheck 124.
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8010821028, be200000, 21136}
Probably caused by : GenuineIntel
Followup: MachineOwner
6: kd> !analyze -v
* Bugcheck Analysis *
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8010821028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000021136, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: Adobe Premiere
CURRENT_IRQL: f
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
STACK_TEXT:
fffff880`0350ab58 fffff800`03413a3b : 00000000`00000124 00000000`00000000 fffffa80`10821028 00000000`be200000 : nt!KeBugCheckEx
fffff880`0350ab60 fffff800`035d6463 : 00000000`00000001 fffffa80`10817950 00000000`00000000 fffffa80`108179a0 : hal!HalBugCheckSystem+0x1e3
fffff880`0350aba0 fffff800`03413700 : 00000000`00000728 fffffa80`10817950 fffff880`0350af30 fffff880`0350af00 : nt!WheaReportHwError+0x263
fffff880`0350ac00 fffff800`03413052 : fffffa80`10817950 fffff880`0350af30 fffffa80`10817950 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0350ad50 fffff800`03412f0d : 00000000`00000008 00000000`00000001 fffff880`0350afb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0350ad90 fffff800`03406e88 : 000007ff`fda7f140 00000000`00000b40 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0350adc0 fffff800`034be4ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0350adf0 fffff800`034be313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0350af30 00000000`0352f2c9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`36c0cdd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x352f2c9
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_cache
FAILURE_ID_HASH: {270f58cb-a20a-a72d-6d81-eb8c82f01f7a}
Followup: MachineOwner
Information for Bugcheck 124:
Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR.
Bugcheck 124, This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
Which is probably caused by "GenuineIntel". Make sure we have updated the BIOS drivers, take a check with the hardware tool provided by the manufacturer, or you may take a check with them.
Best regards
Michael Shao
TechNet Community Support

Blue screen when attempting to use the dedicated video card

I keep getting a blue screen when attempting to use the dedicated video card.
I managed to install the AMD driver for it but without the other components like the Catalyst Control Center as it blue screened on startup when attempting to load the Catalyst Control Center.
The OS loads fine. Any applications that don't use the dedicated video card runs fine. All other drivers install fine as well.
Applications like games and Photoshop that switch to the dedicated video card on startup automatically crashes, the OS freezes then a blue screen appears.
What could be causing the problem? This problem just recently appeared. Two weeks ago.

boogs wrote:
I tried installing the drivers for my laptop from HP's support site. Still the same result.
This problem only appeared a few weeks ago. Before that, the same drivers from the HP site installed and functioned normally.
Could this be a problem with the graphics card itself?
Note sure but if we can know the system P/N others can look to see what drivers it has for the graphics to know what is there.
I am a Volunteer to help others on here-not a HP employee.
Replies aren't online 24/7 because of Time Zone differences.
Remember in this Day and Age of Computing the Internet is Knowledge at your fingertips if you choose understand it. -2015-

Computer Blue Screen when VXI chassis is shutdown Using NI VXI-8360T MXI-VXI and PCIe8362 controllers

Problem Description :
Using NI VXI-8360T MXI-VXI and PCIe8362 controllers.
The software I have is Measurement and Automation Explorer version 5.5.0f0 Problem:
We have had both controllers set up and working together to include running other VXI instruments using the MXI bus. The problem we are having is that when the VXI chassis is shutdown, it causes the computer (that has the PCIe8362 card in it and connected to the VXI card bus) to experience a blue screen of death.
With our older 777178-01 VXI-MXI-2 configuration, our computer does not experience the blue screen when shutting down the VXI chassis while the computer is still on. Do you have information or past issues with the computer experiencing a blue screen due to VXI chassis shutdown?
NI Software : Other version
NI Hardware : VXI/VME/MXI device VXI-8360T
Driver Version :
OS :
Windows 7

Are you using NI-VXI 3.8.1 (or later) and supported hardware for VPO (variable power on) support?
http://digital.ni.com/public.nsf/allkb/6B1F05BB5C0E321186257950007424B2
I think you need to "warn" the hardware/driver you're going to turn the chassis off, either via MAX or a programatic call. Sorry I can't give any more specific help, but I've only heard about this and haven't ever done it myself.
- Robert

Windows Blue Screen - when trying to re-sync an IPOD after doing 5 R's

My windows based Itunes failed to recognize my ipod, so I trouble shooted and finally ended up doing the 5 R's.
This resulted in a "Blank Ipod" (after restore).
I was able to successfully get Itunes to recognize my ipod after the restore. That is when a "major problem" occurred.
When my 37 gigs of MP3s on my PC attempt to automatically update onto my "blank ipod", my system crashes giving me the dreaded windows BLUE SCREEN! The error messgae indicates that a physical memory dump occurred and the system shuts down.
I figure it has something to do with all of those gigs trying to update onto the ipod. SO, I start to manually transfer (drag and drop) about 100 mp3s at a time onto the ipod within itunes. It still crashed after the 3rd batch of 100 mp3s.
Has anyone experienced this? Does it have anything to do with Mirosoft's newest IE vunerability? I use Firefox usually, but sometimes HAVE to use IE. What can I do?
This really *****.
thanks for your help.
Zeppy
Dell Dimension Windows XP

hi zeppy!
hmmmmmm. a 0x7E? that's not the most commonly reported BSOD code here.
but the MS KB seemed to have at least one clue for us.
(1) sometimes people can get blue screens when they plug in an ipod if their FireWire, USB, or dock has gone bad. i see from that STOP message resource that the 0x7E can be associated with dodgy USB.
by way of tracking down that possibility, do you still get the BSOD if you connect to a different port? (or, if you've got a dock, connect directly to a port instead?)
(2) on general principles, we'd better check for malware. download fresh definitions and run vigorous virus and spyware scans. if your security software providers offer online scans, run those as well. (they can sometimes pick up an infection in cases where the security software on the PC has been compromised.)
(3) especially if you've recently installed any new hardware on your PC, head into Device Manager to check to see if there's any alert/warning messages showing up next to any of your devices. if you see any, what do they say?
(4) let's also let's also capture a minidump of the crash and send it to the Discussions Hosts, so they can throw it over the fence for the Apple engineers to analyze.
To set up your machine to capture a minidump, right click on "My Computer", select "Properties", select the "Advanced" tab, select the "Startup and Recovery" Settings button, select "small memory dump" from the popup. When it crashes, look for the MiniDump file. It's usually in the folder "C:\WINDOWS\Minidump" and is called something like Mini<number>-<number>.dmp.
And then send it to a Discussions Host. It doesn't hurt to put the URL to this discussion thread, so that whoever gets it has some context. Also give as much information about the context of the crash (in the email) as you can.
love, b

Lenovo thinkpad L412 blue screen when i move my laptop

i am using lenovo thinkpad L412 laptop
my screen gets blue screen when i move my laptop. if i dont move it it just works fine.
i tried to update my stytem for latest driver and software but still problem doesnt go away.
i also run the diagnostic test for hardware but it doesnt show any problem.

You can't have a blue screen in bios, blue screens are a "feature" of Windows OS.
What is the error code mentioned on the blue screen? This could give information about the nature of the problem.
You could also try to boot from a Linux Live cd distribution, such as Ubuntu for example (no need to install it, just boot from it). If the Live cd works well then most probably this is not a hardware problem but drivers related as somebody already suggested.
Please tell us the machine type of your laptop, the operating system used and any hardware changes you have made (added memory, changed hard disk etc). Give as much details as possible!
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
This will help the rest of the Community with similar issues identify the verified solution and benefit from it.

How to blank laptop screen when using external monitor/

Hi there
I need some help with figuring out how to configure my xorg.conf for my Arch Linux 64 bit installation on a HP Pavilion dv 5000 laptop so that I can automatically blank my laptop screen when using an external monitor. I have Arch Linux installed along with Ubuntu Feisty. In Ubuntu my external monitor (Viewsonic 1912WB) was not detected at the time of installation but with the native 1280X800 resolution that is good for the laptop takes effect for the external monitor automatically when the external monitor is plugged in. The laptop monitor goes blank when the external monitor is plugged in.
In my Arch Linux installation I have not been able to configure a dual head configuration using the ATI Radeon drivers (fglrx). I have the native 1280X800 resolution set up for the laptop monitor and this resolution takes effect for the external monitor also. However the laptop monitor also continues to function when the external monitor is plugged in. I would like to blank the laptop monitor when using the external monitor.
I am attaching my Arch Linux xorg.conf and the Ubuntu xorg.conf below. Thanks for anyone who can help, I am having a lot of difficulty in figuring out how to set up xorg.conf among all the things that I have had to learn so far in Linux and I am a relative newcomer to the whole thing. I have tried to compare the two xorg.conf files and edit my Arch xorg.conf in accordance with the Ubuntu one but it did not work and I keep getting errors!
I am using XFCE as my Desktop environment.
Arch Linux xorg.conf
# File generated by xorgconfig.
# Copyright 2004 The X.Org Foundation
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
# Refer to the xorg.conf(5) man page for details about the format of
# this file.
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# Files section. This allows default font and rgb paths to be set
# Server flags section.
# Input devices
# Core keyboard's InputDevice section
# Core Pointer's InputDevice section
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Monitor section
# Any number of monitor sections may be present
# Graphics device section
# Any number of graphics device sections may be present
# Standard VGA Device:
# Device configured by xorgconfig:
# Screen sections
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
# ServerLayout sections.
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
# Section "DRI"
# Mode 0666
# EndSection
Section "ServerLayout"
# The Identifier line must be present
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
Identifier "Simple Layout"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# RgbPath "/usr/share/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
# FontPath "/usr/share/fonts/TTF"
# FontPath "/usr/share/fonts/Type1"
# FontPath "/usr/lib/X11/fonts/local/"
# FontPath "/usr/lib/X11/fonts/misc/"
# FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/Speedo/"
# FontPath "/usr/lib/X11/fonts/Type1/"
# FontPath "/usr/lib/X11/fonts/TrueType/"
# FontPath "/usr/lib/X11/fonts/freefont/"
# FontPath "/usr/lib/X11/fonts/75dpi/"
# FontPath "/usr/lib/X11/fonts/100dpi/"
# The module search path. The default path is shown here.
# ModulePath "/usr/lib/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
EndSection
Section "Module"
# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
# Load "type1"
# This loads the GLX module
# Load "glx"
# This loads the DRI module
# Load "dri"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option    "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "freetype"
# Load "xtt"
EndSection
Section "InputDevice"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Identifier "Keyboard1"
Driver "kbd"
Option    "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
Option    "XkbRules" "xorg"
Option    "XkbModel" "pc104"
Option    "XkbLayout" "us"
EndSection
Section "InputDevice"
# Identifier and driver
# the following line.
# Option "Protocol" "Xqueue"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7. Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
Identifier "Mouse1"
Driver "mouse"
Option    "Protocol" "Auto" # Auto detect
Option    "Device" "/dev/input/mice"
# When using XQUEUE, comment out the above two lines, and uncomment
Option    "ZAxisMapping" "4 5 6 7"
# Emulate3Buttons is an option for 2-button mice
EndSection
Section "Monitor"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
Identifier "My Monitor"
HorizSync 30.0 - 62.0
VertRefresh 50.0 - 70.0
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option    "VendorName" "ATI Proprietary Driver"
Option    "ModelName" "Generic Autodetecting Monitor"
Option    "DPMS" "true"
EndSection
Section "Device"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
Identifier "Standard VGA"
Driver "vga"
VendorName "Unknown"
BoardName "Unknown"
EndSection
Section "Device"
#VideoRam 131072
# Insert Clocks lines here if appropriate
Identifier "* Generic VESA compatible"
Driver "vesa"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
EndSection
Section "Screen"
Identifier "Screen 1"
Device "* Generic VESA compatible"
Monitor "My Monitor"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1280x800" "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1280x800" "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x800" "800x600" "640x480"
EndSubSection
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Ubuntu xorg.conf
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
# Edit this file with caution, and see the xorg.conf(5) manual page.
# (Type "man xorg.conf" at the shell prompt.)
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg
Section "Files"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
# path to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection
Section "Module"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "vbe"
EndSection
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection
Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizScrollDelta" "0"
EndSection
Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection
Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection
Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection
Section "Device"
Identifier "ATI Technologies Inc ATI Radeon XPRESS 200M 5955 (PCIE)"
Driver "ati"
BusID "PCI:1:5:0"
EndSection
Section "Monitor"
Identifier "Generic Monitor"
Option "DPMS"
EndSection
Section "Screen"
Identifier "Default Screen"
Device "ATI Technologies Inc ATI Radeon XPRESS 200M 5955 (PCIE)"
Monitor "Generic Monitor"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1280x800"
EndSubSection
SubSection "Display"
Depth 4
Modes "1280x800"
EndSubSection
SubSection "Display"
Depth 8
Modes "1280x800"
EndSubSection
SubSection "Display"
Depth 15
Modes "1280x800"
EndSubSection
SubSection "Display"
Depth 16
Modes "1280x800"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x800"
EndSubSection
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "stylus" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "Synaptics Touchpad"
EndSection
Section "DRI"
Mode 0666
EndSection

Xrandr 1.2 provides means for this. But today the only supported configuration is xorg-server-1.3 + xf86-video-intel-2.0. So for Radeon you'll have to wait for drivers that support Randr 1.2.
On my laptop (Thinkpad x60s) that would be:
xrandr --output VGA --auto
xrandr --output LVDS --off

Blue screen when unplugging phone charger from USB

My HTC Droid incredible 2 causes windows 7 crash (blue screen) when I unplug charger cable from desktop USB port. It does not matter whether I have unplugged the phone from charger BEFORE unplugging the charger cable from the USB port. Has anyone else had this issue & resolved it?

On your lower right hand corner is an icon that is used to disconnect your usb devices safely.
simply click on it then select the device you want to remove, the computer will say "Device is safe to remove" then unplug the usb cable from the computer.
Additionally try another usb port on your computer and see if that corrects the problem.
Another thing to do is before you hook the phone up again do a system shut down and restart. Then plug in the phone. This may load your usb drivers correctly or the system will repair them.
Good Luck

Computer goes to blue screen when ipod plugged in.

I have tried all angles on this and still haven't been able to figure out. Can somebody please offer some new knowledge? I have tried some older suggestions awithout resolution. Here is what is happening using Windows 7/lastest updated itunes and ipod 80g classic:
My ipod was completely erased after trying to update through itunes as i normally do. Now when i plug ipod into the itunes, it will not be recognized in the left column and after about 3 minutes my entire computer will go to blue screen and reboot itself. I have tried restoring, checked diagnostics on ipod. I think I may need some more info on opening itunes in safe mode and beginning from there, however I'm open for any other suggestions/links. Thank You

First off, have you made sure your Windows OS is up to date with all the latest patches and updates? Have you also checked with your PC's manufacturer (such as Dell, Toshiba, etc) to make sure you have all the latest drivers, firmware and BIOS installed?
Does the PC ever blue screen when the iPod is NOT connected?
B-rock

Blue screen when powering off

I recently purcahsed a one year old Lenovo 3000, it had Windows XP installed and I upgraded this to Windows Vista with no problems. I then renamed the laptop and deleted the previous owners user files and that's when I had a problem. When I power down the laptop I get a Blue Screen saying something about a dump and saying it was doing something to protect my PC ? I found some kind of fault finding log and it mentioned something about the pc's name and also something about being unable to access a certain user file. I changed the computer name back to the original one and unerased the original user file but I still get the Blue Screen when powering down.
Is it possible to get a replacement software DVD that will get me back to square one please, thanks for any help. Dan McLean in Port Glasgow.

This really sounds like shoddy drivers combined with an IRQ conflict.
I suggest you post your IRQ's from System Info, for example:
IRQ 0   System timer   OK
IRQ 1   Standard 101/102-Key or Microsoft Natural PS/2 Keyboard   OK
IRQ 4   Communications Port (COM1)   OK
IRQ 5   WinFast TV2000 XP WDM Audio Capture   OK
IRQ 6   Standard floppy disk controller   OK
IRQ 8   System CMOS/real time clock   OK
IRQ 9   Microsoft ACPI-Compliant System   OK
IRQ 11   NVIDIA nForce PCI System Management   OK
IRQ 12   Logitech-compatible Mouse PS/2   OK
IRQ 13   Numeric data processor   OK
IRQ 14   Primary IDE Channel   OK
IRQ 15   Secondary IDE Channel   OK
IRQ 16   RADEON X800 XT Platinum Edition   OK
IRQ 17   WinFast TV2000 XP WDM Video Capture   OK
IRQ 18   Creative SB Live! series   OK
IRQ 20   NVIDIA Network Bus Enumerator   OK
IRQ 21   Standard OpenHCD USB Host Controller   OK
IRQ 22   Standard OpenHCD USB Host Controller   OK
IRQ 23   Standard Enhanced PCI to USB Host Controller   OK
Also, as you intend to DL and install the nVidia Drivers make sure you get the sound drivers from Realtek Downloads too.
What Drivers are you using for the AIW?
Take all the Driver CD's and make pretty Christmas tree ornaments out of them
~Edit~ I just looked at the stop error again and realized I misread, then I saw Supershanks post My initial suspicion is likely to be wrong, but it's worthe a look anyway.

Blue Screen when burning a DVD

When I try to burn a DVD the systems crash with a blue screen when "compiling media" is at 95%. Windows returns a post error "PX Engine has stopped working properly". I have followed all steps in both pages http://forums.adobe.com/thread/415318?tstart=30 and http://helpx.adobe.com/premiere-elements/kb/troubleshoot-system-errors-freezes-burning.htm l. The PX Engine is installed by Premiere and I also tried to install an update of PX Engine as instructed by Microsoft Help. Any help? I have a Windows 7 Home Premium 64bit SP1 on Dell XPS (Intel i7, 8 GB RAM, 250+ GB free hd space).

A BSOD is a very serious matter. It is most often caused by hardware, or low-leve drivers interfacing with the OS. This ARTICLE goes into much more detail. It also provides links to tools, that might be very helpful.
I would start looking for:
Heat (DVD burning, like Rendering and Export, is very intensive)
RAM (DVD burning might well be using RAM that sits unused by most other operations)
PSU (DVD burning requires more power, as the HDD's and multi-drive are all very active)
Good luck,
Hunt

Inksys wrt54g gives blue screen when connected to Vista OS

My linksys wireless router gives a blue screen when connected to it using Vista as the platform,Any ideas as to how to salvage this problem...
ASAP

Other than Linksys WRT54G did you tried to connect any other router to the computer?
Have you tried to you use this router on any other computer ?

IMac will only safe boot (blue screen when not safe booting).

A buddy asked me to help with his Intel based iMac. It was giving a blue screen when trying to boot up (and an odd cursor along with the blue screen). The cursor moves around the blue screen but looks like two cursors. One cursor is a normal arrow pointer, the second is a rectangle about .25 inch wide and 1 inch tall made up of about 10 horizontal lines.
I'm very familiar with Macs and OS X and was sure it was probably a messed up preference file (most likely login preference). It wasn't.
Here's the odd circumstances:
I have an intel macbook that if I use firewire target disk mode I can boot just fine off his iMac.
His computer will not boot off my Macbook that is in firewire target disk mode.
We cloned his hard drive to an external firewire hard drive (using Carbon Copy Cloner), my Macbook boots off it just fine, his iMac will not.
He's been wanting to go to Leopard so we upgraded his computer (did basic upgrade), but it still blue screened (with odd cursor).
Then we did an erase and install. Still no difference in behavior.
I would almost be convinced that it's a hardware failure, but it will safe boot every time.
Here's what happened when it died. His son was playing a Star Wars game (I'm not sure which one). The kid was in the middle of the game and paused it when it was time for dinner. When the kid went back to play, the computer was frozen. They tried everything to unfreeze it and ended up powering it down. Started the blue screen ever since.
He's going to contact Apple (it's barely still under it's warranty) but I was hoping someone here has another idea what it could be.

I found this topic while trying to find an answer to my problem. It seems we have a similar thing going on with our imacs (although mine is a much older crt imac). I'll copy and paste my original post from the imac board :
Hi
I received a free imac snow (G3 500mhz) from someone. He told me it was broke, and someone told him the logic board needed to be replaced.
I brought it home and tried to start it up. It gave the '?' folder icon. I started up from an OS 9.1 cd - Success! Except there was no HD. I opened it up and discovered that the HD wasn't connect to the ATA cable. I was able to start up to a previously installed Tiger. Except once it booted it would quickly freeze - the mouse pointer would turn into a scrambled beach ball (very strange) and wouldn't move.
I did some research and found about the potential problem with OS X and the imac's firmware. I restarted from the 9.1 CD and installed that OS. Everything seemed fine and was running ok (from my limited time on it). I then DL'd the latest firmware for the imac (4.1.9.) and tried to run it. Except the message came up that the latest firmware had already been installed. So i guess thats a good thing. I don't have to worry about firmware being a problem.
So i did a zero out wipe on the HD and installed tiger from the dvd. But on the first restart after installation (where i should go to the set up assistant) I get the scrambled beach ball and it freezes.
I thought perhaps the HD is faulty and ran disk utility on it - it came back as fine. I doubled checked to make sure it was set to 'master'. it sure was. I decided to swap out the HD anyways since i can't see what else could be the problem and put in a different 30gb IDE drive. I once again zeroed out the drive and did a fresh install of tiger. On restart i get the same scrambled beach ball and the freeze.
I guess i should describe the scrambled beach ball. It's seems like the beach ball icon, except the bits that make it up are out of order and glitched out.. perhaps a video problem?
Could this really be a logic board problem? It was working in OS 9.1 fine. It starts up from system CDs and DVDs fine. Wouldn't a logic board exhibit the same problems on those systems?
Anyone have any idea?
Update - starting in Safe mode (restart with shift held down) works, and i was able to update to the latest version of Tiger, but once i restart with the full system i get the same problem.
This seems to me that it ISN'T a logic board problem, but more of a system software problem. Now my question is how do i isolate and fix the problem in Tiger?
I guess i'll post this question in the Tiger forum, but if anyone has any ideas please let me know.
Thanks

H87M-P33 bios hangs (code 99) when both memory modules installed

Hello everyone!
MB: H87M-P33
CPU: Intel Core I5-4670
RAM: Corsair Vengeance LP 2x4GB kit 1600MHz 9-9-9-24 1.5V (CML8GX3M2A1600C9B)
PSU: Corsair CX500
Besides power button, nothing else is connected.
I'm building a brand new system. It boots with either module from the memory kit in either slot, but bios hangs (code 99) when BOTH memory modules are installed.
I tried to update bios to v2.1, but still won't boot with both modules installed.
Then I looked on the global site and found v2.2 bios for this board, which states "- Improved memory compatibility." and released on 2013-08-19, which is fairly recently. I tried to download it from download site (US, EU, CHN) but all sites give 404 error (file not found) to me.
Link to MB:
wwwDOTmsi.com/product/mb/H87M-P33.html#/?div=BIOS
Links for downloads I tried and give 404 to me:
download1.msi.com/files/downloads/bos_exe/7817v22.zip
download2.msi.com/files/downloads/bos_exe/7817v22.zip
download3.msi.com/files/downloads/bos_exe/7817v22.zip
I hope you guys can help me.

Quote from: klapaucius on 12-September-13, 15:10:43
It boots fine with a single stick in either slot. I tried flashing the attached beta bios via UEFI interface (choose the option with ME) and it updated. It still won't work if both slots are filled, works fine if either of dimm slots is filled with either stick from the kit.
ADD: I also tried putting whole RAM kit in my main machine and it works, so RAM isn't faulty.
Use a single RAM module, boot up, access the BIOS and be sure XMP is disabled.
Set the timings to 9-9-9-24, the voltage to 1.55-1.60V and the speed to 1333MHz.
Save the settings, shut down, insert the 2nd RAM module and see if it works.

Reader 9.0, 9.1, 9.1.2 blue screening when opening multiple PW protected files

I have a user, using MSOffice 2k3, who get a blue screen when opening multiple password protected files thru Outlook. The error suggests to update the BIOS, which has been done. This occurrs in all 3 versions of Reader 9. It specifically occurrs AFTER he inputs the password in the PW box. It does not matter which file he opens 1st. Any assistance would be appreciated.
mburdikoff

No, you are wrong (Gene & Mike). First, the forms, at least my forms, have NOT been edited since being created in designer. They were created and saved directly to flash. Second, this issue has been posted on the acrobat forum as well as the life cycle designer forum and both thread were ended with adobe expert posts saying it was an adobe reader issue and to post here.
I have experimented more with this issue and it seems to be a 'trusted identity' issue within reader, but I have not wholely figured it out yet. My forms work on Reader, 7, 8, and 9. They work on all versions of 7 and 8 regardless of what the form was optimized for (my forms were optimized for 9 and higher). The only trouble is on 9.0. I have found that when updating on client machines, reader gives a prompt (sometimes) that says reader has found a set of trusted identities from a previous version, would you like to use these identies or create a new set of identities. If you choose to keep the existing trusted identies set, the form works, even when upgraded to reader 9.0
Not trying to be argumentative (Mike and Gene) but the 'experts' bail on this issue by telling people it's a reader problem and to post here.

Blue screen when using 2 memory modules !!

Similar Messages

Maybe you are looking for