Windows XP Home - BSOD

[Sigmund.F]

Hi,
my friends mom's laptop crash every time when I try to start it. Memtest86+ doesnt find anything.

Specs: Fujitsu-Siemens AMILO M1425

http://www.laptopsdirect.co.uk/Fujitsu-Siemens-Amilo-M-1425-Base-Model-LKN:GBR-15/version.asp

minidumps included

- Sigmund

 

[Broni]

To make things easier to read...

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.

 

[Sigmund.F]

==================================================
Dump File : Mini020710-05.dmp
Crash Time : 7.2.2010 22:31:24
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0xff1711f2
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x804d9b64
Caused By Driver : w22n51.sys
Caused By Address : w22n51.sys+6a112
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : J:\Mini020710-05.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini020710-04.dmp
Crash Time : 7.2.2010 22:28:38
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0xff1711f2
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x804d9b64
Caused By Driver : w22n51.sys
Caused By Address : w22n51.sys+6a112
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : J:\Mini020710-04.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini020710-03.dmp
Crash Time : 7.2.2010 22:24:00
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0xff1711f2
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x804d9b64
Caused By Driver : w22n51.sys
Caused By Address : w22n51.sys+6a112
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : J:\Mini020710-03.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini020710-02.dmp
Crash Time : 7.2.2010 21:04:22
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x0000047b
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0xf7432e9f
Caused By Driver : NDIS.SYS
Caused By Address : NDIS.SYS+18e9f
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : J:\Mini020710-02.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini020710-01.dmp
Crash Time : 7.2.2010 13:54:34
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0xff1711f2
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x804d9b64
Caused By Driver : w22n51.sys
Caused By Address : w22n51.sys+6a112
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : J:\Mini020710-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

 

[Route44]

Four of you minidumps cite 0xA errors which are caused by either hardware or drivers. In your case all four cited the same Intel wireless driver w22n51.sys as your issue.

 

[Broni]

That's it.
Try to reinstall it.

 

[Sigmund.F]

I updated the Intel Wireless drivers to:

Intel PRO/Wireless 2200BG & 2915ABG
Version: 9.0.3.9

Let's see what happens

 

[Route44]

One other thing that I wanted to mention but I was kicked back to my desktop is that the fifth minidump was an 0xD1 and these are caused mostly by faulty drivers and sometimes by faulty or mismatched memory.

The driver cited is an F-Secure firewall driver fsdfw.sys. We've seen it where NIC drivers and security suits don't always play well together.

Also, in this dump two things stood out. First is Code Corruption and the second is Memory_Corruption_Patch. You may want to go to the F-Secure forums and/or tech information to see if there is any information on your security software and these items.