Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

BSODs on W7. Is it SP1 or RAM fault?


  • Please log in to reply

#1
netule

netule

    Member

  • Member
  • PipPip
  • 12 posts
Hi,

I reinstalled my W7 OS on Feb23, 2011. The windows updates came also with the SP1.

On March 1st I bought and installed a second 1GB RAM module, same manufacturer and description as my initial one: 1GB Kingmax, 400Mhz, PC3200, TSOP [MPXD4 - DDR1G400]

As you may see from the report below, my first BSOD came exactly on March 1st.

The first report is from "BlueScreenView" software.
The second report is from "WhoCrashed Home Edition 3.01"

The WhoCrashed program suggests errors with some of my drivers: lan, sound and video. It seems that every time the system crashes there is a different problem. It also says the problems are due to software and not to hardware malfundtions. However, everything coincides with the installation of the new memory module!
This is the first time I have a blue screen on this computer. Is it the SP1 or the new RAM?

I also performed the Memtest86+ which found no errors within the RAM modules.

Can you pls have a look and let me know what I can do?

I will search for new drivers but I am reluctant I'll find updated ones since my computer is quite old, a Fujitsu-Siemens Scenic E600 i865G.

Thanks.

==================================================
Dump File : 031711-33093-01.dmp
Crash Time : 17-Mar-11 09:04:32
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x00000000
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x89a28736
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+67736
File Description : TCP/IP Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\031711-33093-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 139,264
==================================================

==================================================
Dump File : 031611-28250-01.dmp
Crash Time : 16-Mar-11 17:08:52
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : 0xe8001845
Parameter 2 : 0x00000001
Parameter 3 : 0xa1a7617b
Parameter 4 : 0x00000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5ed57
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\031611-28250-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 139,264
==================================================

==================================================
Dump File : 031311-42078-01.dmp
Crash Time : 13-Mar-11 19:12:29
Bug Check String : DRIVER_CORRUPTED_EXPOOL
Bug Check Code : 0x000000c5
Parameter 1 : 0x000004b5
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x8292684e
Caused By Driver : NETIO.SYS
Caused By Address : NETIO.SYS+2b4e
File Description : Network I/O Subsystem
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\031311-42078-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 139,264
==================================================

==================================================
Dump File : 030911-31437-01.dmp
Crash Time : 09-Mar-11 15:59:00
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 0x74d30d64
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x828740f2
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+7bb46
File Description : TCP/IP Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\030911-31437-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 139,264
==================================================

==================================================
Dump File : 030811-30203-01.dmp
Crash Time : 08-Mar-11 23:10:33
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0xf809fe4c
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x8961f9ac
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+5f9ac
File Description : TCP/IP Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\030811-30203-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 139,264
==================================================

==================================================
Dump File : 030411-34953-01.dmp
Crash Time : 04-Mar-11 00:55:44
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 : halmacpi.dll
Caused By Address : halmacpi.dll+3800
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\030411-34953-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 139,264
==================================================

==================================================
Dump File : 030211-31765-01.dmp
Crash Time : 02-Mar-11 17:25:59
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0xf5bac480
Parameter 2 : 0x00000002
Parameter 3 : 0x00000001
Parameter 4 : 0x8960f897
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+6a897
File Description : TCP/IP Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\030211-31765-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 139,264
==================================================

==================================================
Dump File : 030111-47640-01.dmp
Crash Time : 01-Mar-11 21:17:15
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : 0xfff6c3c4
Parameter 2 : 0x00000000
Parameter 3 : 0x8b04ee9e
Parameter 4 : 0x00000000
Caused By Driver : ialmdd5.DLL
Caused By Address : ialmdd5.DLL+29ed8
File Description : DirectDraw® Driver for Intel® Graphics Technology
Product Name : Intel Graphics Accelerator Drivers for Windows NT®
Company : Intel Corporation
File Version : 6.14.10.3889
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\Minidump\030111-47640-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 139,264
==================================================


Welcome to WhoCrashed HOME EDITION v 3.01
--------------------------------------------------------------------------------

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 www.resplendence.com/support

To check if an update of this program is available, click here.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

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.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.



--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: MILICUSH-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Pentium® 4 CPU 2.80GHz Intel586, level: 15
2 logical processors, active mask: 3
RAM: 2138103808 total
VM: 2147352576, free: 1968701440



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 17-Mar-11 07:03:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031711-33093-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x67736)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFFFFF89A28736)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 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 Wed 16-Mar-11 15:07:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031611-28250-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC617B)
Bugcheck code: 0x50 (0xFFFFFFFFE8001845, 0x1, 0xFFFFFFFFA1A7617B, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that invalid system memory has been referenced.
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 Sun 13-Mar-11 17:11:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031311-42078-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x8304)
Bugcheck code: 0xC5 (0x4B5, 0x2, 0x1, 0xFFFFFFFF8292684E)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that the system attempted to access invalid 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. 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 Wed 09-Mar-11 13:57:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030911-31437-01.dmp
This was probably caused by the following module: e1g60i32.sys (E1G60I32+0x17F4)
Bugcheck code: 0xA (0x74D30D64, 0x2, 0x0, 0xFFFFFFFF828740F2)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e1g60i32.sys
product: Intel® PRO/1000 Adapter
company: Intel Corporation
description: Intel® PRO/1000 Adapter NDIS 6 deserialized 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.
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: e1g60i32.sys (Intel® PRO/1000 Adapter NDIS 6 deserialized driver, Intel Corporation).
Google query: e1g60i32.sys Intel Corporation IRQL_NOT_LESS_OR_EQUAL




On Tue 08-Mar-11 21:09:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030811-30203-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x5F9AC)
Bugcheck code: 0xD1 (0xFFFFFFFFF809FE4C, 0x2, 0x0, 0xFFFFFFFF8961F9AC)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 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 03-Mar-11 22:54:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030411-34953-01.dmp
This was probably caused by the following module: smwdm.sys (smwdm+0x75E07)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\smwdm.sys
product: SoundMAX Digital Audio Driver
company: Analog Devices, Inc.
description: SoundMAX Integrated Digital Audio
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: smwdm.sys (SoundMAX Integrated Digital Audio , Analog Devices, Inc.).
Google query: smwdm.sys Analog Devices, Inc. UNEXPECTED_KERNEL_MODE_TRAP




On Wed 02-Mar-11 15:24:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030211-31765-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6A897)
Bugcheck code: 0xD1 (0xFFFFFFFFF5BAC480, 0x2, 0x1, 0xFFFFFFFF8960F897)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 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 01-Mar-11 19:15:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030111-47640-01.dmp
This was probably caused by the following module: ialmdd5.dll (ialmdd5+0x1EE9E)
Bugcheck code: 0x50 (0xFFFFFFFFFFF6C3C4, 0x0, 0xFFFFFFFF8B04EE9E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ialmdd5.dll
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: DirectDraw® Driver for Intel® Graphics Technology
Bug check description: This indicates that invalid system memory has been referenced.
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: ialmdd5.dll (DirectDraw® Driver for Intel® Graphics Technology, Intel Corporation).
Google query: ialmdd5.dll Intel Corporation PAGE_FAULT_IN_NONPAGED_AREA





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

8 crash dumps have been found and analyzed. 3 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:

ialmdd5.dll (DirectDraw® Driver for Intel® Graphics Technology, Intel Corporation)

smwdm.sys (SoundMAX Integrated Digital Audio , Analog Devices, Inc.)

e1g60i32.sys (Intel® PRO/1000 Adapter NDIS 6 deserialized driver, Intel 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.
  • 0

Advertisements


#2
netule

netule

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts
In the mean time, one more BSOD.

Since my Scenic E600 is quite old there aren't anymore any supported drivers for Windows 7 on fujitsu-siemens website. As I already did before having this crashes, I used windows 2000 drivers for all the components that were not properly recognised by W7. This worked before without any problems. But since with the new W7-SP1 or the new memory module everything has changed.

I searched today for new drivers, and although I couldn't find anything better I just reinstalled the drivers for video and audio. While continue to work a new crash happened with a result in a new driver problem...

Welcome to WhoCrashed HOME EDITION v 3.01

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 17-Mar-11 11:07:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031711-29187-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x15D6)
Bugcheck code: 0xD1 (0xFFFFFFFF81FFE058, 0x1C, 0x0, 0xFFFFFFFF81FFE058)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
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 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.

--------------------------------------------------------------------------------
  • 0

#3
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
Bad computer memory is one of the three main reasons for random system failures.. the other two are heat (usually caused by fans or heatsinks being blocked with dust) or power issues...

first...lets make sure its not your memory going bad...get memtest + here....
the lowdown is here..
get the 2nd one down and burn the ISO file to a cd and then boot it from the cd drive...

if you don't have a burning program that will burn .ISO files go here and get burncdcc ..a small FAST no frills iso
burning program...

NOTE...do not put a blank cd in until burncdcc opens the tray for you
1. Start by clicking on BurnCDCC.exe
2. Browse to the ISO file you want to burn on cd/dvd ....in this case its memtest86.iso
3. Select the ISO file
4. click on Start

make sure in the bios the cd drive is the first boot device....put the cd in the cd drive..boot your computer....
let memtest run for at least 3 hours...if it starts showing any errors during that time then you will have to replace the RAM...no errors after 3 hours just press Esc to end the tests and we will try some other tests..
  • 0

#4
netule

netule

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts
I've already ran memtest86+ 2 times, each of them lasting for about 45 minutes.

I'll run it again for the amount of time you specified.

Thanks
  • 0

#5
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
for computer burn in purpose's we let memtest run for 72 hours
thorough test is 8 hours...
for what were doing 2 or 3 hours should show any problems
  • 0

#6
netule

netule

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts
I let the program run for 13 hours.

Ready for new instructions

+ another crush (this was before the memtest began)


On Thu 17-Mar-11 17:07:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031811-24390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x206246)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A3F246, 0xFFFFFFFF8DF4F90C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Attached Thumbnails

  • IMG_0041.JPG

Edited by netule, 18 March 2011 - 12:49 AM.

  • 0

#7
netule

netule

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts
I just plugged in a WinMobile device and when the Wmdc tried to start everything went blue..


On Fri 18-Mar-11 09:19:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031811-23562-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xB7C0A)
Bugcheck code: 0x50 (0xFFFFFFFFB59D2ABA, 0x0, 0xFFFFFFFF9BDB7C0A, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that invalid system memory has been referenced.
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.
  • 0

#8
netule

netule

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts
one more crash, different error



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Fri 18-Mar-11 13:01:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031811-23390-01.dmp
This was probably caused by the following module: hal.sys (hal+0x3014)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF82C24014, 0xFFFFFFFFAB16B980, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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: hal.sys .
Google query: hal.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
  • 0

#9
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
download and install WhoCrashed from http://www.resplende...ashedSetup.exe' class='bbc_url' title='External link' rel='nofollow external'>here..
This program checks for any drivers which may have been causing your computer to crash....

click on it...then run...then next...put a tick in accept...then next..put a tick in the don't create a start menu folder..then next...put a tick in create a desktop icon..then install.. then make sure there is a tick in launch whocrashed...then finish...then click Analyze ...

if you get a message
This software requires the right version of Windows Debugging Tools for your type of computer. Because this is not normally installed and is not redistributable, we suggest you select the download option from below. Then the right package will be downloaded to a temporary folder and the required files will be extracted from the package automatically. You only need to do this once
click on download then try running it again...

WhoCrashed will create report...you have to scroll down to see it
Copy and paste it into your next reply...
================
are you overclocking
  • 0

#10
netule

netule

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts
Every report that I attached to all my posts is taken from WhoCrashed.

The last Conclusion of the report is this:

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

12 crash dumps have been found and analyzed. 4 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:

ialmdd5.dll (DirectDraw® Driver for Intel® Graphics Technology, Intel Corporation)

smwdm.sys (SoundMAX Integrated Digital Audio , Analog Devices, Inc.)

e1g60i32.sys (Intel® PRO/1000 Adapter NDIS 6 deserialized driver, Intel Corporation)

hal.sys

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

I am not overclocking.

Since my computer is quite old and Fujitsu-Siemens does not offer support anymore for Windows 7 or Vista I had to use the drivers from Windows XP. It worked well before installing SP1, but now it seems it won't. The RAM module looks allright so I guess I have to find some drivers "aprooved" by SP1...which I don't know where to get them from. What do you think?
thanks

Edited by netule, 18 March 2011 - 09:49 AM.

  • 0

Advertisements


#11
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
go to your computer manufactures website and get your chipset driver and reinstall it for starters...
then go here and see what they say you need...get a screenshot for me

How to identify your graphics driver version here

Intel® Chipset Identification Utility to identify your Intel® chipset here

just in case we need it later
Intel® Processor Identification Utility here
  • 0

#12
netule

netule

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts

go to your computer manufactures website and get your chipset driver and reinstall it for starters...

I went here http://ts.fujitsu.co.../downloads.html and input my PC id YBFC254818; I selected Win2000 chipset drivers and installed them. No errors.

then go here and see what they say you need...get a screenshot for me

screen shot attached "driver detective.png"


How to identify your graphics driver version here

view picture "intel chipset.png"

Intel® Chipset Identification Utility to identify your Intel® chipset here

view picture "intel chipset id.png" which failed.

just in case we need it later
Intel® Processor Identification Utility here


After installing the W2k video driver the pc hasn't showed another bsod yet (XP driver gave an error).
I notice that Driver Detective has some drivers suitable for my pc but they are not free..

I attached a screen shot(Lan.png) where W7 installed a more recent driver for LAN than the one provided on Fujitsu
website.

Thanks

Attached Thumbnails

  • driver detective.png
  • intel chipset.png
  • intel chipset id.png
  • lan.png
  • intel proc id.png

Edited by netule, 19 March 2011 - 07:56 AM.

  • 0

#13
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
are you having any hard drive...usb...or lan issues now...if not don't worry about the drivers...you only want to update drivers if your having problems...
if its not broke don't fix, is a good rule
  • 0

#14
netule

netule

    Member

  • Topic Starter
  • Member
  • PipPip
  • 12 posts
I haven't had a blue screen for 24 hours since the reinstalling of the same old W2k graphic driver. Not that it is meaningful but it's smth.
Hope it will be stable now. If not I'll probably stress you some more :D

Thanks for your help
  • 0

#15
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
Okie dokie check your device manager...any red or yellow
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP