Bad CPU cause stop errors?

Does anyone know that a bad cpu cause stop errors in win2k ect.. or what would cause such errors? Bad memory?/

Hi,
It can be anything:
Bad CPU
Bad mounted CPU-cooler
Light powersupply
IDE cables wrong used
Harddisk broken
Mobo damaged
Metal standoff's left between the case and the board
Bad drivers
Broken videocard
Bad memory banks
Bad BIOS settings
There are probably a few more, but that's about what it can cause it.....
Start reading the trouble guide.... :D

Similar Messages

Plugging iPod in causes stop error

Ever since -I think- Sunday, whenever I try to plug my iPod in the USB portal, it causes some kind of stop error, showing a blue screen saying something caused a stop error. The code is 0x00000007, with some parameters behind it.
I don't understand, I recently installed Windows SP 3 via the Windows Updates, i don't know if that has anything to do with it...
Please help me, my battery is about to die and I really can't live without the iPod =( [lol]

I have the same problem on a Windows XP machine; I have not been able to solve it yet but here is one small piece of additional information: the 0x00000007 STOP error was happening before I installed SP3, and it still happens after SP3 was installed.

RAM problems with KT3 Ultra 2 causing STOP errors in XP

I've run the NEC ncramtst program on my PC and its coming up with an error in the extended memory at adddress 1B8EE01C which probably explains the stop errors and problems I've been having in XP...
I've tried reseating the RAM and tried a different slot but it still returns the same error.
The PC is only 2 months old and I have only experienced stop errors in the last 2 weeks or so and usually are at random - and occur more often when copying files - or putting load on the PC.. any ideas why the RAM is only now causing errors and what the problem is?
Are the problems definatly being caused by RAM or could it be the motherboard?
Thanks in advance
Ben
MSI KT3 Ultra 2
AMD AlthonXP 2400+
512Mb PC2700 DDR RAM (with errors)
80Gb Hard drive
Geforce Ti4400 Graphics card
Modem
LAN

OK I found a few minidumps in the event log
The computer has rebooted from a bugcheck. The bugcheck was: 0x10000050 (0xde1d3ee0, 0x00000000, 0x804eef61, 0x00000000)
Error code 10000050, parameter1 e262ca7a, parameter2 00000001, parameter3 8053cb3e, parameter4 00000001.
Error code 1000008e, parameter1 c0000005, parameter2 8053cbb1, parameter3 ee5b1a40, parameter4 00000000.
The computer has rebooted from a bugcheck. The bugcheck was: 0x10000050 (0xe1fe9a18, 0x00000000, 0x8053cbb1, 0x00000001). A dump was saved in: C:WINDOWSMinidumpMini030703-10.dmp.
Hope these help

After AMD X2 3800 upgrade MSI Radio causes stop error

Hi!
First of all sorry for by bad English
I have an MSI TV Anywhere master card for about two years now.
Until now it was running fine, using the updated drivers from MSI's site
This include the main driver, and the new WinDVR 3.0 and the updated MSI Radio
With these AMD vs Intel price wars, I've upgraded my Athlon Winchester 3000+ to a X2 3800+
The CPU is running fine
However, MSI radio immedialy gives a BSOD since I have changed the CPU
I have even got as far as reinstalling XP SP2 from scratch, and it still BSOD's :(
I get
STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER
How do I solve it?
Any other users having trouble with TV Anwhere Master with an AMD X2
CPU has run for several hours PRIME 95 and some heavy games with no crashes whatsoever
Just click on MSI radio and the mouse cursor wil freeze, followed by a BSOD and a reboot
Every time this happend
The only time when I could lauch MSI radio was when I booted Windows XP in safe mode
Thx in advance
Steven
System specs:
CPU AMD X2 3800 Socket 939
RAM 1Gb DDR400
Mobo Asus A8V Deluxe rev2 bios 1018, latest version
2x HDD WD Raptor 740 and Maxtor Diamondmax 10 250
AOpen A600A Case with 350W PSU by Fortron Source Power
PCI stuff:
SCSI Controller for scanner
TV Anywhere Master
Opti USB card
DVD, CDRW, and CDROM drive

Hi Stu!
Followed you advice, I looked a little more at the processor AMD procesor driver program
I already had installed the latest version, but it crashed too :(
However you suggestion had led my to try this:
* Removed the normal AMD processor driver
* Installed the AMD Fix for dual core processors from the AMD site
It worked!! Now MSI radio no more crashes!
knock on wood
I'll report back when there are errors
This is the page I got the utility from:
http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_13118,00.html
It's the first tool listed
From the desc:
"The AMD Dual-Core Optimizer can help improve some PC gaming video performance by compensating for those applications that bypass the Windows API for timing by directly using the RDTSC (Read Time Stamp Counter) instruction"
Hope this helps anyone who has an AMD X2 an has similar problems
Actually, with the new drivers from MSI I'm quite happy with my TV Anywhere Master
Greetings & thanks everyone
Steven

Skipped or bad frames causes "Unknown error" while trying to fuse or export as...

Hi. So, I'm trying to fuse footage from my Canon xf305 -to- an H.264 Youtube HD 29.97. I've successfully done this many times before, but this, one, particular clip has some problems. WithIn the roughly 10 minutes of this clip there are 4 small sections that the footage (video portion) seems to stall onto a still frame. This lasts literally for mabe 5 frames or so, and then the video continues. other than that the clip plays fine on the timeline, It's almost undetectable, but when I try and export out to any other format, Premiere gives me an "Unknown Error" about halfway through the export/fuse. What's Up With That?
I's there a way to "Force" Primiere to ignore those bad frames and export as best as possible?
Thanks in Advance for any answeres. Rich

First thing I'd recommend is deleting the Cache files. Go to Edit>Preferences>Media... and take note of their location on the hard drive. Then close down PP and use Windows Explorer or Finder to delete those files. When you reopen your project, PP will rebuild those files.
Second thing I recommend is adding your voice to the following feature request to make this process easier.
http://forums.adobe.com/thread/1369263?tstart=60

Error:arch: posix_spawnp: osascript: Bad CPU type in executable

Hi, i am new to these issues
I use to be able to excute my frank-cucmber on Lion and now when i move to mountain lion and I get the following error
error:arch: posix_spawnp: osascript: Bad CPU type in executable
i read on the interent that mountain lion is not supporting 32 bit
so how can i solve the problem so 32 bit will be supported?

You need a 64-bit version.
32-bit will never be supported on Mountain Lion.

Rollup 8 for Exchange 2010 SP2 causes EWS error with bad parameter for Exchange.MailboxReplicationService.ProxyService

When I installed Rollup 8 for Exchange 2010 SP2 it caused an error in EWS
EWS failed with the error:
exchange web service could not load file or assembly Exchange.MailboxReplicationService.ProxyService bad parameter
When I uninstalled the rollup all worked fine again.
Any ideas, Thanks in advance?

Hi,
To apply this update rollup, you must have Exchange Server 2010 SP2 installed. And remove all interim updates for Exchange Server 2010 SP2 before you apply this update rollup. Please check your installation deployment by the following article:
Install the Latest Update Rollup for Exchange 2010
http://technet.microsoft.com/en-us/library/ff637981.aspx
Description of Update Rollup 8 for Exchange Server 2010 Service Pack 2
http://support.microsoft.com/kb/2903903/en-us
If all requirements and preparations are configured properly, please collect your error logs to check your installation. It would be helpful to post some event logs here for further analysis.
Thanks,
Winnie Liang
TechNet Community Support

GeForce FX5600 128 - Causes BSOD and STOP Error

Hi everyone,
I recently upgraded my Fathers computer from Win ME to XP (SP1), and I now cannot run Microsoft Flight Simulator 2004. It ran perfectly under ME, and I haven't changed any hardware during the upgrade.
As soon as the game starts (plane on the runway) I get a blue screen and a 'STOP' error: *** STOP: 0x00000050 (0XC967C967, 0X00000000, 0X8053CDD1, 0x00000000)
By turning off all 3dfx functions in the game settings, or by turning off hardware acceleration in Windows we have managed to get into the game, but the graphics are poor and so slow its unplayable.
Apart from this, the system is working perfectly with no other problems when running normal windows apps. I have no other games to try the 3dfx functions on.
The hardware configuration is:
GeForce FX5600 128 graphics card
512 mb RAM
AMD Athlon 1.4Ghz processor.
The software configuration is:
Direct X 9b (same version as was being used to run the game under ME)
Nvidia drivers tried:
Nvidia VGA Driver 61.77 for Win XP/2000 (not WHQL)
Nvidia VGA Driver available through windows update (WHQL – though I can't remember the driver number)
Also tried an old driver 43.?? that came with the video card. The problem is always the same.
I have run dxdiag and initially it told me that the 61.77 drivers were not WHQL certified. After then running windows update it downloaded a driver which shows as WHQL certified (I do not know the version of this driver), I ran dxdiag again, and the system reported no problems. I successfully completed all direct draw and direct 3d tests under the dxdiag program, with no problems reported.
I have been in contact with Microsoft FS9 support initially, who later passed me to the operating system department as they had no luck in finding the fault. They tell me its a hardware issue and I should contact the manufacturer.
So far I have tried creating a (completely bare) parallel Windows XP installation and running the game in that, again the same problem occurs.
Does anyone have any suggestions on what I can do to resolve this problem? I have an opportunity this weekend to remove XP and go back to ME, which I am planning to do unless anyone has any thoughts on how I might fix this issue?
Many thanks in advance, John

Been running the Memtest86+ overnight on one stick and it came up with some 1690 errors...
Just stuck the other in now and leaving it run for a couple of hours... Not holding my breath though. Already sent my supplier an email to expect them in the post for a refund. Time to go down the old branded RAM route. Any suggestions for rock solid RAM that won't break the bank?
Thanks once again fellas,
Niels

Bad update push is causing system errors

Way to go Apple. Pushing out an update that is broken and now application is broken AND causing system errors (see all other comments). Get you act together and fix this ASAP. Just because we are Windows users, don't punish us.

Way to go Apple. Pushing out an update that is broken and now application is broken AND causing system errors (see all other comments). Get you act together and fix this ASAP. Just because we are Windows users, don't punish us.

MSI K9A Platinum and VIA drivers issue? XP 0x0000007B stop error.

I get a Windows Stop error when trying to boot into Windows XP with new components. The SATA hard drive (and Windows XP installation) is from the old computer.
The new computer components are:
MB: MSI K9A Platinum, chipset: RD580 (North Bridge), SB600 (South Bridge)
CPU: AMD Athlon 64 x2 5600+, boxed (the cooler and fan came with the CPU).
Video: MSI Radeon 1950 XTX
The old (and working) computer setup is:
OS: XP Professional
MB: Abit AV8-3rd Eye, chipset: VIA K8T800Pro + VT8237
CPU: AMD Athlon 64 3500+
Video: Sapphire Radeon 9800Pro All-in-Wonder, videodriver: atidvag.dll version 6.14.10.6542
HD: Maxtor 6B200M0 SCSI Disk Device
BIOS: Phoenix 6.00PG 20.04.2005
System drivers with "via" in the name: VIAAGP1.SYS, viaide.sys, viasride.sys
VIA 4in1 (Hyperion) version: 4.55 (that can be found at HKEY_Local_Machine\Software\Via4in1Driver).
VIA 2.20e SATA/RAID driver was used when installing this computer setup.
The precise stop error is:
0x0000007B (0xba4c3528, 0xc0000034, 0x00000000, 0x00000000)
From many sites I have gathered that the error is related to Windows XP not being able to access a critical system drive. Most probably the SATA hard drive issue.
The problem probably is the VIA drivers of the old motherboard and/or the SATA driver.
First I should mention, that MSI K9A Platinum does not have a hard disk SATA driver. If it does, I have been unable to find one. Certainly no such floppy disk included, and no such driver in the MSI's Web page for this motherboard.
Second important point: I never used RAID. I did use VIA 2.20e SATA/RAID driver disk when installing Windows XP to the old computer.
Strange that the hard drive model is reported as a "SCSI Disk Device". It's not a SCSI drive however: it's a SATA disk.
I have tried to uninstal the motherboard chipset drivers (Hyperion v4.55), but there seems to be a bug here: the drivers should be uninstalled using the installation program, and select the uninstall option. However, I do not get the uninstallation option to choose at all! Yes, I'm using the normal installation mode, not the quick installation (although tried that, too). The Hyperion setup program just installs, and asks to reboot the computer. After rebooting and trying again, it still does not offer me an uninstallation choise.
I know how to install hard drive VIA SATA driver, but I have no idea how to uninstall it. And I'm afraid to do that without certainty that it IS the solution, since I could not access the hard drive any more in the old computer setup (and return to read this forum). Also, I do not have a floppy drive any more. Anyone know if there is an issue with K9A and XP having VIA SATA driver installed?
When I tried the new computer setup, I first tried the simplest possible hardware combination: there were no CD/DVD-drives, no (parallel)IDE hard drives, and no PCI cards, except the MSI video adapter.
My BIOS Setup experiments. None of these helped: got the same stop error each time.
1) I didn't much touch the BIOS setting first. Just tried to boot with the settings BIOS came with.
2) Next I disabled the integrated audio, LAN and IEE1394 devices and floppy drive and disabled all other choises except the SATA drive as a boot device.
3) Next I tried with the fail-safe BIOS defaults.
4) Cleared CMOS.
5) Changed OnChip SATA type from Native IDE to Legacy IDE. (Only one boot attempt with the setting as Legacy.)
6) Disabled PCI IDE BusMaster.
7) Never touched anything in the Cell Menu: so the settings are in minimum.
A step I have taken after the last attempt: run Windows XP hard drive error-checking tool to every logical drive with the fix option selected, and the system drive also with scan the bad sectors option selected.
My plans next are:
1) to install a newer Hyperion driver. If that would correct the no-unistallation-choice-bug,
2) to disable USB-devices in the BIOS (desperate),
3) to choose the Windows general video display driver (although I seriously doubt this is a display driver problem!).
4) to uninstall the Anti-Virus software (Avira Antivir).
I've read a numerous Web pages so far about the 0x0000007B stop error. Here are some links:
Quote
http://www.seagate.com/www/en-us/support/knowledge_base/
Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE
This Stop message, also known as Stop 0x7B, indicates that Windows XP Professional lost access to the system volume or boot volume during the startup process. This error always occurs while the system is starting and is often caused by one of the following:
* Hardware problems
* Corrupted or incompatible storage drivers
* File system problems
* Boot sector viruses
* Outdated firmware
During I/O system initialization, this error can occur when:
* The controller or driver for the startup device (typically the hard disk) failed to initialize the necessary hardware.
* File system initialization failed because the system did not recognize the data on the boot device.
Quote
http://support.microsoft.com/kb/314082
You receive a Stop 0x0000007B error after you move the Windows XP system disk to another computer
SYMPTOMS
After you move the Microsoft Windows XP system (boot) disk to a backup computer, you may receive the following Stop error when you try to start the Windows XP-based backup computer:
STOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000)
CAUSE
This error may occur if the registry entries and the drivers for the mass storage controller hardware in the backup computer are not installed in Windows XP.
RESOLUTION
To resolve this error, use the same hardware for the backup computer.
Heh, heh! Very nice Microsoft, but I plan to update my computer, so I NEED to use different components
Quote
http://support.microsoft.com/kb/324103
Device Driver Issues
You may receive a "Stop 0x0000007B" error message in the following scenarios:
•   A device driver that the computer boot controller needs is not configured to start during the startup process.
•   A device driver that the computer boot controller needs is corrupted.
•   Information in the Windows XP registry (information related to how the device drivers load during startup) is corrupted.
Hardware Issues
You may receive a "Stop 0x0000007B" error message if there is a resource conflict between the boot controller and another controller or between SCSI devices. You may also receive this Stop error message if drive translation is not being performed or if drive translation was changed. To troubleshoot this issue:
1.   If an IRQ or I/O port address conflict exists between the boot controller and another controller, Windows XP either stops responding (hangs) or displays a "Stop 0x0000007B" error message. If you recently added new hardware, remove the new hardware or reconfigure it so that it does not conflict with the resources of any other installed controllers.
2.   If you are using a SCSI hard disk, check the SCSI chain for correct termination. Remove any unused SCSI devices or make sure that each SCSI ID is unique.
3.   Make sure that drive translation is turned on (if it is required) and that it has not been changed. For example, if you recently switched controllers, this issue may occur. For additional information about this issue, click the following article number to view the article in the Microsoft Knowledge Base: 314082.
Quote
http://support.microsoft.com/kb/316401/
SYMPTOMS
When you start your Microsoft Windows XP-based computer after you replace the motherboard on the computer, you may receive a Stop error message that is similar to the following:
STOP 0x0000007B INACCESSABLE_BOOT_DEVICE
CAUSE
This issue may occur if the new motherboard contains an embedded IDE controller that has a different chipset than the original motherboard.
RESOLUTION
Method 1: Perform an in-place upgrade of Windows XP [<- That means repair installation of Windows XP]
•   Do not use a repair or in-place upgrade if you suspect disk problems.
Method 2: Repartition and format your hard disk and reinstall Windows XP

Alright I got the situation over.
Quote from: Roskaposti on 19-May-07, 04:44:59
My plans next are:
1) to install a newer Hyperion driver. If that would correct the no-unistallation-choice-bug,
2) to disable USB-devices in the BIOS (desperate),
3) to choose the Windows general video display driver (although I seriously doubt this is a display driver problem!).
4) to uninstall the Anti-Virus software (Avira Antivir).
I did try all all the above, and none of them helped.
And by the way: after installing the new Hyperion (VIA chipset drivers), I was finally able to also uninstall. It also uninstalled the IDE SATA (I think) and PATA drivers.
But what I had to do, was to make a REPAIR installation of Windows XP.
So, I was wondering now afterwards: this is really, really silly. Why the hell we need to re-install Windows if we move the SYSTEM SATA drive to another computer? We don't have similar problem with parallel IDE drives. Whom should we thank here??
The issue is to insert the driver files and the information of the ide drivers Windows should use with the next boot. How can it be this difficult?
What you basically need is..
- the information about the new chipset's PCIIDE.SYS/[VENDOR_PROVIDED_FILE].SYS and ATAPIIDE.SYS inserted into the values in HKEY_LOCAL_MACHINE\SYSTEM\ControlSetXXX\Control\CriticalDeviceDatabase
- and the vendor's IDE drivers to the %SYSTEMROOT%/System32/drivers folder.
Maybe something else, I don't know. But the problem was, Windows didn't know how, or what drivers to use. That can't be so big problem you need to install the whole OS anew!

K8T NEO FSR bad bios or bad CPU?

Hi - I just got a K8T NEO-FSR with an Athlon 64 3000 (newcastle) and 512 Meg of Corsair value select memory. I installed everything fine and tried to install a fresh copy of windows xp home but I kept getting a blue screen of death and a registry error (from the CD!!).
I then reformatted my drive and put a copy of windows 2000 pro on it. After updating the drivers, everything seemed to be OK. But - I was getting a few random problems (CD stopped working, freeze, etc). I was going to try to install XP but I thought I should probably upgrade the BIOS first just to make sure that wasn't the problem.
Well - I followed the instructions for updating the BIOS (I've done it before for other systems) and everything seemed to go smoothly until I tried to reboot. Nothing - it powers up but doesn't do anything. I assumed that something must be wrong with the BIOS. I double checked which file I was using A6702VMS.180.
I then tried a BIOS recovery. I reformatted a floppy on a windows XP machine and put a copy of the BIOS that I had backed up before the flash onto the disk named AMIBIOS.ROM. Then I unplugged the power supply and every piece of hardware except the CPU, reset the CMOS, and let it sit for 15 minutes. Then I reconnected the floppy and plugged in a PS2 keyboard into the back. Pushed down CTRL and HOME and turned the power on. Nothing. Tried it again with each CTRL key and with the regular HOME key and the keypad. Nothing.
The LED's on the back panel show all 4 red which the manual says is a bad CPU. Could my CPU have died somehow? Did I miss something obvious?
My power supply is an Enermax 350W with 32A on 3.3V, 32A on 5V, and 17A on 12V.
Any thoughts? I'm a little annoyed that I can't find a definitive source for how many amps on each of the rails the main board and CPU need. I've found widely varying advice on all of the boards I've read.
Thanks,
Ted

Quote
1) The PSU that you have is quite weak on the +12v Rail & could be the cause of your problems, most people on here recommend 20a on the +12v Rail.
I've seen people on various boards throw numbers anywhere from 15A to 30A for the 12V rail. However, I haven't seen anyone quote any hard sources. My back of the envelope computations:
CPU: 89 W (max power from AMD's web site)
MEM: uses 3.3V
Floppy: uses 5V
CD: 20W
RAM: uses 3.3V
HD: 15W
Geforce2 GTS graphics card: 8W
which gives me about 132W on the 12V rail at maximum power usage (which - since I haven't done anything I doubt I've hit). This would be about 11 amps which is easily covered by my power supply. And - the 89W number form AMD is for all the Athlon64 chips of which the 3000 is the very low end so it's probably less than that.
Quote
2) You may have faulty RAM & i would recommend running a memory testing program just to check that is ok.
Could the RAM be faulty even though I had a windows 2000 setup running reasonably well? The BIOS did do a memory check on each startup (I turned that on when I first installed the board).
Quote
As for the system not booting now, sounds like you have a bad BIOS flash & that you will need to get the BIOS reflashed or RMA your motherboard.
I don't think this board supports reflashing - the chip is soldered onto the board. Any idea why the rescue procedure isn't working?

"Bad CPU Type In Executable"

After upgrading from an eMac to an Intel Mac Mini, I noticed that I needed to reinstall Xcode. Once I reinstalled Xcode (v2.4), I made some changes to one of my applications. After testing it fully on my new Mac, I copied the .app file to my old eMac and attempted to re-run. In doing so, I received the following error message:
"You cannot open the application 'NAME OF APPLICATION' because it may be damaged or incomplete."
So, in Terminal, I navigated through the Package Contents to the actual executable and tried to run it. I, then, received the following error:
"Bad CPU type in executable."
How do I correct this error, so it will run on both of my Macs??
THANKS IN ADVANCE!!
WBELL
eMac Specs:
1GHz, 768MB DDR, OSX 10.4.x
Mini Specs:
1.5GHz Core Solo, 1024MB DDR2, OSX 10.4.x
Mac Mini Mac OS X (10.4.7) 1.5GHz Core Solo

Here are a couple of things to check...
First, from your screen shot it appears that the main.m file is from an older AS Studio application (ie is this a project that was originally created some time ago... perhaps under Project Builder?). The main.m file that gets included with relatively new AS Stdio apps looks like this:
<pre>
extern void ASKInitialize();
extern int NSApplicationMain(int argc, const char *argv[]);
int main(int argc, const char *argv[])
ASKInitialize();
return NSApplicationMain(argc, argv);
</pre>
So you may want to copy/paste the main.m code from a newly created AS Studio app into your (older?) existing project. I'm not sure the above problem would cause the failure to build a Universal app, but changing code in main.m may get rid of the warnings you're seeing.
But also, the screenshot made me wonder if your target(s) needs to be converted to the newer "native" target format (this is different from the "conversion" that Xcode does to an older project file). With your project open click on Xcode's "Project" menu... is the option "Upgrade 'YourTargetName' to Native Target" or "Upgrade all Targets in Project to Native" available? If so, I think you must convert to native targets in order to build universal binaries.
Hope this helps,
Steve

Windows 7 64bit STOP Error Code 0x000000F4

Hello, I got a BSOD when my computer was almost idle (only utorrent was running) with stop error code 0x000000F4.
Also at the blue screen it got stuck at the 2nd step (don't remember what it says) and as a result I don't have a minidump file.
My pc specs are:
Motherboard: ASUS Rampage III Extreme
CPU: Intel i7 - 950 @ 3,00GHz
RAM: 3x2GB @ 1866MHz
Windows Drive: 60GB SSD (OCZ Agility)
OS: Windows 7 Ultimate Sp1 64bit
This has happened quite a few times during the 1 year I have this computer. The previous times the SSD I had (Corsair F60) stopped working. (2 SSDs dead)
The problem is that I cannot reproduce the problem so that we find out the cause. Is it something with the controller of the motherboard? What should I do?
Thank you for your time!

* Bugcheck Analysis *
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800a74ab30, Terminating object
Arg3: fffffa800a74ae10, Process image file name
Arg4: fffff8000339f8b0, Explanatory message (ascii)
Debugging Details:
PROCESS_OBJECT: fffffa800a74ab30
IMAGE_NAME: csrss.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: csrss
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: csrss.exe
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR: 0xF4_C0000005
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`0c7d60e8 fffff800`034265e2 : 00000000`000000f4 00000000`00000003 fffffa80`0a74ab30 fffffa80`0a74ae10 : nt!KeBugCheckEx
fffff880`0c7d60f0 fffff800`033d399b : ffffffff`ffffffff fffffa80`0be7ab60 fffffa80`0a74ab30 fffffa80`0a74ab30 : nt!PspCatchCriticalBreak+0x92
fffff880`0c7d6130 fffff800`03353448 : ffffffff`ffffffff 00000000`00000001 fffffa80`0a74ab30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`0c7d6180 fffff800`0309aed3 : fffffa80`0a74ab30 fffff800`c0000005 fffffa80`0be7ab60 00000000`04040a40 : nt!NtTerminateProcess+0xf4
fffff880`0c7d6200 fffff800`03097470 : fffff800`030e767f fffff880`0c7d6b78 fffff880`0c7d68d0 fffff880`0c7d6c20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0c7d6398 fffff800`030e767f : fffff880`0c7d6b78 fffff880`0c7d68d0 fffff880`0c7d6c20 00000000`04041600 : nt!KiServiceLinkage
fffff880`0c7d63a0 fffff800`0309b2c2 : fffff880`0c7d6b78 00000000`778d8f36 fffff880`0c7d6c20 00000000`040410d8 : nt! ?? ::FNODOBFM::`string'+0x49874
fffff880`0c7d6a40 fffff800`03099e3a : 00000000`00000001 00000000`04040ff8 00000000`00000001 00000000`778d8f36 : nt!KiExceptionDispatch+0xc2
fffff880`0c7d6c20 00000000`778e9a9d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`04041000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778e9a9d
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0xF4_C0000005_IMAGE_csrss.exe
BUCKET_ID: X64_0xF4_C0000005_IMAGE_csrss.exe
Followup: MachineOwner
Bug Check Code 0xF4: http://msdn.microsoft.com/en-us/library/ff560372(VS.85).aspx
The BSOD occured when csrss.exe was running. Have
a look to that: http://www.ehow.com/how_2104293_solve-csrssexe-problem.html
Please disable all security softwares you are using and check again.
If this does not help, zip memory dump MEMORY.DMP under c:\windows\ and upload it.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft Student
Partner 2010 / 2011
Microsoft Certified
Professional
Microsoft Certified
Systems Administrator: Security
Microsoft Certified
Systems Engineer: Security
Microsoft Certified
Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified
Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft Certified
Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows 7, Configuring
Microsoft
Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
Microsoft Certified
IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Trainer

Geforce 6800 Stop Errors

After a month of tracking a random reboot problem, I have finally managed to get a stop error blue screen. To my delight it has pointed out the very cause of my problem. NV4_disp.dll. Now, my drivers for my MSI geforce NX6800 are the 61.77 version. Whats the solution to this problem?

Overheating not an issue, stays very cool
Drivers I have tried muktiply for both mobo and video card to no avail
Reformatted 3 times now, the agony of doing that was horrible
Underpowered, unlikely, as I said, also upped the volts on the agp slot to 1.6
Sharing IRQs i'm not familar with, symptoms, solutions?
Hardware incompatibilty, this one I have explored a lot, I have swapped my ram. I have become increasingly suspicous that etheir my motherboard or cpu is shot
Motherboard looks perfect, only month old, contacts clean, no residue, no oils
VGA i have become increasingly curouis if it is the source of my problem, although the installation went well, the fact that one of the errors pointed out NV4_Disp.DLL makes me think that my drivers are corrupt.
My last blue screen, however pointed to win32.sys
Event Type:   Error
Event Source:   System Error
Event Category:   (102)
Event ID:   1003
Date:      10/4/2004
Time:      7:46:02 PM
User:      N/A
Computer:   MASTER
Description:
Error code 1000008e, parameter1 c0000005, parameter2 bf804892, parameter3 f78ce714, parameter4 00000000.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 62 66 38 30 34 38 39 32 bf804892
0040: 2c 20 66 37 38 63 65 37 , f78ce7
0048: 31 34 2c 20 30 30 30 30 14, 0000
0050: 30 30 30 30 0000

Stop errors

Hi, I have an AMD64 board, the K8T Neo-FIS2R, with 1 gig RAM, Radeon 9800 Pro, Santa Cruz sound card, and Athlon64 3200+ processor. Now, I ran it fine for a while, but suddenly, I get stop errors repeatedly, stop errors 0x00000077 and 0x0000007A. I get them a lot when I play games, but only Unreal based games (UT2k4, Postal 2, and such). For example, I played a long time on Half Life, no problem, but playing Postal creates several hitches, then a crash. Quickly. I checked forums for UT2k4 and Postal 2, and got no answers... What could be causing this? The temperature runs at about 52-54C at the most, which it has with ease before, so that can't be it.

Well, I ran a windows Mem disgnostic boot disk, and the first time it crashed... second it was ok. So I booted back up... still bad. Angry, I cracked the computer and yanked out the mem to look at it closely. Well... long story short, there was dust. On the connector. Not sure if it was there initially or if my pulling it out got the ram dirty, but I cleaned it and put it back in, and no problems anymore. Who knew.
Maybe it's a bad cause-effect relationship (i.e. something else changed and I didn't see it), but hey, it's working now, so lesson learned. Clean the PC now and then.

Bad CPU cause stop errors?

Similar Messages

Maybe you are looking for