Solved Unexpected shutdown, blue screen, HELP!

[Bookishbirdy]

[FONT=Segoe UI, Arial]On Sun 6/5/2011 3:42:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini060411-09.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]hal.dll[/FONT] (hal+0x3E79)
Bugcheck code: 0xA (0x34, 0x2, 0x1, 0xFFFFFFFF823A4E79)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\hal.dll
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


_____________________________________________________________________________________________[/FONT]
[FONT=Segoe UI, Arial]
[/FONT]Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: 00000034
BCP2: 00000002
BCP3: 00000001
BCP4: 823A4E79
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini060511-05.dmp
C:\Users\Owner\AppData\Local\Temp\WER-98046-0.sysdata.xml
C:\Users\Owner\AppData\Local\Temp\WERBD26.tmp.version.txt
[FONT=Segoe UI, Arial]_____________________________________________________________________________________________

[/FONT]Home Premium 32-bit - Changed out hard-drive in 2009 - Full retail version - Bought computer in 2007, but new hard-drive in 2009. - Age of OS system is 2 years.
[FONT=Segoe UI, Arial]
How do I fix this?! It keeps crashing when I'm not in safe mode.
[/FONT]

 

[americancritic]

Hello and welcome to the forum

Please follow the instruction here.

http://www.vistax64.com/crashes-debugging/282419-blue-screen-death-bsod-posting-instructions.html

Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL
The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A. This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
Cause

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.

The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

This is why we need your BSOD report as you have different stop codes.

 

[Bookishbirdy]

Alright, did that.

 

[Bookishbirdy]

Hello and welcome to the forum

Please follow the instruction here.

http://www.vistax64.com/crashes-debugging/282419-blue-screen-death-bsod-posting-instructions.html

Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL
The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A. This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
Cause

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.

The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

This is why we need your BSOD report as you have different stop codes.

Ok, I attached the files.

 

[americancritic]

We are just now going threw your BSOD file and will let you know something real soon...

Upon opening your report you have 51 Bosd files to go threw.

 

[americancritic]

Hello

Most of your BSOD is coming back to bugcheck A...

0xA - Probable Cause "win32k.sys" - Most common causes can be bad device drivers but also can be caused by Incompatible Hardware and Software.

What is the name of your anit-virus...

Have you added any new hardware of software lately...

 

[americancritic]

Hello I need to find out the following.

1. Manufacture Name of your system
2. Model Number...
3. Laptop or desktop...
4. The Name of your Anti-Virus...

 

[roy69]

It may also be an idea to update your windows software if you can, you have no service packs installed.

 

[americancritic]

Thank you Roy69 I was just about to tell the op that he has none and should update to sp2...

 

[americancritic]

Hello

I am close to giving you an answer for your BSOD's, so far this is what I have found out.

51 memorys dumps in 10 days...
3 different BSOD codes...

Stop code error 0xA total = 41
Stop code error E4 total = 8
Stop Code error 1000007E total = 2

ntkrpamp.exe shows up in all of the 0xA errors this is a process associated with Microsoft windows operating system from Microsoft corporation. ntkrpamp.exe is a system process that is needed for your windows system to work properly.

I believe this is due to a driver, it will take me a little longer to track it down and then will give you what you need to correct this problem...

Thank you for your patience...

 

[richc46]

Welcome
Based upon the analysis of AmericanCritic, I have a few suggestions. I think that if you follow the advice I hope that we will be able to prevent the BSODs in the future.

The reports that you have submittedreveal clues to the cause of your problem. They do not give a definitive answer. The more reports that we receivethe more clues are made available improving our chances of finding a solutionto your problem. Each remedy suggested must be performed regardless ofplacement in this report or other variables. You may have to experience severalmore BSODs until the final answer is discovered.

SFC /scannow
System Files - SFC Command

Scan with your Anti Virus

Update to SP2

Driver Verifier Inst (This step must be completed). The apparent cause of your BSOD was a driver

Since the driver that crashed you has not been listed you shouldrun driver verifier
Please run Verifier with these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'lltell you what the driver is. But sometimes it'll crash and won't tell you thedriver. Other times it'll crash before you can log in to Windows. If you can'tget to Safe Mode, then you'll have to resort to offline editing of the registryto disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've gotaccess to another computer so you can contact us if problems arise. Then make aSystem Restore point (so you can restore the system using the Vista/Windows 7Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and pressEnter
- 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 limitedexperimentation 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 useyour system normally, and if you know what causes the crash, do thatrepeatedly. The objective here is to get the system to crash because DriverVerifier is stressing the drivers out. If it doesn't crash for you, then let itrun 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 goingback 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 yourinstallation DVD to set the system back to the previous restore point that youcreated.




Enable the driver verifier

www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html

 

[Bookishbirdy]

Hello

I am close to giving you an answer for your BSOD's, so far this is what I have found out.

51 memorys dumps in 10 days...
3 different BSOD codes...

Stop code error 0xA total = 41
Stop code error E4 total = 8
Stop Code error 1000007E total = 2

ntkrpamp.exe shows up in all of the 0xA errors this is a process associated with Microsoft windows operating system from Microsoft corporation. ntkrpamp.exe is a system process that is needed for your windows system to work properly.

I believe this is due to a driver, it will take me a little longer to track it down and then will give you what you need to correct this problem...

Thank you for your patience...

Thanks for all your help, the last time I installed a service pack, I had to change my harddrive because it got a hung file or whatever, so I've been weary of installing any since then. I have AVG and also Malwarebytes.

 

[Bookishbirdy]

Welcome
Based upon the analysis of AmericanCritic, I have a few suggestions. I think that if you follow the advice I hope that we will be able to prevent the BSODs in the future.

The reports that you have submittedreveal clues to the cause of your problem. They do not give a definitive answer. The more reports that we receivethe more clues are made available improving our chances of finding a solutionto your problem. Each remedy suggested must be performed regardless ofplacement in this report or other variables. You may have to experience severalmore BSODs until the final answer is discovered.

SFC /scannow
System Files - SFC Command

Scan with your Anti Virus

Update to SP2

Driver Verifier Inst (This step must be completed). The apparent cause of your BSOD was a driver

Since the driver that crashed you has not been listed you shouldrun driver verifier
Please run Verifier with these settings:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'lltell you what the driver is. But sometimes it'll crash and won't tell you thedriver. Other times it'll crash before you can log in to Windows. If you can'tget to Safe Mode, then you'll have to resort to offline editing of the registryto disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've gotaccess to another computer so you can contact us if problems arise. Then make aSystem Restore point (so you can restore the system using the Vista/Windows 7Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and pressEnter
- 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 limitedexperimentation 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 useyour system normally, and if you know what causes the crash, do thatrepeatedly. The objective here is to get the system to crash because DriverVerifier is stressing the drivers out. If it doesn't crash for you, then let itrun 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 goingback 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 yourinstallation DVD to set the system back to the previous restore point that youcreated.




Enable the driver verifier

www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html

Ok, I'll try these, see if they work. Thank you.

 

[americancritic]

Hello glad you have seen the posts, go slow at your own speed and it will work just fine, after you have run driver verifier then please give us the results. LOL

 

[richc46]

If the solution does not work, post your new dump reports. We will find the solution.

 

[Bookishbirdy]

If the solution does not work, post your new dump reports. We will find the solution.

It says no device matches the something specified (null) when I try to do that... but I think I'm just going to backup my files while it's possible to even turn on the computer and just buy a new computer... thank you thou for your help, I needed to upgrade to a new computer anyway.

 

[richc46]

We are sorry that we could not be more help, but we do wish you the best of luck and years of enjoyment with the new computer.

 

[americancritic]

Hello I am sorry also that all the things you tried did not work, best of luck with your new system...

Rich you can mark this one as solved...