[Tia218]

Where to start... well its my partners Sept 09 Acer Aspire M6241 running Vista home Basic. (not sure of RAM)

Few weeks ago a windows update overnight started BSOD errors, a system restore and turning off updates helped for short time. (Win Updates meant factory restore on my old XP laptop a couple of years ago! )

But then it got worse, eventually working in odd way. He could boot up once, get random BSOD, open in safe mode, then reboot normally and it would work for hours, but now he's getting BSOD in safe mode and getting increasingly confused and mad. He's tried uninstalling cr*p, altering start up programs and a few resorting to 'last known good' reboots with little long term effect. Friend today had thoughts of failing hard drive but that doesn't add up to me, don't want to back up over 220GB and factory restore if something easier.

I did some googling today, found this place and first access to minidumps through Bluescreenview gave this report going back to the first BSOD on April 11:


==================================================
Dump File : Mini050211-01.dmp
Crash Time : 2011-05-02 16:58:20
Bug Check String : BUGCODE_USB_DRIVER
Bug Check Code : 0x000000fe
Parameter 1 : 0x00000005
Parameter 2 : 0x8539d0e0
Parameter 3 : 0x10de07fe
Parameter 4 : 0x85b3c62c
Caused By Driver : USBPORT.SYS
Caused By Address : USBPORT.SYS+29706
File Description : USB 1.1 & 2.0 Port Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini050211-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 178 256
==================================================

==================================================
Dump File : Mini043011-01.dmp
Crash Time : 2011-04-30 14:07:02
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x00001ab0
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x807e12bf
Caused By Driver : nvstor32.sys
Caused By Address : nvstor32.sys+c2bf
File Description : NVIDIA® nForce™ Sata Performance Driver
Product Name : NVIDIA nForce™ SATA Driver
Company : NVIDIA Corporation
File Version : 10.3.0.33 built by: WinDDK
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini043011-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 138 736
==================================================

==================================================
Dump File : Mini042711-03.dmp
Crash Time : 2011-04-27 17:25:03
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0x00000000
Parameter 2 : 0x0000001b
Parameter 3 : 0x00000001
Parameter 4 : 0x822da5da
Caused By Driver : hal.dll
Caused By Address : hal.dll+770c
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini042711-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 138 736
==================================================

==================================================
Dump File : Mini042711-02.dmp
Crash Time : 2011-04-27 17:16:04
Bug Check String : DRIVER_CORRUPTED_EXPOOL
Bug Check Code : 0x000000c5
Parameter 1 : 0x0007118b
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x822f082a
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+4dfd9
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18327 (vistasp2_gdr.101014-0432)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini042711-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 138 736
==================================================

==================================================
Dump File : Mini042711-01.dmp
Crash Time : 2011-04-27 17:11:33
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0x00000060
Parameter 2 : 0x0000001b
Parameter 3 : 0x00000001
Parameter 4 : 0x822de5ce
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+4dfd9
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18327 (vistasp2_gdr.101014-0432)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini042711-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 138 736
==================================================

==================================================
Dump File : Mini042611-02.dmp
Crash Time : 2011-04-26 16:57:59
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0x00000084
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x825c7ff9
Caused By Driver : hal.dll
Caused By Address : hal.dll+3ff9
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini042611-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 138 736
==================================================

==================================================
Dump File : Mini042611-01.dmp
Crash Time : 2011-04-26 16:55:54
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x28000000
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x8a2321d2
Caused By Driver : storport.sys
Caused By Address : storport.sys+61d2
File Description : Microsoft Storage Port Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini042611-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 133 704
==================================================

==================================================
Dump File : Mini042511-01.dmp
Crash Time : 2011-04-25 16:34:06
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 0x00005003
Parameter 2 : 0xc0802000
Parameter 3 : 0x00007fd3
Parameter 4 : 0x08246f01
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+cdb3f
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18327 (vistasp2_gdr.101014-0432)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini042511-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 138 736
==================================================

==================================================
Dump File : Mini042411-02.dmp
Crash Time : 2011-04-24 17:17:07
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : 0x8c7742a4
Parameter 2 : 0x00000001
Parameter 3 : 0x86cc70b0
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+98379
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18327 (vistasp2_gdr.101014-0432)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini042411-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 138 736
==================================================

==================================================
Dump File : Mini042411-01.dmp
Crash Time : 2011-04-24 16:53:37
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 0x001904aa
Parameter 2 : 0x9cb758ac
Parameter 3 : 0x9cb755a8
Parameter 4 : 0x8a6a3c34
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+9bc34
File Description : NTFS-drivrutin
Product Name : Operativsystemet Microsoft® Windows®
Company : Microsoft Corporation
File Version : 6.0.6000.16386 (vista_rtm.061101-2205)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini042411-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 138 736
==================================================

==================================================
Dump File : Mini042311-01.dmp
Crash Time : 2011-04-23 15:01:13
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 0x00000020
Parameter 2 : 0xac2f6e20
Parameter 3 : 0xac2f6e40
Parameter 4 : 0x0a040808
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+cdb3f
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18327 (vistasp2_gdr.101014-0432)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini042311-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 138 736
==================================================

==================================================
Dump File : Mini042211-01.dmp
Crash Time : 2011-04-22 10:56:33
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8232900c
Parameter 3 : 0x9d8036f4
Parameter 4 : 0x00000000
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+1f805
File Description : Filterhanteraren för Microsofts filsystem
Product Name : Operativsystemet Microsoft® Windows®
Company : Microsoft Corporation
File Version : 6.0.6000.16386 (vista_rtm.061101-2205)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini042211-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 138 736
==================================================

==================================================
Dump File : Mini042111-01.dmp
Crash Time : 2011-04-21 18:30:18
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 0x00000020
Parameter 2 : 0x84e4e978
Parameter 3 : 0x84e4e9a0
Parameter 4 : 0x1805000b
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+cdb3f
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18327 (vistasp2_gdr.101014-0432)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini042111-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 131 072
==================================================

==================================================
Dump File : Mini042011-01.dmp
Crash Time : 2011-04-20 17:42:24
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 0x00005003
Parameter 2 : 0xc0802000
Parameter 3 : 0x00012e8b
Parameter 4 : 0x18be6d12
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini042011-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 131 072
==================================================

==================================================
Dump File : Mini041811-01.dmp
Crash Time : 2011-04-18 18:09:59
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 0x00000020
Parameter 2 : 0x8503a1f0
Parameter 3 : 0x8503a218
Parameter 4 : 0x1805000d
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+cdb3f
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18327 (vistasp2_gdr.101014-0432)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini041811-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 138 736
==================================================

==================================================
Dump File : Mini041111-01.dmp
Crash Time : 2011-04-11 17:38:21
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 0x00000007
Parameter 2 : 0x0000110b
Parameter 3 : 0x00000000
Parameter 4 : 0x8602de68
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+cdb3f
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18327 (vistasp2_gdr.101014-0432)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini041111-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 138 736
==================================================

Very little idea what it all means.. please can you advise?? I just wish it had been something simple to detect. I'm happy to mooch around but his system is Swedish and since it's not my native language I get pretty confused.

Huge thanks for your help. Sadly it's 23.30 here now but that should time for replies before I can get back online. ;o)

Tia

Attached Files

•  crashes.txt   27.16KB   240 downloads

[Advertisements]

Is there any reason why no one has replied... have I done something wrong??

[Tia218]

Is there any reason why no one has replied... have I done something wrong??

[rshaffer61]

Sorry your topic has gone unanswered. We have been very busy but I will try to assist you with your issue.
First all a explanation of your BSOD's.

0x000000FE: BUGCODE_USB_DRIVER
(Click to consult the online MSDN article.)
Usually indicates a USB driver problem. Make sure, though, that you have the latest Windows service pack installed.

What SP do you have installed?

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online Win XP Resource Kit article.)
The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.

Have you run a memory test to make sure your memory is good or not?

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

Have you updated any drivers, added any new software or programs?
How about changed out any hardware?

0x000000C5: DRIVER_CORRUPTED_EXPOOL
(Click to consult the online MSDN article.)
An attempt occurred to touch invalid memory at a process IRQL that is too high. This is almost always caused by drivers that have corrupted the system pool. If you’ve recently installed any new software, check to see if it’s properly installed; and check for updated drivers on the manufacturer’s web site.

Again possible driver issue.

0x0000001A: MEMORY_MANAGEMENT
(Click to consult the online MSDN article.)
This memory management error is usually hardware related. See the General Troubleshooting of STOP Messages checklist above. If this occurs while installing Windows, also check the Windows system requirements including the amount of RAM and disk space required to load the operating system. If none of the above resolves the problem, see the MSDN article linked above for further steps.

Again with a possible memory issue.

0x00000024: NTFS_FILE_SYSTEM
(Click to consult the online MSDN article.)
A problem occurred within NTFS.SYS, the driver file that allows the system to read and write to NTFS file system drives. There may be a physical problem with the disk, or an Interrupt Request Packet (IRP) may be corrupted. Other common causes include heavy hard drive fragmentation, heavy file I/O, problems with some types of drive-mirroring software, or some antivirus software. I suggest running ChkDsk or ScanDisk as a first step; then disable all file system filters such as virus scanners, firewall software, or backup utilities. Check the file properties of NTFS.SYS to ensure it matches the current OS or SP version. Update all disk, tape backup, CD-ROM, or removable device drivers to the most current versions.

Possible HD issue or OS issue.

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
(Click to consult the online MSDN article.)
Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card). Use the General Troubleshooting of STOP Messages checklist above.

Memory again or possible software issue with your anit virus program.

0x00000019: BAD_POOL_HEADER
(Click to consult the online MSDN article.)
A pool header issue is a problem with Windows memory allocation. Device driver issues are probably the msot common, but this can have diverse causes including bad sectors or other disk write issues, and problems with some routers. (By theory, RAM problems would be suspect for memory pool issues, but I haven’t been able to confirm this as a cause.)

Memory or HD issue possible

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
(Click to consult the online MSDN article.)
A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).

Driver or other hardware issue.






Now that seems to cover everything so lets get started.

Tutorial for running chkdsk in Vista\Win 7 located HERE.


Run hard drive diagnostics: http://www.tacktech....ay.cfm?ttid=287
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (select "Write image file to disc" option), and make the CD bootable.

NOTE. If your hard drive is made by Toshiba, try the Hitachi DFT CD Image version of the software

Thanks to Broni for the instructions







If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-2.11.iso.zip file.
3. Inside, you'll find memtest86+-2.11.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-2.11.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

[Tia218]

Thank you so much... been a bit crazy around home too this week.

We obviously have a lot to do over the weekend.

I have one question before we start though, prior to the Windows update on April 11th there were NO BSOD errors at all...nothing! It seems so bizarre to go from nothing to all these errors and potential issues. Is there not one thing that could be responsible for these things going on... or could something software linked be creating the BSODs?

We will be checking things and hoping nothing too scary turns up, just seems like an awful lot for a system that is only just 18 months old!

Will be back in touch again soon. Many thanks again.

Tia

[rshaffer61]

The biggest possibility is a memory problem.
Next I would suspect the hard drive.
Next I would say a driver has become corrupted after the update.


I would advice running the test in this order:

• Memory
• Hard drive
• Then run the following

Please Run the PCPitstop.com OverDrive Full Tests

Here's how:

You must use your Internet Explorer for this procedure. (doesn't work so well in Firefox or others). If your machine is running Vista or Windows 7, you must Select IE to “Run as Administrator”. After completing PCPitstop OverDrive you can close your IE browser and re-open it Normally so that you are no longer running as administrator.

Go to: http://www.pcpitstop.com
Click on "Free Computer Check-up" listed below PC Pitstop OverDrive
In the User Login - Click on "Sign up FREE!"
You'll need to submit a valid email address and create your own password, then click - Create Account(button)

Now enter your email address and password to Log in, Select - Scan this system Now!(button)
You will then be asked to download an ActiveX component and allow it to install.
It is safe and does not compromise your privacy.
Follow the on-screen prompts to install the ActiveX and to allow the Full Tests to be run on your machine.

The Full Tests take about 2 1/2 - 3 minutes on most machines.
When complete, a Results - Summary - Recommended Fixes will be displayed.

Please post the URL internet address, from your Results, back here into this Topic Thread so that we can review the configuration and present performance levels of your machine.

Note: During the graphics 2D and graphics 3D testing, your screen will display some rapidly moving objects.
If you are sensitive to visual flashing, it may cause dizziness. Therefore, look away from the screen during that portion of the testing.

After reviewing the results we will be more informed and may be able to provide better recommendations for you to work towards improving your machine's performance.

While PCPitstop does offer a variety of Paid Products, the PCPitstop OverDrive testing is FREE. Please ignore the references to Paid Products. We prefer to provide manual solution instructions that you can apply directly to your machine.

Best Regards

[swedneck]

Thread starter's frustrated partner (machine owner) chiming in:

After a couple of tries I had the test results for you at http://www.pcpitstop.com/betapit/sec.asp?conid=24352463&report=Summary.

Far from a system expert myself (but I have to admit that I know enough to be embarrassed about the Recycle bin and the Defrag values). However, I have done a disc cleanup, deleted a large folder I had prepared to rescue, and lifted over some 25GB of music to the D: partition. Those things could be done quickly (everything has to be done quickly today). So the free space numbers on the test results should now be around 38% on C: and around 68% on D:.
After having done this, it worked fine the rest of the night and I was stupid enough to get optimistic. Following day though, it turned out that this "working fine session" wasn't more than one of these "random lucky ones" that my partner mentioned in the first post. (Now I'm back where I started - a few minutes of working fine followed by sudden death.)

/Nick

________________________________________________


Additional BSOD reports to the earlier ones:
==================================================
Dump File : Mini050711-01.dmp
Crash Time : 2011-05-07 21:07:42
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8a252d35
Parameter 3 : 0x8cd5db48
Parameter 4 : 0x00000000
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+5d35
File Description : Filterhanteraren för Microsofts filsystem
Product Name : Operativsystemet Microsoft® Windows®
Company : Microsoft Corporation
File Version : 6.0.6000.16386 (vista_rtm.061101-2205)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini050711-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 134 664
==================================================

==================================================
Dump File : Mini050711-02.dmp
Crash Time : 2011-05-07 22:36:41
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0x008736ba
Parameter 2 : 0x0000001b
Parameter 3 : 0x00000001
Parameter 4 : 0x822b6705
Caused By Driver : hal.dll
Caused By Address : hal.dll+7468
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini050711-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 134 664
==================================================

==================================================
Dump File : Mini050711-03.dmp
Crash Time : 2011-05-07 22:43:13
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x0000007f
Parameter 1 : 0x0000000d
Parameter 2 : 0x00000000
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+b752a
File Description : Win32-drivrutin för flera användare
Product Name : Operativsystemet Microsoft® Windows®
Company : Microsoft Corporation
File Version : 6.0.6000.16386 (vista_rtm.061101-2205)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini050711-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 134 664
==================================================

==================================================
Dump File : Mini050711-04.dmp
Crash Time : 2011-05-07 22:52:30
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : 0xc0000005
Parameter 2 : 0x822f982c
Parameter 3 : 0x8b15fb80
Parameter 4 : 0x8b15f87c
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+ee82c
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18327 (vistasp2_gdr.101014-0432)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini050711-04.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 138 736
==================================================

==================================================
Dump File : Mini050811-01.dmp
Crash Time : 2011-05-08 00:14:01
Bug Check String : BUGCODE_USB_DRIVER
Bug Check Code : 0x000000fe
Parameter 1 : 0x00000008
Parameter 2 : 0x00000006
Parameter 3 : 0x00000006
Parameter 4 : 0x85cd2988
Caused By Driver : usbhub.sys
Caused By Address : usbhub.sys+141df
File Description : Default Hub Driver for USB
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini050811-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 208 960
==================================================

==================================================
Dump File : Mini050811-02.dmp
Crash Time : 2011-05-08 17:42:36
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 0x00003451
Parameter 2 : 0xc04f5d50
Parameter 3 : 0x88aa3030
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+cdb3f
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18327 (vistasp2_gdr.101014-0432)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini050811-02.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 138 736
==================================================

==================================================
Dump File : Mini050811-03.dmp
Crash Time : 2011-05-08 17:43:48
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x00000006
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x8eaf15f5
Caused By Driver : USBSTOR.SYS
Caused By Address : USBSTOR.SYS+25f5
File Description : USB Mass Storage Class Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini050811-03.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 173 248
==================================================

==================================================
Dump File : Mini050811-04.dmp
Crash Time : 2011-05-08 23:45:22
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8232f010
Parameter 3 : 0xad57f854
Parameter 4 : 0x00000000
Caused By Driver : luafv.sys
Caused By Address : luafv.sys+98e3
File Description : Filterdrivrutin för LUA-filvirtualisering
Product Name : Operativsystemet Microsoft® Windows®
Company : Microsoft Corporation
File Version : 6.0.6001.18000 (longhorn_rtm.080118-1840)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\Mini050811-04.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6002
Dump File Size : 138 736
==================================================

Edited by swedneck, 11 May 2011 - 05:44 AM.

[rshaffer61]

Do the memory test using Memtest86 and let me know the results. I am checking your PC PitStop log now.
Have you done the hard drive diagnostics test yet?
I also see your Java is out of date and you have two audio drivers that need to be updated.
Please recheck the make and model of the system as I am finding nothing for it on Acers site even close to that make and model number.
Acer Aspire M6241

[rshaffer61]

Are you still having problems with your issue?
It has been 23 days since your last response and I was wondering if the issue has been resolved?
If so can you explain how it was resolved so others may be able to fix it if they have the same issue.
If not please let us know and we can continue with helping you to resolve the issue.

Also if you are certain the update was the problem you could go to Add\Remove Programs and at the top of the window make sure to click the little box about show updates.
Find the update you suspect is the culprit and uninstall it. Let us know if it works.

[swedneck]

Are you still having problems with your issue?
It has been 23 days since your last response and I was wondering if the issue has been resolved?
If so can you explain how it was resolved so others may be able to fix it if they have the same issue.
If not please let us know and we can continue with helping you to resolve the issue............
//..//

Sorry for not replying. In the end I saw what I really wanted to do. Being aware of which league I play in, the only thing I knew that I was on top of was a factory restore. But I also knew what it meant so, even though I knew that it wouldn't get better by itself, I still pushed it forward... and dusted off the old ones and used them instead. Now it's finally done and it's working fine again.
Glad to see that it was a software issue.

Good things have come out of this though. During the time pushing it forward, I have done a lot of reading and today I know a lot more about "how it works" than I did before. Sitting with the old ones also gave me the opportunity to experiment with things that I found too scary to do with the Aspire. (Wouldn't lose anything if something went wrong.) While reading an article about partitions I also ran into a chapter about image backups... and having now realized that this wasn't a thing that "just happened to others", I quickly tried out the mentioned program Acronis True Image and played with it on the old one. Needless to say, it was the first program installed on the Aspire after the restore. This will not happen again. An external harddrive was bought and during one of these "lucky sessions" I managed to save most of my files. Installed programs disappeared in the restore, but it also swept all the crap away. Programs can be reinstalled, but having learned about the usage of image backups (and True Image's 'Try And Decide' tool) it will be easier to keep it clean.

To sum it up: When I sat there fighting the blue screens, the hopelessness was closing up around me. Now, looking back, I'm just grateful. It gave me more than I lost from it. Today I know a lot more about 'what to do', 'what not to do', 'HOW to do'... and last but not least, 'what I will do from now on'.

So I thank you for the time you spent to try helping out. Even though I took another road, your help has still contributed to what I have learned during this.

Best Regards,
/Nick

[rshaffer61]

Thank you for the update and your resolution. I am glad you were able to get everything running again even though it may have not been the way you wanted it to be.
Thank you for allowing us the chance to help and even though we did not in the end resolve the issue our direction gave you the knowledge and experience to move on and find a resolution to help yourself.
I do hope you will return to GTG if you have any other problems and personally want to say thank you for allowing me the chance to assist you.