Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

unable to find cause of bsod


  • Please log in to reply
14 replies to this topic

#1 Byte By Byte PC

Byte By Byte PC

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:06:33 PM

Posted 28 February 2011 - 11:04 AM

hello all. i have a machine that a built for a customer about a month or so ago. winxp pro sp3 4gb ram 2.81ghz amd x4 630 cpu. also mobo is ecs mcp61m-m3 v1.0 i for life of me cannot figure out the bsod. bsod only occures on COLD startup, ie machine is off all night ad you turn on in the morning.

category: 102 type; error event id:103 Error code 100000d1, parameter1 90545a1b, parameter2 0000001c, parameter3 00000008, parameter4 90545a1b.

another error code same event id Error code 100000d1, parameter1 90503850, parameter2 0000001c, parameter3 00000008, parameter4 90503850.


any help would be much appreciated. im thinking potential driver issues, but i canot pin point this down. thank you!

Edited by Byte By Byte PC, 28 February 2011 - 11:29 AM.


BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,734 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:07:33 PM

Posted 28 February 2011 - 11:19 AM

Please post the detail for those errors, as reflected in Event Viewer.

You may want to take a look at http://www.eventid.net/display.asp?eventid=103&source=

Louis

#3 Byte By Byte PC

Byte By Byte PC
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:06:33 PM

Posted 28 February 2011 - 11:26 AM

Attached File  event.bmp   35.76KB   6 downloadshere is a quick screen shot of the event

Edited by Byte By Byte PC, 28 February 2011 - 11:28 AM.


#4 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:08:33 PM

Posted 28 February 2011 - 11:30 AM

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

#5 Byte By Byte PC

Byte By Byte PC
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:06:33 PM

Posted 28 February 2011 - 12:00 PM

hey thx for a new diagnostic tool! never seen this one before. here is the data.
==================================================
Dump File : Mini022811-01.dmp
Crash Time : 2/28/2011 8:26:22 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x90545a1b
Parameter 2 : 0x0000001c
Parameter 3 : 0x00000008
Parameter 4 : 0x90545a1b
Caused By Driver : hal.dll
Caused By Address : hal.dll+291a
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini022811-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini022611-01.dmp
Crash Time : 2/26/2011 8:07:27 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x90503850
Parameter 2 : 0x0000001c
Parameter 3 : 0x00000008
Parameter 4 : 0x90503850
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini022611-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini022511-02.dmp
Crash Time : 2/25/2011 8:33:07 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x98503850
Parameter 2 : 0x0000001c
Parameter 3 : 0x00000008
Parameter 4 : 0x98503850
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini022511-02.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini022511-01.dmp
Crash Time : 2/25/2011 8:31:20 AM
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x1000007f
Parameter 1 : 0x0000000d
Parameter 2 : 0x00000000
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+8b87a
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6064 (xpsp_sp3_gdr.101231-1614)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini022511-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini022411-01.dmp
Crash Time : 2/24/2011 1:06:09 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0xe0e12494
Parameter 2 : 0x00000001
Parameter 3 : 0x00000000
Parameter 4 : 0x80505f37
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+2ef37
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6055 (xpsp_sp3_gdr.101209-1647)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini022411-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini022311-01.dmp
Crash Time : 2/23/2011 9:24:34 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x98503850
Parameter 2 : 0x0000001c
Parameter 3 : 0x00000008
Parameter 4 : 0x98503850
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+e28
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini022311-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini022211-01.dmp
Crash Time : 2/22/2011 9:41:13 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x90503850
Parameter 2 : 0x0000001c
Parameter 3 : 0x00000008
Parameter 4 : 0x90503850
Caused By Driver : NDIS.sys
Caused By Address : NDIS.sys+6b85
File Description : NDIS 5.1 wrapper driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-0852)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini022211-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini022111-02.dmp
Crash Time : 2/21/2011 8:29:06 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x90503850
Parameter 2 : 0x0000001c
Parameter 3 : 0x00000008
Parameter 4 : 0x90503850
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini022111-02.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini022111-01.dmp
Crash Time : 2/21/2011 8:25:01 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x56df86c5
Parameter 2 : 0x0000001c
Parameter 3 : 0x00000000
Parameter 4 : 0x88503857
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini022111-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini021811-02.dmp
Crash Time : 2/18/2011 7:57:57 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x55f1eefd
Parameter 2 : 0x0000001c
Parameter 3 : 0x00000000
Parameter 4 : 0x88503857
Caused By Driver : aswSP.SYS
Caused By Address : aswSP.SYS+9901
File Description : avast! self protection module
Product Name : avast! Antivirus System
Company : AVAST Software
File Version : 5.1.889.0
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini021811-02.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini021811-01.dmp
Crash Time : 2/18/2011 8:40:01 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x1418f28d
Parameter 2 : 0x0000001c
Parameter 3 : 0x00000000
Parameter 4 : 0x88503857
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+2f65
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6064 (xpsp_sp3_gdr.101231-1614)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini021811-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini021611-01.dmp
Crash Time : 2/16/2011 9:05:40 AM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x56df86c5
Parameter 2 : 0x0000001c
Parameter 3 : 0x00000000
Parameter 4 : 0x88503857
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini021611-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

#6 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:08:33 PM

Posted 28 February 2011 - 12:20 PM

Okay, here's what I suggest:

1) Go to the websites of your various hardware manufacturers and download and install the latest drivers (especially video, audio & NIC if appropriate). Again, obtain the drivers ONLY from the OEM websites. Also check to see if you have the current chipset driver.

2) Check to see if you have the latest version of Avast. If not, download and install the latest version.

3) Check for a bios update

#7 Byte By Byte PC

Byte By Byte PC
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:06:33 PM

Posted 28 February 2011 - 12:36 PM

i had aready tried bios update last week, avast is current.i will try to search fro some better drivers for the mobo as mobo manufacturer included their latest drivers on cd. Do you have any other suggesions? I hate to format and start over just to find the problem still will exist. thank you thus far.

#8 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:08:33 PM

Posted 28 February 2011 - 12:42 PM

Bad or conflicting drivers is the most common cause of your error. It could also be ram related. If you haven't already done so you should run a diagnostic on the ram.

You can also set the pagefile to zero and then run chkdsk /r from the recovery console. After you finish, be sure to set the pagefile back to system managed. The reason for resetting the pagefile is to insure that the error isn't caused by a hard disk problem in the area where the pagefile is located. If there is, the checkdisk will go more quickly if the space isn't occupied.

Edited by Allan, 28 February 2011 - 12:44 PM.


#9 Byte By Byte PC

Byte By Byte PC
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:06:33 PM

Posted 28 February 2011 - 08:37 PM

i completely wiped out all the drivers and reinstalled them. ill find out mro if it crashes on cold boot if customer calls. thanks for the help. im gonna go bonkers if it still acts up. memory passed all tests.

#10 noknojon

noknojon

  • Banned
  • 10,871 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:10:33 AM

Posted 28 February 2011 - 10:43 PM

Hi -
As stated above by Allan you should also run a Check Disk r scan as there are several points in the report that show the basic system
may have some problems - Here is a simple code for the chkdsk /r if you can open Run Box -
Open the Run Box and copy / paste this code into it to run the 5 stage check disk scan -
CMD /C ECHO Y|CHKDSK C: /R | SHUTDOWN /R /T 30
This will reboot your system in 30 seconds, so please close all programs (internet also) and click OK -
As the scan will take 30 to 45 mins (on average) put on the kettle (or fix another project) and just let the scan run to completion -

Thank You -
EDIT -
Save the code if you want for future uses -

Edited by noknojon, 28 February 2011 - 10:51 PM.


#11 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:08:33 PM

Posted 01 March 2011 - 08:07 AM

i completely wiped out all the drivers and reinstalled them. ill find out mro if it crashes on cold boot if customer calls. thanks for the help. im gonna go bonkers if it still acts up. memory passed all tests.

How did you "wipe out all the drivers"?

Also, the preferred method for running checkdisk with XP is simply to boot to the recovery console and run chkdsk /r

#12 noknojon

noknojon

  • Banned
  • 10,871 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:10:33 AM

Posted 01 March 2011 - 06:13 PM

>> Also, the preferred method for running checkdisk with XP is simply to boot to the recovery console and run chkdsk /r <<

The code I listed takes care of all operations involved with Check Disk and makes it simple to explain to most users -
The auto reboot in 30 seconds saves you logging off and back on to start the program - It is just a Reboot and chkdsk /r in one simple application -
I have used this code for many years and even use it on my own XP every month or 2, just to check for problems -

>> i completely wiped out all the drivers and reinstalled them <<
I assume you mean Uninstalled and Reinstalled (not wiped out) the drivers -

Edited by noknojon, 01 March 2011 - 06:15 PM.


#13 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:08:33 PM

Posted 01 March 2011 - 06:16 PM

Didn't say there's anything wrong with your method John :).

#14 Byte By Byte PC

Byte By Byte PC
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:06:33 PM

Posted 02 March 2011 - 12:33 AM

unit still has exact same problem this morn. from a cold boot it took 6 trys before it booted. all hardware diagnostics pass. i guess ill have to do a backup, format, reinstall and cross fingers. only other rhing i can think of is perhaps a bad motherboard.................

#15 hamluis

hamluis

    Moderator


  • Moderator
  • 55,734 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:07:33 PM

Posted 02 March 2011 - 08:38 AM

FWIW: I suspect that...memory, hard drives, and PSUs...all go bad more frequently than motherboards. I would choose those as hardware suspects before i ever thought of the motherboard.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users