[Cunjurongkid]

Hi team,
I am hoping that someone could give me some advice as to what to do now with my laptop. Hope this is the correct bit on the "board" to post it.

Since the 5th April while collecting Farmville gifts off my Facebook page my laptop has randomly BSOD & rebooted. I followed recommendations to do virus scans which came up empty with Avast (free) Bootscans also showed nothing. According to the control panel the only recent updates had been adobe reader as far as I could see so I removed them, there has been no hardware or software upgrades done. Windows updates are done up to date, I even downloaded AVG free & ran that, it did come up with some cookies but nothing too exciting, in the rootscan that I ran it did find something out of place so I told it to remove that (sorry I didn't get its name)
It was only today that I discovered that you could stop the computer from re-booting automatically so I was able to get the following message/codes IRQL_NOT_LESS_OR_EQUAL & *** STOP 0x0000000A (0xFFFFFFF0, 0x00000002, 0x00000000, 0x804E2284)

It doesn't happen all the time, just totally randomally, I can be doing the same things over & over again (collecting Farmville gifts off the wall) & nothing then the next time bam! BSOD! It doesn't happen at any other time & it can go a day or so without doing it then off it goes again

I didn't know if it was something in my laptop's hardware that was dying so I was going to download a RAM stress tester to see if anything was on the way out & that that's what the problem was.

After the problems started I did back-up my information, I would have just done a system re-boot but that setting had been turned off.

I still have my original XP discs & was wondering whether to just do a clean install & see what happened but if it was caused by an update then it would just happen again. My other thought was to upgrade to Windows 7, after running the update advisor it says that my system can handle it.

Thanks in advance for your help, I'm not extremely computer savvy but I'll do my best to follow your instructions.

Cheers,
Jodie

[Advertisements]

0x0000000A: IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online MSDN article.)
Typically due to a bad driver, or faulty or incompatible hardware or software. Use the General Troubleshooting of STOP Messages checklist above. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)

Go to

Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Reboot after your done running chkdsk /r...
then Go to Start...Run and type: eventvwr.msc press Enter
When Event Viewer opens, click on Applications... then scroll down to [b]Winlogon]/b] and double-click on it. This is the log created after running Checkdisk...copy and paste the log back here


We will advise after studying the log.

[rshaffer61]

0x0000000A: IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online MSDN article.)
Typically due to a bad driver, or faulty or incompatible hardware or software. Use the General Troubleshooting of STOP Messages checklist above. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own.)

Go to

Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y
If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Reboot after your done running chkdsk /r...
then Go to Start...Run and type: eventvwr.msc press Enter
When Event Viewer opens, click on Applications... then scroll down to [b]Winlogon]/b] and double-click on it. This is the log created after running Checkdisk...copy and paste the log back here


We will advise after studying the log.

[Cunjurongkid]

Here you go...


Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 748 unused index entries from index $SII of file 0x9.
Cleaning up 748 unused index entries from index $SDH of file 0x9.
Cleaning up 748 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

244187968 KB total disk space.
53668596 KB in 143301 files.
64040 KB in 17930 indexes.
0 KB in bad sectors.
288800 KB in use by the system.
65536 KB occupied by the log file.
190166532 KB available on disk.

4096 bytes in each allocation unit.
61046992 total allocation units on disk.
47541633 allocation units available on disk.

Internal Info:
b0 b4 02 00 da 75 02 00 be ec 03 00 00 00 00 00 .....u..........
94 4c 00 00 03 00 00 00 f1 07 00 00 00 00 00 00 .L..............
a8 88 1a 05 00 00 00 00 f6 c9 fb 84 00 00 00 00 ................
d0 88 c3 10 00 00 00 00 8e 60 35 d7 04 00 00 00 .........`5.....
f0 06 d6 a6 09 00 00 00 a6 e7 4a 22 0f 00 00 00 ..........J"....
99 9e 36 00 00 00 00 00 98 38 07 00 c5 2f 02 00 ..6......8.../..
00 00 00 00 00 d0 ab cb 0c 00 00 00 0a 46 00 00 .............F..

Windows has finished checking your disk.
Please wait while your computer restarts.


For more information, see Help and Support Center at
http://go.microsoft....ink/events.asp.

Thankyou

[rshaffer61]

Go Start and then to Run ("Start Search" in Vista),
Type in: sfc /scannow
Click OK (Enter in Vista).
Have Windows CD/DVD handy.
If System File Checker (sfc) finds any errors, it may ask you for the CD/DVD.
If sfc does not find any errors in Windows XP, it will simply quit, without any message.
In Vista you will receive the following message: "Windows resource protection did not find any integrity violations".

For Vista users ONLY: Navigate to C:\Windows\Logs\CBS folder. You'll see CBS.log file.
Usually, it's pretty big file, so upload it to Flyupload, and post download link.


If you don't have Windows CD....
This applies mostly to Windows XP, since Vista rarely requires use of its DVD while running "sfc"
Note This method will not necessarily work as well, as when using Windows CD, because not always ALL system files are backed up on your hard drive. Also, backed up files may be corrupted as well.

Go Start and then Run
type in regedit and click OK


Navigate to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup

You will see various entries Values on the right hand side.

The one we want is called: SourcePath

It probably has an entry pointing to your CD-ROM drive, usually D and that is why it is asking for the XP CD.
All we need to do is change it to: C:
Now, double click the SourcePatch setting and a new box will pop up.
Change the drive letter from your CD drive to your root drive, usually C:
Close Registry Editor.

Now restart your computer and try sfc /scannow again!


Thanks to Broni for the instructions



Revised and Simplified:


Do you have a valid XP CD?

If so, place it in your CD ROM drive and follow the instructions below:

• Click on Start and select Run... type sfc /scannow (note the space) (Let this run undisturbed until the window with the blue progress bar goes away)

SFC - Which stands for System File Checker,
retrieves the correct version of the file from %Systemroot%\System32\Dllcache or the Windows installation source files, and then replaces the incorrect file.
If you want to see what was replaced, right-click My Computer and click on Manage. In the new window that appears, expand the Event Viewer (by clicking on the + symbol next to it) and then click on System.

[Cunjurongkid]

I don't actually have the XP CD that is currently installed on this computer (my Mum's partner bought it & the code/key home from work & took all the CD's when he moved out)
I do have another XP CD that was from my other laptop, would that be of any use or would it just confuse things not being the same CD that was installed on this laptop?

[Cunjurongkid]

Ok, so I went through the registry & found the source path & changed it to C:/ rather then D:/ & then restarted my laptop as per Broni instructions.

When it restarted I ran sfc /scannow

It came up with a box stating
Files that are required for Windows to run properly must be copied to the DLL cache.
Insert your Windows XP Professional CD-ROM now.

Did I miss something?

[rshaffer61]

Nope you didn't miss anything. It happens when something it needs cannot be found. Click enter or retry and see if it keeps going.
If not then you will have to borrow a XP cd. The one for your laptop will not work.

[Cunjurongkid]

What would be the difference with borrowing an XP cd to using the other one that I've got? It's the original Windows XP Home Edition Version 2002 Includes Service Pack 1 disc that I have, I just didn't use it when I installed XP on this laptop as it was already in use on another laptop which has since "passed on".
If it's a matter of the codes/key not matching then the same would hold true with a borrowed cd wouldn't it?
Sorry to seem vague.

I will keep trying the sfc /scannow & if it says to skip the file yes or no I could just try yes & see what happens instead of cancelling it?

[rshaffer61]

The one you mentioned is from a laptop and usually does not work with these steps.
Is the laptop one a full version or is it a recovery disk for the laptop?

[Cunjurongkid]

it's a full version, I just looked for a recovery disc & no luck.
So the only disc that I have is a full version of Windows XP that isn't the same disc that was used on this laptop's install. It isn't in use currently (the full version on the other disc) as the laptop that it was on originally has since died & been buried.

Edited by Cunjurongkid, 02 May 2011 - 09:09 PM.

[rshaffer61]

If the disc is full version then it should work. You are not reinstalling but only checking the System Files with this step.

[Cunjurongkid]

So I'll stick that disc in & then run the sfc /scannow?
Should I do a backup or something first? It's not going to automatically reinstall XP is it?
Sorry to seem paranoid.

** well I tried to run it & put the cd in when it asked & it told me
The CD you provided is the wrong CD.
Please insert the Windows XP Professional CD-ROM into your CD-ROM drive

So I can't get any further either with or without it

Edited by Cunjurongkid, 02 May 2011 - 10:32 PM.

[rshaffer61]

Nope no reinstall as you found out.
Now you need to borrow a XP Pro cd to do the step.

Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.

Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply







http://www.resplendence.com/downloads

[Cunjurongkid]

Wow, that was quick & painless


Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Mon 2/05/2011 6:06:46 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini050211-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x1F33B)
Bugcheck code: 0x1000000A (0xFFFFFFFFFFFFFFF0, 0x2, 0x0, 0xFFFFFFFF804E2284)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software CUSTOM_ERROR




On Fri 29/04/2011 6:52:37 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini042911-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x20A8C)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8053B9FF, 0xFFFFFFFFB48D1B0C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M




On Mon 25/04/2011 9:40:33 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini042611-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF8AC5)
Bugcheck code: 0x10000050 (0xFFFFFFFF9AD4D8F8, 0x0, 0xFFFFFFFF805CFAC5, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 20/04/2011 12:03:56 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini042011-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x12769)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805BC23D, 0xFFFFFFFFB3826C60, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M




On Sun 17/04/2011 12:35:06 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041711-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x27AF)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF832F1CB0, 0xFFFFFFFF832F1CD8, 0xA050027)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 Fri 15/04/2011 8:54:35 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041511-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x118E1)
Bugcheck code: 0x10000050 (0xFFFFFFFFF000EEF3, 0x8, 0xFFFFFFFFF000EEF3, 0x2)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software CUSTOM_ERROR




On Tue 12/04/2011 8:05:31 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041211-02.dmp
This was probably caused by the following module: ipnat.sys (ipnat+0xF34E)
Bugcheck code: 0x1000000A (0xFFFFFFFF9AC28430, 0x2, 0x1, 0xFFFFFFFF805469D0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\ipnat.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IP Network Address Translator
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 12/04/2011 7:58:01 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041211-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x2339)
Bugcheck code: 0x100000D1 (0x4, 0x2, 0x1, 0xFFFFFFFFB9E1E339)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System 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.


On Thu 7/04/2011 11:47:05 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040711-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x1D7C2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8053BA38, 0xFFFFFFFFB3CA9974, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M




On Tue 5/04/2011 7:08:54 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini040511-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x118E1)
Bugcheck code: 0x10000050 (0xFFFFFFFF9ADB4F18, 0x0, 0xFFFFFFFF805BC23D, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software CUSTOM_ERROR




On Mon 6/09/2010 10:33:34 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini090610-01.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x29A3E3)
Bugcheck code: 0x10000050 (0xFFFFFFFFB0195000, 0x1, 0xFFFFFFFFBF2AC3E3, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 174.82
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 174.82
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: nv4_disp.dll (NVIDIA Compatible Windows 2000 Display driver, Version 174.82 , NVIDIA Corporation).
Google query: nv4_disp.dll NVIDIA Corporation CUSTOM_ERROR




On Tue 27/07/2010 9:32:11 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini072710-01.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x29A3E3)
Bugcheck code: 0x10000050 (0xFFFFFFFFB2C45000, 0x1, 0xFFFFFFFFBF2AC3E3, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 174.82
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 174.82
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: nv4_disp.dll (NVIDIA Compatible Windows 2000 Display driver, Version 174.82 , NVIDIA Corporation).
Google query: nv4_disp.dll NVIDIA Corporation CUSTOM_ERROR





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

12 crash dumps have been found and analyzed. 8 third party drivers have 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:

aswsp.sys (avast! self protection module, AVAST Software)

nv4_disp.dll (NVIDIA Compatible Windows 2000 Display driver, Version 174.82 , NVIDIA Corporation)

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 general suggestions for troubleshooting system crashes 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.

[rshaffer61]

Uhhhh what version of Avast are you running?