BSOD HELP! No idea what to do!

Okay new BSOD... got it randomly when talking to a friend error was win32k.sys, and here is a new report and all with a dump file.

Okay I know you need more than minidumps, but read these 2 there brand new and I just need you too read thema nd tell me what happend please thats all i need to know.

MvdB said:

Regretfully this again is only the dumpfile (2x), not the corresponding logs...

It is a 8E with a exception code c0000005. These are quite common and normally mean that any one of the following could be a problem:
Insufficient disk space, Device driver, Video card, BIOS, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory

The general way forward is:

you should use some basic troubleshooting techniques:

• Make sure you have enough disk space.
• Try changing video adapters.
• Check with your hardware vendor for any BIOS updates.
• Disable BIOS memory options such as caching or shadowing.

I need the logs to confirm.

What motherboard do you have? It is not in your specs...
Also, if you are SURE this all started with the newer driver you downloaded from nvidia, how about going back to a restore point from before that date?

caget1 said:

Okay new BSOD... got it randomly when talking to a friend error was win32k.sys, and here is a new report and all with a dump file.

Just a second set of eyes.

There are a few problems that could be causing this.


First


1-ASACPI.SYS

The pre 2009 version of this driver is a known BSOD cause. Yours is 2004

Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.SYS file is date stamped from 2009 or 2010 (NOT 2005).


Second

Your L1C62x86.sys L1c PCI-E Gigabit Ethernet Controller from Atheros Communications, Inc is close to 3 years old and needs updating.



Third and most important

the crash points to a memory exception (C00000005) and blames win2k.sys. This is usually caused by a dirver and in your case I am suspecting the AVAST.

I would remove and replace it with Microsoft security essentials and run these two tests

http://files.avast.com/files/eng/aswclear5.exe

Virus, Spyware & Malware Protection | Microsoft Security Essentials



1-Memtest.

*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.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

RAM - Test with Memtest86+



2-Driver verifier

I'd suggest that you first backup your data 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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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"
- 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).

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.

Driver Verifier - Enable and Disable

I dont mean to hate or anything, but you helded A LOT more than him.

zigzag3143 said:

caget1 said:

Okay new BSOD... got it randomly when talking to a friend error was win32k.sys, and here is a new report and all with a dump file.

Just a second set of eyes.

There are a few problems that could be causing this.


First


1-ASACPI.SYS

The pre 2009 version of this driver is a known BSOD cause. Yours is 2004

Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.SYS file is date stamped from 2009 or 2010 (NOT 2005).


Second

Your L1C62x86.sys L1c PCI-E Gigabit Ethernet Controller from Atheros Communications, Inc is close to 3 years old and needs updating.



Third and most important

the crash points to a memory exception (C00000005) and blames win2k.sys. This is usually caused by a dirver and in your case I am suspecting the AVAST.

I would remove and replace it with Microsoft security essentials and run these two tests

http://files.avast.com/files/eng/aswclear5.exe

Virus, Spyware & Malware Protection | Microsoft Security Essentials



1-Memtest.

*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.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

RAM - Test with Memtest86+



2-Driver verifier

I'd suggest that you first backup your data 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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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"
- 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).

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.

Driver Verifier - Enable and Disable

And that isnt my motherboard. :/ http://usa.asus.com/Motherboards/AMD...M_LE/#download <-- That is

zigzag3143 said:

caget1 said:

Okay new BSOD... got it randomly when talking to a friend error was win32k.sys, and here is a new report and all with a dump file.

Just a second set of eyes.

There are a few problems that could be causing this.


First


1-ASACPI.SYS

The pre 2009 version of this driver is a known BSOD cause. Yours is 2004

Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.SYS file is date stamped from 2009 or 2010 (NOT 2005).


Second

Your L1C62x86.sys L1c PCI-E Gigabit Ethernet Controller from Atheros Communications, Inc is close to 3 years old and needs updating.



Third and most important

the crash points to a memory exception (C00000005) and blames win2k.sys. This is usually caused by a dirver and in your case I am suspecting the AVAST.

I would remove and replace it with Microsoft security essentials and run these two tests

http://files.avast.com/files/eng/aswclear5.exe

Virus, Spyware & Malware Protection | Microsoft Security Essentials



1-Memtest.

*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.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

RAM - Test with Memtest86+



2-Driver verifier

I'd suggest that you first backup your data 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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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"
- 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).

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.

Driver Verifier - Enable and Disable

sorry for this again but avast is gone and I have that downloaded and installed timestamped for may 2009 and i cant find a new driver for my adapter, can you help me please?

zigzag3143 said:

caget1 said:

Okay new BSOD... got it randomly when talking to a friend error was win32k.sys, and here is a new report and all with a dump file.

Just a second set of eyes.

There are a few problems that could be causing this.


First


1-ASACPI.SYS

The pre 2009 version of this driver is a known BSOD cause. Yours is 2004

Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.SYS file is date stamped from 2009 or 2010 (NOT 2005).


Second

Your L1C62x86.sys L1c PCI-E Gigabit Ethernet Controller from Atheros Communications, Inc is close to 3 years old and needs updating.



Third and most important

the crash points to a memory exception (C00000005) and blames win2k.sys. This is usually caused by a dirver and in your case I am suspecting the AVAST.

I would remove and replace it with Microsoft security essentials and run these two tests

http://files.avast.com/files/eng/aswclear5.exe

Virus, Spyware & Malware Protection | Microsoft Security Essentials



1-Memtest.

*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.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

RAM - Test with Memtest86+



2-Driver verifier

I'd suggest that you first backup your data 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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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"
- 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).

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.

Driver Verifier - Enable and Disable

hey other set of eyes got 3 more BSOD minidumps, mind reading for me?

Hye i ran my pc with driver verifier and i couldnt even get to the loading windows lolgo wothout a BSOD here the minidumps.

zigzag3143 said:

caget1 said:

Okay new BSOD... got it randomly when talking to a friend error was win32k.sys, and here is a new report and all with a dump file.

Just a second set of eyes.

There are a few problems that could be causing this.


First


1-ASACPI.SYS

The pre 2009 version of this driver is a known BSOD cause. Yours is 2004

Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.SYS file is date stamped from 2009 or 2010 (NOT 2005).


Second

Your L1C62x86.sys L1c PCI-E Gigabit Ethernet Controller from Atheros Communications, Inc is close to 3 years old and needs updating.



Third and most important

the crash points to a memory exception (C00000005) and blames win2k.sys. This is usually caused by a dirver and in your case I am suspecting the AVAST.

I would remove and replace it with Microsoft security essentials and run these two tests

http://files.avast.com/files/eng/aswclear5.exe

Virus, Spyware & Malware Protection | Microsoft Security Essentials



1-Memtest.

*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.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

RAM - Test with Memtest86+



2-Driver verifier

I'd suggest that you first backup your data 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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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"
- 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).

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.

Driver Verifier - Enable and Disable