Multiple Repeating BSOD's on Packard Bell Dot MU laptop

Hello,

· OS - Windows 7 Home Premium 64-bit
· What was original installed OS on system? - Windows 7 Home Premium
· The OS is an OEM version
· Age of system - 2 Years
· Age of OS installation - 1 Day
· CPU - Intel Celeron CPU 743 @ 1.30GHz 1.30Ghz
· Video Card - Unknown built in
· MotherBoard - Unknown, built in
· Power Supply - HIPRO 30w

I have been having problems with my Packard Bell Dot M/U laptop for a while, getting various Blue Screens, mainly stating DRIVER_IRQL_NOT_LESS_OR_EQUAL.

After searching for various solutions without success I got into safemode, backed up all of my files to my external HD and decided to do a system factory reset and clean install of windows 7 Home Premium.

When this first ran it crashed during install but I didn't see the message, upon re-starting it went into a restart loop where windows said that it had had an unknown error and windows could not be installed, please restart!

I managed to get it to re-start the whole process, wiping and re-installing windows again, this time it got further, I can get into the setup screens for windows, first the language screen, then the username screen, password and licence terms, then the updates screen (where i'm selecting ask me later) and finally date and time settings, It then says Finalizing windows and then the BSOD appears! Eventually I have managed to get the computer to finish the installation, each time getting a little bit further before it crashes.

I have had 3 different blue screens -

DRIVER_IRQL_NOT_LESS_OR_EQUAL
*** STOP: 0x000000D1 (0x0000000000000000,0x000000000000001,0xFFFFF88001070771)
*** iastor.sys - Address FFFFF88001070771 base at FFFFF88001026000, datestamp 4a287aa4

BAD_POOL_CALLER
*** STOP: 0x000000C2 (0000000000000007,0x00000000000001097, 0x0000000000000000, 0xFFFFFA8006CEAFC0)

SYSTEM_SERVICE_EXCEPTION
*** STOP: 0x0000003B (0x00000000C000001D, 0xFFFFF80002A84E32, 0xFFFFF880051ACD70, 0x0000000000000000)

*** STOP: 0x00009087 (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)

I Think its a faulty driver of some sort, but have no idea how to identify whats the problem or how to fix it!

Its a laptop with no new hardware, nothing plugged into USB's so its not a new piece of hardware I've installed, and I've done a complete wipe and re-install yet its still BSOD'ing

I have included my windows dump files and some analysis files for reference.

Any Ideas?

Many Thanks

Liam

liamomuk said:

Hello,

· OS - Windows 7 Home Premium 64-bit
· What was original installed OS on system? - Windows 7 Home Premium
· The OS is an OEM version
· Age of system - 2 Years
· Age of OS installation - 1 Day
· CPU - Intel Celeron CPU 743 @ 1.30GHz 1.30Ghz
· Video Card - Unknown built in
· MotherBoard - Unknown, built in
· Power Supply - HIPRO 30w

I have been having problems with my Packard Bell Dot M/U laptop for a while, getting various Blue Screens, mainly stating DRIVER_IRQL_NOT_LESS_OR_EQUAL.

After searching for various solutions without success I got into safemode, backed up all of my files to my external HD and decided to do a system factory reset and clean install of windows 7 Home Premium.

When this first ran it crashed during install but I didn't see the message, upon re-starting it went into a restart loop where windows said that it had had an unknown error and windows could not be installed, please restart!

I managed to get it to re-start the whole process, wiping and re-installing windows again, this time it got further, I can get into the setup screens for windows, first the language screen, then the username screen, password and licence terms, then the updates screen (where i'm selecting ask me later) and finally date and time settings, It then says Finalizing windows and then the BSOD appears! Eventually I have managed to get the computer to finish the installation, each time getting a little bit further before it crashes.

I have had 3 different blue screens -

DRIVER_IRQL_NOT_LESS_OR_EQUAL
*** STOP: 0x000000D1 (0x0000000000000000,0x000000000000001,0xFFFFF88001070771)
*** iastor.sys - Address FFFFF88001070771 base at FFFFF88001026000, datestamp 4a287aa4

BAD_POOL_CALLER
*** STOP: 0x000000C2 (0000000000000007,0x00000000000001097, 0x0000000000000000, 0xFFFFFA8006CEAFC0)

SYSTEM_SERVICE_EXCEPTION
*** STOP: 0x0000003B (0x00000000C000001D, 0xFFFFF80002A84E32, 0xFFFFF880051ACD70, 0x0000000000000000)

*** STOP: 0x00009087 (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)

I Think its a faulty driver of some sort, but have no idea how to identify whats the problem or how to fix it!

Its a laptop with no new hardware, nothing plugged into USB's so its not a new piece of hardware I've installed, and I've done a complete wipe and re-install yet its still BSOD'ing

I have included my windows dump files and some analysis files for reference.

Any Ideas?

Many Thanks

Liam

Hi and these are virtually identical. All related to your iastor driver. Update it and any other older driver listed below.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\dump\053111-45973-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 UP Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a4a000 PsLoadedModuleList = 0xfffff800`02c87e50
Debug session time: Tue May 31 04:54:32.260 2011 (GMT-4)
System Uptime: 0 days 0:15:13.336
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ffffffffffffffe1, 2, 1, fffff880010f54ff}

Unable to load image \SystemRoot\system32\DRIVERS\iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
Probably caused by : iaStor.sys ( iaStor+524ff )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffffffffffffe1, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880010f54ff, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf20e0
 ffffffffffffffe1 

CURRENT_IRQL:  2

FAULTING_IP: 
iaStor+524ff
fffff880`010f54ff 48894620        mov     qword ptr [rsi+20h],rax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  taskhost.exe

TRAP_FRAME:  fffff80000ba2960 -- (.trap 0xfffff80000ba2960)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=7fffffffffffffff rbx=0000000000000000 rcx=fffffa8002de1000
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880010f54ff rsp=fffff80000ba2af0 rbp=0000000000000000
 r8=fffffa8002de1000  r9=0000000000000000 r10=fffff880010a86b8
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
iaStor+0x524ff:
fffff880`010f54ff 48894620        mov     qword ptr [rsi+20h],rax ds:1d80:00000000`00000020=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002abb469 to fffff80002abbf00

STACK_TEXT:  
fffff800`00ba2818 fffff800`02abb469 : 00000000`0000000a ffffffff`ffffffe1 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00ba2820 fffff800`02aba0e0 : fffff880`013eb110 fffff880`05d1a340 fffffa80`03e20060 fffffa80`03294b60 : nt!KiBugCheckDispatch+0x69
fffff800`00ba2960 fffff880`010f54ff : fffffa80`06be4678 fffff880`0441011b fffffa80`07189190 fffffa80`06b927a8 : nt!KiPageFault+0x260
fffff800`00ba2af0 fffffa80`06be4678 : fffff880`0441011b fffffa80`07189190 fffffa80`06b927a8 fffffa80`06be49b8 : iaStor+0x524ff
fffff800`00ba2af8 fffff880`0441011b : fffffa80`07189190 fffffa80`06b927a8 fffffa80`06be49b8 fffffa80`06be49c8 : 0xfffffa80`06be4678
fffff800`00ba2b00 fffff880`0440b75c : fffffa80`06be4678 fffffa80`06b927a8 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiInterlockedInsertTailList+0x47
fffff800`00ba2b50 00000000`00000000 : fffff880`05d1a340 fffff880`010a9136 fffffa80`02de4b00 00000000`00000014 : dxgmms1!VidSchiFreeQueuePacket+0xa4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
iaStor+524ff
fffff880`010f54ff 48894620        mov     qword ptr [rsi+20h],rax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  iaStor+524ff

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStor

IMAGE_NAME:  iaStor.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a287aa4

FAILURE_BUCKET_ID:  X64_0xD1_iaStor+524ff

BUCKET_ID:  X64_0xD1_iaStor+524ff

Followup: MachineOwner
---------

Older drivers

Code:

DKbFltr.sys    3/25/2009 11:15:42 PM        fffff880`0270c000    fffff880`02718000    0x0000c000    0x49caf35e                        
amdxata.sys    5/19/2009 1:56:59 PM        fffff880`0117c000    fffff880`01187000    0x0000b000    0x4a12f2eb                        
iaStor.sys    6/4/2009 9:53:40 PM    iaStor.sys+524ff    fffff880`0102d000    fffff880`01149000    0x0011c000    0x4a287aa4

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Thanks for your message, I have downloaded the rootkit detector and after a few reboots/crashes it eventually ran and said there was one file, It has now re-booted and I'm running it again to see what it says, will post back anything it comes up with.

Righto, this time its come back clean, so fingers crossed its ok, any suggestions of any other checks i should do to make sure?

Thanks again.

liam