![]() |
STOP: 0X7B error!
I will try to keep this as short as possible. Windows XP on all.
Computer A is running along OK and has a need to re-boot. On the restart the blue screen of death pops up. STOP: 0x0000007B Restart is the same error. Computer A is used only to run a scanner. Important job must get scanned. Identical computer B is brought over to run scanner. Pull hard drive from A insert into B and everything boots fine, runs for days non stop. Insert perfectly running hard drive from computer B into Computer A and blue screen of death. Finish big scan job. Insert Drive B back into computer B and it works perfect. Take B out and re-insert A drive into B and it works. Both drives work in B. Neither drive works in A. Buy brew hard drive and install windows from scratch onto A. No problems except no software and files need to do job with A computer. Clone HD B to new drive. STOP: 0x0000007B and much cursing. Bottom line: Computer A will not get past STOP: 0x0000007B with either A or B drive, works just fine with new drive. Computer B works with all drives. WTF. How do I cure this? |
Google STOP: 0x0000007B error code. Lots of info.
|
Need to borrow a 12ga and some slugs. I can be there by 3:00 :D
|
|
Dave knows all about those MB failures...
|
I have run the full diagnostic of the entire computer system. After 4 hours the diag prog reported no errors. It was the diag program that came with the computer.
I have googled the error and so far nothing seems to apply. I will keep fighting and cussing. I am just looking for the magic answer from the brain trust. |
12ga and slugs....
|
That might make me feel better for a few seconds but it will not bring back the computer.
I am stubborn enough to want to figure out what the F**K is wrong. I already have a new 1 TB drive up and running. I could copy my data and start re-loading programs. I did not loose anything except time. It just does not make sense that one computer will boot just fine but the other is whacked. Curious minds want to know. |
We will have some tannerite next week...
|
Sounds like a hardware issue. Memory, MB, Power supply, or too much heat.
|
Quote:
It is like a mad wife hard drive and a husband computer. "I am NOT talking to you" and I still don't know what I did. :( |
Try the memory program I suggested...
|
Quote:
My vote is now swap the computers. |
Would start by pulling all of the memory out of the critter then running it. If all is well then one by one start introducing chips back in until you get the error again.
Hope its not a MB issue... |
Stop.....
hammertime! |
Quote:
|
Pull BOTH of them out and restart the computer. It will react slower but should still run.
Have seen memory that would test good but that was still causing problems. |
Quote:
|
Quote:
|
Corrupt driver?
|
All times are GMT -8. The time now is 04:36 AM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
Search Engine Optimization by vBSEO 3.6.0
Copyright 2025 Pelican Parts, LLC - Posts may be archived for display on the Pelican Parts Website