Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Blue Screen

Started by Breadman Pete , Mar 13 2011 05:05 PM

Please log in to reply

#1
Breadman Pete

Posted 13 March 2011 - 05:05 PM

Member

Member
11 posts

I have an Acer T180
AMD Athlon™ 64x2 Dual core processor
3600+ 2.00 Ghz
Memory(RAM)2.00GB
system type 32-bit operating System

The computer crashes usually when playing a video. I get blue screen that says " IRQL-not less or equal" I don't know what this means. it also says " If this is first time you've seen this stop erroe screen, restart your computer, If this screen appears again follow these steps. check to make sure any new hardware of software is properly installed If new installation ask you harware or software manufacture for any windows update you might need. If problems contiue, disable or remove any newly installed hardware or software, Disable BIOS memory options such as caching or shadowing.If you need to use safe mode to remove or diable components, restart your computer, press F8 to select advance start-up options, and then select Safe Mode.

When it gets to this screen everthing is locked up and I have to un-plug the computer. Please help

#2
Macboatmaster

Posted 13 March 2011 - 08:05 PM

Member
7,237 posts

The most common causes for the "IRQ not less than or equal to" blue screen errors would be faulty or misbehaving driver, driver conflict, or a hardware issue such as faulty memory.

Basically it means that driver or service has tried to access the memory at a higher level than is allowed.

Usually a driver issue.

check to make sure any new hardware of software is properly installed If new installation ask you harware or software manufacture for any windows update you might need

Have you installed any new hardware ie: usb devices, etc. Or have you updated any drivers through one of the sites offering driver updates, - Driver detective, driver agent etc., these type of sites, quite often do supply the wrong driver.

Have you used any sort of registry cleaner - PLEASE DO NOT DO SO. - they can cause such errors.

Download this please
http://www.resplendence.com/whocrashed
Run the program, click the analyse tab and copy and paste the results to your next post.
Pls do not attach them as a file which I then have to open.

Edited by Macboatmaster, 13 March 2011 - 08:06 PM.

#3
Breadman Pete

Posted 15 March 2011 - 05:45 PM

Member

Topic Starter
Member
11 posts

<hr>Welcome to WhoCrashed HOME EDITION v 3.01<hr> 
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution. Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice. This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems. 
To obtain technical support visit <a href="http://www.resplende...ce.com/support" target="_blank">www.resplendence.com/support</a> To check if an update of this program is available, <a href="http://www.resplende...ho30130104.htm" target="_blank">click here.</a> Just click the Analyze button for a comprehensible report ... 
<hr>Home Edition Notice<hr> 
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should ge the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features. <a href="http://www.resplende...whocrashed_pro" target="_blank">Click here for more information on the professional edition.</a> <a href="http://www.resplende...nce.com/buynow" target="_blank">Click here to buy the the professional edition of WhoCrashed.</a> 
<hr>System Information (local)<hr> 
computer name: INGRID-PC windows version: Windows Vista Service Pack 2, 6.0, build: 6002 windows dir: C:\Windows CPU: AuthenticAMD AMD Athlon™ 64 X2 Dual Core Processor 3600+ AMD586, level: 15 2 logical processors, active mask: 3 RAM: 1877811200 total VM: 2147352576, free: 2019348480 
<hr>Crash Dump Analysis<hr> 
Crash dump directory: C:\Windows\minidump 
Crash dumps are enabled on your computer. 
On Tue 3/15/2011 11:53:53 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: <a href="http://www.google.co...q=ntkrpamp.exe" target="_blank">ntkrpamp.exe</a> (nt!Kei386EoiHelper+0x1736) Bugcheck code: 0x7F (0x8, 0xFFFFFFFF80153000, 0x0, 0x0) Error: <a href="http://www.google.co...RNEL_MODE_TRAP" target="_blank">UNEXPECTED_KERNEL_MODE_TRAP</a> Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntkrpamp.exe . Google query: <a href="http://www.google.co...RNEL_MODE_TRAP" target="_blank">ntkrpamp.exe UNEXPECTED_KERNEL_MODE_TRAP</a> 
On Tue 3/15/2011 3:12:45 PM GMT your computer crashed crash dump file: C:\Windows\minidump\Mini031511-01.dmp This was probably caused by the following module: <a href="http://www.google.co...ch?q=amdk8.sys" target="_blank">amdk8.sys</a> (amdk8+0x1A9C) Bugcheck code: 0xA (0xFFFFFFFF8333D340, 0x1C, 0x0, 0xFFFFFFFF822EE9A3) Error: <a href="http://www.google.co..._LESS_OR_EQUAL" target="_blank">IRQL_NOT_LESS_OR_EQUAL</a> file path: C:\Windows\system32\drivers\amdk8.sys product: <a href="http://www.google.co... Windows® Operating System" target="_blank">Microsoft® Windows® Operating System</a> company: <a href="http://www.google.co...rch?q=Microsoft Corporation" target="_blank">Microsoft Corporation</a> description: Processor Device Driver 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. 
On Tue 3/15/2011 12:26:01 AM GMT your computer crashed crash dump file: C:\Windows\minidump\Mini031411-02.dmp This was probably caused by the following module: <a href="http://www.google.co...ch?q=amdk8.sys" target="_blank">amdk8.sys</a> (amdk8+0x1A9C) Bugcheck code: 0xA (0xFFFFFFFF93B42840, 0x1C, 0x1, 0xFFFFFFFF822B6987) Error: <a href="http://www.google.co..._LESS_OR_EQUAL" target="_blank">IRQL_NOT_LESS_OR_EQUAL</a> file path: C:\Windows\system32\drivers\amdk8.sys product: <a href="http://www.google.co... Windows® Operating System" target="_blank">Microsoft® Windows® Operating System</a> company: <a href="http://www.google.co...rch?q=Microsoft Corporation" target="_blank">Microsoft Corporation</a> description: Processor Device Driver 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. 
On Mon 3/14/2011 5:20:38 PM GMT your computer crashed crash dump file: C:\Windows\minidump\Mini031411-01.dmp This was probably caused by the following module: <a href="http://www.google.co...q=ntkrnlpa.exe" target="_blank">ntkrnlpa.exe</a> (nt+0x4DFD9) Bugcheck code: 0xD1 (0x2938, 0xFF, 0x8, 0x8) Error: <a href="http://www.google.co..._LESS_OR_EQUAL" target="_blank">DRIVER_IRQL_NOT_LESS_OR_EQUAL</a> file path: C:\Windows\system32\ntkrnlpa.exe product: <a href="http://www.google.co... Windows® Operating System" target="_blank">Microsoft® Windows® Operating System</a> company: <a href="http://www.google.co...rch?q=Microsoft Corporation" target="_blank">Microsoft Corporation</a> description: NT Kernel & System Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 
<hr>Conclusion<hr> 
4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: <a href="http://www.google.co...q=ntkrpamp.exe" target="_blank">ntkrpamp.exe </a> If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems. Read the topic <a href="http://www.resplende...roubleshooting" target="_blank">general suggestions for troubleshooting system crashes</a> for more information. Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

#4
Macboatmaster

Posted 15 March 2011 - 07:14 PM

Member
7,237 posts

Try again pls
when you click the analyse simply copy and paste just the crsh dump analysis as per this..
On Mon 3/14/2011 06:49:39 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031411-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x38FA9)
Bugcheck code: 0x100000D1 (0xC, 0x2, 0x0, 0xFFFFFFFFA8478FA9)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Protocol Driver
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.

Therefore hold mouse button, drag across analysis. right click copy.
To post reply, right click paste,

Edited by Macboatmaster, 15 March 2011 - 07:15 PM.

#5
Macboatmaster

Posted 15 March 2011 - 07:22 PM

Member
7,237 posts

Further to the above from what I can make out in amongst all the unwanted copy and paste.
FIRSTLY and as advised later in this thread by the Moderator rshaffer61 please do this
RUN A chkdsk /r, that is a five stage check and will take sometime, please do not interrupt it.

After that has completed run a system file c hecker on the cmd sfc /scannow, that ensures that all system files are correct and in the right place.

Here are the instructions for those commands.
CHKDSK
1. Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
2.. Type "chkdsk C: /r" without the quotes and note the space please between chkdsk and C: and C: and /r.
Follow the prompts agreeing to run on reboot.

System file checker.

Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
Type the following command, and then press ENTER: sfc /scannowThe sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions.

AFTER running these commands, see how it is please and if still a problem please follow the advice below.

Go here
http://support.acer....b=1&modelId=386

Check it has remained on the Aspire T180 select your version of Vista as the operating system and download the drivers as follows.and install in this order.
1. Chipset
2. Lan
3. Graphics
4. Audio
5. Wireless.

Do not select the BIOS tab and attempt the BIOS flash. Never flash the BIOS on a working system, except as a last resort and then only if BIOS is corrupt.

BEFORE you do this go Device Manager and check on show hidden devices, that is on the view tab for any warnings on drivers.
Make a note of which has them.
Download and install the drivers I have indicated and then on reboot, check the device manager situation again pls.

Here is how to access device manager
http://windows.micro...-Device-Manager

Edited by Macboatmaster, 15 March 2011 - 09:20 PM.

#6
rshaffer61

Posted 15 March 2011 - 07:31 PM

Moderator

Moderator
34,114 posts

Since this is a BSOD issue you might try this.

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program

#7
Macboatmaster

Posted 15 March 2011 - 07:56 PM

Member
7,237 posts

>On Tue 3/15/2011 11:53:53 PM GMT your computer crashed.crash dump file: C:\Windows\memory.dmpThis was probably caused by the following module =ntkrpamp.exe" target="_blank">ntkrpamp.exe</a> (nt!Kei386EoiHelper+0x1736) Bugcheck code: 0x7F =MSDN+bugcheck+UNEXPECTED_KERNEL_MODE_TRAP" UNEXPECTED_KERNEL_MODE_TRAP Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: =ntkrpamp.exe+UNEXPECTED_KERNEL_MODE_TRAP" ntkrpamp.exe UNEXPECTED_KERNEL_MODE_TRAP

All of his Who Crashed albeit it is more or less unreadable on his copy and paste , which I asked him for seeing the BSOD, indicate - copy and paste from his blue screen
ntkrpamp.exe
This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above
or
IRQL_NOT_LESS_OR_EQUAL

amdk8.sys

which I was thinking if not a driver issue, was then going down the route of ram, temps on graphics. etc.

Edited by Macboatmaster, 15 March 2011 - 08:05 PM.

#8
rshaffer61

Posted 15 March 2011 - 08:27 PM

Moderator

Moderator
34,114 posts

I would say to look more at the OS as the culprit.

The File AmdK8.sys is located in the folder C:\Windows\System32\drivers. Known file sizes on Windows XP are 36,352 bytes (60% of all occurrence), 36,864 bytes, 35,328 bytes, 35,840 bytes.http://www.file.net/process/amdk8.sys.html
The driver can be started or stopped from Services in the Control Panel or by other programs. The program is not visible. There is no detailed description of this service. The file is not a Windows system file. The file is a Microsoft signed file.

Suggestions would be to start with a chkdsk /r and a sfc to make sure the OS is not having a issue.

#9
Breadman Pete

Posted 16 March 2011 - 04:31 PM

Member

Topic Starter
Member
11 posts

On Tue 3/15/2011 11:53:53 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: <a href="http://www.google.co...q=ntkrpamp.exe" target="_blank">ntkrpamp.exe</a> (nt!Kei386EoiHelper+0x1736) Bugcheck code: 0x7F (0x8, 0xFFFFFFFF80153000, 0x0, 0x0) Error: <a href="http://www.google.co...RNEL_MODE_TRAP" target="_blank">UNEXPECTED_KERNEL_MODE_TRAP</a> Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntkrpamp.exe . Google query: <a href="http://www.google.co...RNEL_MODE_TRAP" target="_blank">ntkrpamp.exe UNEXPECTED_KERNEL_MODE_TRAP</a> 
On Tue 3/15/2011 3:12:45 PM GMT your computer crashed crash dump file: C:\Windows\minidump\Mini031511-01.dmp This was probably caused by the following module: <a href="http://www.google.co...ch?q=amdk8.sys" target="_blank">amdk8.sys</a> (amdk8+0x1A9C) Bugcheck code: 0xA (0xFFFFFFFF8333D340, 0x1C, 0x0, 0xFFFFFFFF822EE9A3) Error: <a href="http://www.google.co..._LESS_OR_EQUAL" target="_blank">IRQL_NOT_LESS_OR_EQUAL</a> file path: C:\Windows\system32\drivers\amdk8.sys product: <a href="http://www.google.co... Windows® Operating System" target="_blank">Microsoft® Windows® Operating System</a> company: <a href="http://www.google.co...rch?q=Microsoft Corporation" target="_blank">Microsoft Corporation</a> description: Processor Device Driver 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. 
On Tue 3/15/2011 12:26:01 AM GMT your computer crashed crash dump file: C:\Windows\minidump\Mini031411-02.dmp This was probably caused by the following module: <a href="http://www.google.co...ch?q=amdk8.sys" target="_blank">amdk8.sys</a> (amdk8+0x1A9C) Bugcheck code: 0xA (0xFFFFFFFF93B42840, 0x1C, 0x1, 0xFFFFFFFF822B6987) Error: <a href="http://www.google.co..._LESS_OR_EQUAL" target="_blank">IRQL_NOT_LESS_OR_EQUAL</a> file path: C:\Windows\system32\drivers\amdk8.sys product: <a href="http://www.google.co... Windows® Operating System" target="_blank">Microsoft® Windows® Operating System</a> company: <a href="http://www.google.co...rch?q=Microsoft Corporation" target="_blank">Microsoft Corporation</a> description: Processor Device Driver 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. 
On Mon 3/14/2011 5:20:38 PM GMT your computer crashed crash dump file: C:\Windows\minidump\Mini031411-01.dmp This was probably caused by the following module: <a href="http://www.google.co...q=ntkrnlpa.exe" target="_blank">ntkrnlpa.exe</a> (nt+0x4DFD9) Bugcheck code: 0xD1 (0x2938, 0xFF, 0x8, 0x8) Error: <a href="http://www.google.co..._LESS_OR_EQUAL" target="_blank">DRIVER_IRQL_NOT_LESS_OR_EQUAL</a> file path: C:\Windows\system32\ntkrnlpa.exe product: <a href="http://www.google.co... Windows® Operating System" target="_blank">Microsoft® Windows® Operating System</a> company: <a href="http://www.google.co...rch?q=Microsoft Corporation" target="_blank">Microsoft Corporation</a> description: NT Kernel & System Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 
<hr>Conclusion<hr> 
4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: <a href="http://www.google.co...q=ntkrpamp.exe" target="_blank">ntkrpamp.exe </a> If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems. Read the topic <a href="http://www.resplende...roubleshooting" target="_blank">general suggestions for troubleshooting system crashes</a> for more information. Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

#10
Macboatmaster

Posted 16 March 2011 - 05:20 PM

Member
7,237 posts

You have posted exactly the same as you did before. With respect you must yourself see that it is unreadable without a great deal of effort.
Pls DO NOT post it again until it looks like my example in my post 4.

It is a simple matter of the instructions I gave you in that post.
I do appreciate how stressful it is when something goes worng and you cannot fix it.

However it really is no use posting that sort of unreadable material.

MORE IMPORTANTLY HAVE YOU FOLLOWED THE FULL PROCEDURE IN POST Five please.

Edited by Macboatmaster, 16 March 2011 - 05:21 PM.

#11
rshaffer61

Posted 16 March 2011 - 05:43 PM

Moderator

Moderator
34,114 posts

Just a observation but it looks like the notepad log has word wrap enabled.

#12
Breadman Pete

Posted 16 March 2011 - 06:34 PM

Member

Topic Starter
Member
11 posts

sorry about the post, I don't see anything like the example you gave, sorry I am not very knowledgeable concerning computers. I did the first step. chkdsk I also did the system file check, not sure if it did this, "does it only take a split second" or is it a long scanning type process, it did the prior.. Anyhow I tried watching a video and it crashed so I suppose know I will go to next step..

#13
Macboatmaster

Posted 16 March 2011 - 06:48 PM

Member
7,237 posts

On that system file checker are you certain you are typing the correct command.
it is
sfc /scannow
note space between sfc and the /.
If you type just sfc
it will simply flash once in a split second.

Pls do this for the chkdsk results.
The Vista check disk log can be found as follows: Go to Start, Control Panel,
Administrative Tools, Event Viewer, Windows Logs, Application. Scroll down
the Application Events looking for Wininit in the Source Column.
Double click that entry and please tell us if there were any reports of bad sectors found and were any file errors found other thena minor inconsistencies.

When you run WHo Crashed, you click analyse and then a message appears saying scroll down for the results. You ack that message and the message disappears, you then scroll down until you find the results of the Mini dump analysis. It will not read the same as the one I sent as that is from another thread I was working, but it will look the same. - or should do. ie: in the same format.
You then simply drag your mouse, holding down the left button, acrooss those results,
You let go of the left button and click the right button,a menu appears, you then click Copy with the left button.
On your reply on Geeks, in the message panel you simply right click and on the menu that appears you left click paste.

HOWEVER a few posts back - on post 6 actually - the Moderator asked for a Blue screen view, just after I had said I could not read your Who crashed report. Blue screen view is another utility similar to Who Crashed.
As cannot manage the Who crashed copy and paste PLEASE follow rshaffer61`s instruction for blue screen view.

Edited by Macboatmaster, 16 March 2011 - 07:01 PM.