Shipped computer overseas, now have BSOD everytime is shutdown/restart

[saucey]

I brought my PC desktop on the plane as checked luggage.
When I turned it on after arriving home, it would power up, but no bios and no beep
after a lot of cable wiggling etc. i started to trouble shoot it by taking pieces out and putting them back in.
after stripping it to just the ram, i got the beep and bios back.
slowly added piece by piece and it gradually worked.

Problem now is everytime I shut down or reboot I get bsod.

Here is the error:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 50
BCP1: 8ACD3B98
BCP2: 00000000
BCP3: 86A26D82
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\080810-41293-01.dmp
C:\Users\DrSostagon\AppData\Local\Temp\WER-80590-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


My system is
System Manufacturer/Model Number Homebuilt OS windows 7 Ultimate 32 bit (installed within last 4 months) CPU Intel (R) Pentium (R) D CPU 3.00 GHZ Motherboard Asus P5KPL-AM EPU Memory 2G Graphics Card(s) NVIDIA GeForce 9800GT Sound Card internal Monitor(s) Displays LG w2353v Screen Resolution N/A Hard Drives 1TB
1 80G on another note, perhaps related is in device manager/

i have an error alert/message beside "Asusotherdevices - EIO Driver

 

[ttran]

Hi and welcome to SF!

How many DMp file do you have? Are you using any programs such as CCleaner, they might clean out your minidump folder. Please upload more next time if you can, simply just follow this procedure:

Go to C:\Windows\Minidump and copy all of the dmp files to the desktop. Select all>right-click on one>Send to>New Compressed folder. Then attach the zip file to your next post by use of the paperclip icon in the advanced editor.

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

For now, please update these drivers:

ISODrive ISODrive.sys Fri Apr 13 16:42:14 2007 (461F5076)
ISO CD-ROM Device Driver - ISODrive 
asusgsb  asusgsb.sys  Thu Sep 27 20:14:15 2007 (46FBACA7
ASUS Virtual Video Capture Device Driver [URL="http://support.asus.com/download/download.aspx"]ASUSTeK Computer Inc.-Support-[/URL]
AsIO     AsIO.sys     Mon Dec 17 16:10:20 2007 (47663CFC)
  Asus PCProbe Utility [URL="http://support.asus.com/download/download.aspx"]ASUSTeK Computer Inc.-Support-[/URL]

Also, please perform a cleanboot:
How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

BugCheck 50, {8acd3b98, 0, 86a26d82, 0}

Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+dc )

Followup: MachineOwner
---------
PROCESS_NAME:  System

Regard,

Tuan

 

[saucey]

Hi and welcome to SF!

How many DMp file do you have? Are you using any programs such as CCleaner, they might clean out your minidump folder. Please upload more next time if you can, simply just follow this procedure:

Go to C:\Windows\Minidump and copy all of the dmp files to the desktop. Select all>right-click on one>Send to>New Compressed folder. Then attach the zip file to your next post by use of the paperclip icon in the advanced editor.

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

For now, please update these drivers:

ISODrive ISODrive.sys Fri Apr 13 16:42:14 2007 (461F5076)
ISO CD-ROM Device Driver - ISODrive 
asusgsb  asusgsb.sys  Thu Sep 27 20:14:15 2007 (46FBACA7
ASUS Virtual Video Capture Device Driver [URL="http://support.asus.com/download/download.aspx"]ASUSTeK Computer Inc.-Support-[/URL]
AsIO     AsIO.sys     Mon Dec 17 16:10:20 2007 (47663CFC)
  Asus PCProbe Utility [URL="http://support.asus.com/download/download.aspx"]ASUSTeK Computer Inc.-Support-[/URL]

Also, please perform a cleanboot:
How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

BugCheck 50, {8acd3b98, 0, 86a26d82, 0}

Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+dc )

Followup: MachineOwner
---------
PROCESS_NAME:  System

Regard,

Tuan

Thanks for the help Tuan, I will try a clean boot after i send you this message containing the minidump.zip.

I do use CC cleaner, and used it trying to fix this problem, was that a bad idea?

Could you please tell me where I can find those drivers? I tried googling all of them, but it seems like many bunk websites trying to sell some sort of all-in-one driver repair software.

Do you think my OS Harddrive got jostled in moving and has a bad bit in it? How about trying to restore to a point before I moved the computer?

Just to be clear...I am only looking for these 3 drivers? ISODrive.sys

asusgsb.sys and AsIO.sys

 

[ttran]

What third party antivirus or firewall are you using? For those Asus driver I listed above, they come with different tool from Asus, in the mean time if you don't use any of them, you can uninstall them.
In looking through your drivers, I see that you have AVG anti virus installed. AVG is known to cause BSOD, on some systems. I suggest that you uninstall it while trouble shooting using the uninstall tool > Info > Tool (32bit) - Tool (64 bit). If you have AVG Identity Protection installed, uninstall it also >Info > Tool[FONT=&quot]. I recommend that you install MSE and make sure Windows Firewall is turned on.

[/FONT] The results from the DMP files do not give a definitive answer. While we investigate further here are a few things that you can do.

1-Run a system file check to verify and repair you system files. You do this by typing cmd in search, then right click and run as admin. SFC /SCANNOW

2-Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

3-Event viewer
Go into event viewer (type eventvwr in search). Go to the windows log>application tab.

You want to look for critical errors (they have red in the left column ).

When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.

When you find them please note the event ID, and the source codes and tell us what they are.

4-Device manager
Please go to start>search>type device manager.
Are there any "unknown devices" with yellow triangles on them?
Is you driver there , listed, and working?

If your driver is missing, or there is a yellow triangle on it, you will need to update it.

5-Driver verifier
please run Verifier with these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[ickymay]

after a physical move I would suspect a shifted motherboard and or gfx card also ram ?

did you move the CPU ?

 

[saucey]

Thanks so much for your help in advance.

I didnt touch the cpu, but seeing the way the airlines handled the package, im assuming the computer took some heavy hits. It was wrapped in 3 inch foam and in a hard plastic case. But it still took some heavy hits. It worked flawlessly before I put it on the plane and immediatly failed upon the first hook up after. So I am sure that it took some sort of damage. Probably hardware damage. Ill try the above suggestions and keep you posted.