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

Random BSOD's


  • Please log in to reply
9 replies to this topic

#1 ijabit

ijabit

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:11:43 AM

Posted 24 March 2011 - 11:03 AM

I've been troubleshooting a BSOD for the better part of the day and could use some assistance. The machine is an HP D530 Small Form Factor and the system information is attached. I've also attached several dump files; I loaded the dump files up in windbg they all point to different things:
mfehidk.sys 1000000A
ialmnt5.sys 10000050
ndis.sys 1000000A
ntkrnlmp.exe 1000000A
ntfs.sys 00000024
memory_corruption 0000004E

The red flag for me was memory_corruption. To test this, I removed all memory in the system and replaced with brand new 1GB KTC-D320 stick. However, I still get BSOD's on this machine. Kingston's website lists the D320 as a compatible system (as you'd expect since "D320" is built right into the model number).

If this isn't memory, what else could it be? I ran chkdsk /f and found a few empty sectors marked as allocated, nothing major. There is a single PCI device installed, a Matrox Millennium G450 video card.
I'm running into a brick wall, can someone please help?? Every article and resource says this is a driver or hardware issue but I'm starting to think it's a software issue...

Thanks,
Jim

Attached Files



BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,629 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:01:43 PM

Posted 24 March 2011 - 11:19 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

#3 ijabit

ijabit
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:11:43 AM

Posted 24 March 2011 - 11:28 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


Okay, it doesn't seem to provide as much information, but here you go:
==================================================
Dump File         : Mini032411-01.dmp
Crash Time        : 3/24/2011 10:08:25 AM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x1000000a
Parameter 1       : 0x80f24e00
Parameter 2       : 0x0000001c
Parameter 3       : 0x00000001
Parameter 4       : 0x804e6986
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+f986
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : 32-bit
Computer Name     : 
Full Path         : C:\Users\jab\Documents\share\Dumpfiles\Mini032411-01.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 2600
Dump File Size    : 90,112
==================================================

==================================================
Dump File         : Mini032411-04.dmp
Crash Time        : 3/24/2011 9:59:03 AM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x1000000a
Parameter 1       : 0x000000b8
Parameter 2       : 0x0000001c
Parameter 3       : 0x00000001
Parameter 4       : 0x804e1c18
Caused By Driver  : Ntfs.sys
Caused By Address : Ntfs.sys+e28
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : 32-bit
Computer Name     : 
Full Path         : C:\Users\jab\Documents\share\Dumpfiles\Mini032411-04.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 2600
Dump File Size    : 90,112
==================================================

==================================================
Dump File         : Mini032411-03.dmp
Crash Time        : 3/24/2011 9:40:08 AM
Bug Check String  : PFN_LIST_CORRUPT
Bug Check Code    : 0x0000004e
Parameter 1       : 0x00000007
Parameter 2       : 0x00038ea8
Parameter 3       : 0x00000007
Parameter 4       : 0x00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+606ba
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : 32-bit
Computer Name     : 
Full Path         : C:\Users\jab\Documents\share\Dumpfiles\Mini032411-03.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 2600
Dump File Size    : 90,112
==================================================

==================================================
Dump File         : Mini032411-02.dmp
Crash Time        : 3/24/2011 9:13:26 AM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x1000000a
Parameter 1       : 0x00000010
Parameter 2       : 0x00000002
Parameter 3       : 0x00000000
Parameter 4       : 0x804f2ef5
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1bef5
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : 32-bit
Computer Name     : 
Full Path         : C:\Users\jab\Documents\share\Dumpfiles\Mini032411-02.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 2600
Dump File Size    : 90,112
==================================================

==================================================
Dump File         : Mini032211-09.dmp
Crash Time        : 3/22/2011 3:13:18 PM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x1000000a
Parameter 1       : 0x00000000
Parameter 2       : 0x0000001c
Parameter 3       : 0x00000000
Parameter 4       : 0x805218d7
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4a8d7
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : 32-bit
Computer Name     : 
Full Path         : C:\Users\jab\Documents\share\Dumpfiles\Mini032211-09.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 2600
Dump File Size    : 90,112
==================================================

==================================================
Dump File         : Mini032211-08.dmp
Crash Time        : 3/22/2011 2:37:03 PM
Bug Check String  : PFN_LIST_CORRUPT
Bug Check Code    : 0x0000004e
Parameter 1       : 0x00000099
Parameter 2       : 0x0003ca68
Parameter 3       : 0x00000000
Parameter 4       : 0x00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+606ba
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : 32-bit
Computer Name     : 
Full Path         : C:\Users\jab\Documents\share\Dumpfiles\Mini032211-08.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 2600
Dump File Size    : 90,112
==================================================

==================================================
Dump File         : Mini032211-07.dmp
Crash Time        : 3/22/2011 1:28:01 PM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x1000000a
Parameter 1       : 0xffbe0000
Parameter 2       : 0x00000001
Parameter 3       : 0x00000000
Parameter 4       : 0x804f4c1c
Caused By Driver  : hal.dll
Caused By Address : hal.dll+2aa8
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : 32-bit
Computer Name     : 
Full Path         : C:\Users\jab\Documents\share\Dumpfiles\Mini032211-07.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 2600
Dump File Size    : 90,112
==================================================

==================================================
Dump File         : Mini032211-06.dmp
Crash Time        : 3/22/2011 7:39:42 AM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x1000000a
Parameter 1       : 0x00000012
Parameter 2       : 0x0000001c
Parameter 3       : 0x00000000
Parameter 4       : 0x804e1468
Caused By Driver  : NDIS.sys
Caused By Address : NDIS.sys+19066
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : 32-bit
Computer Name     : 
Full Path         : C:\Users\jab\Documents\share\Dumpfiles\Mini032211-06.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 2600
Dump File Size    : 90,112
==================================================

==================================================
Dump File         : Mini032211-05.dmp
Crash Time        : 3/22/2011 7:38:10 AM
Bug Check String  : PFN_LIST_CORRUPT
Bug Check Code    : 0x0000004e
Parameter 1       : 0x00000007
Parameter 2       : 0x0000c860
Parameter 3       : 0x00000011
Parameter 4       : 0x00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+606ba
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : 32-bit
Computer Name     : 
Full Path         : C:\Users\jab\Documents\share\Dumpfiles\Mini032211-05.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 2600
Dump File Size    : 90,112
==================================================

==================================================
Dump File         : Mini032211-04.dmp
Crash Time        : 3/22/2011 7:36:44 AM
Bug Check String  : PFN_LIST_CORRUPT
Bug Check Code    : 0x0000004e
Parameter 1       : 0x00000099
Parameter 2       : 0x0000a824
Parameter 3       : 0x00000000
Parameter 4       : 0x00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+606ba
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : 32-bit
Computer Name     : 
Full Path         : C:\Users\jab\Documents\share\Dumpfiles\Mini032211-04.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 2600
Dump File Size    : 90,112
==================================================

==================================================
Dump File         : Mini032211-03.dmp
Crash Time        : 3/22/2011 7:35:07 AM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x1000000a
Parameter 1       : 0x00000004
Parameter 2       : 0x00000002
Parameter 3       : 0x00000000
Parameter 4       : 0x804e7f0d
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+10f0d
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : 32-bit
Computer Name     : 
Full Path         : C:\Users\jab\Documents\share\Dumpfiles\Mini032211-03.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 2600
Dump File Size    : 90,112
==================================================

==================================================
Dump File         : Mini032211-02.dmp
Crash Time        : 3/22/2011 7:30:34 AM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x1000000a
Parameter 1       : 0x00000028
Parameter 2       : 0x00000002
Parameter 3       : 0x00000000
Parameter 4       : 0x80517f7b
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+40f7b
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : 32-bit
Computer Name     : 
Full Path         : C:\Users\jab\Documents\share\Dumpfiles\Mini032211-02.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 2600
Dump File Size    : 90,112
==================================================

==================================================
Dump File         : Mini032211-01.dmp
Crash Time        : 3/22/2011 7:24:45 AM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x1000000a
Parameter 1       : 0x00000028
Parameter 2       : 0x00000002
Parameter 3       : 0x00000000
Parameter 4       : 0x80517f7b
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+40f7b
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : 32-bit
Computer Name     : 
Full Path         : C:\Users\jab\Documents\share\Dumpfiles\Mini032211-01.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 2600
Dump File Size    : 90,112
==================================================

==================================================
Dump File         : Mini032111-04.dmp
Crash Time        : 3/21/2011 7:17:49 AM
Bug Check String  : PFN_LIST_CORRUPT
Bug Check Code    : 0x0000004e
Parameter 1       : 0x00000007
Parameter 2       : 0x0000a248
Parameter 3       : 0x0000001b
Parameter 4       : 0x00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+606ba
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : 32-bit
Computer Name     : 
Full Path         : C:\Users\jab\Documents\share\Dumpfiles\Mini032111-04.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 2600
Dump File Size    : 90,112
==================================================

==================================================
Dump File         : Mini032111-03.dmp
Crash Time        : 3/21/2011 7:13:12 AM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x1000000a
Parameter 1       : 0x00690068
Parameter 2       : 0x0000001c
Parameter 3       : 0x00000000
Parameter 4       : 0x804e20bc
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+b0bc
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : 32-bit
Computer Name     : 
Full Path         : C:\Users\jab\Documents\share\Dumpfiles\Mini032111-03.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 2600
Dump File Size    : 90,112
==================================================

==================================================
Dump File         : Mini032111-02.dmp
Crash Time        : 3/21/2011 7:10:06 AM
Bug Check String  : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x1000008e
Parameter 1       : 0xc0000005
Parameter 2       : 0x804f3abe
Parameter 3       : 0xb8720a14
Parameter 4       : 0x00000000
Caused By Driver  : Ntfs.sys
Caused By Address : Ntfs.sys+20a3a
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : 32-bit
Computer Name     : 
Full Path         : C:\Users\jab\Documents\share\Dumpfiles\Mini032111-02.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 2600
Dump File Size    : 90,112
==================================================

==================================================
Dump File         : Mini032111-01.dmp
Crash Time        : 3/21/2011 7:07:52 AM
Bug Check String  : NTFS_FILE_SYSTEM
Bug Check Code    : 0x00000024
Parameter 1       : 0x001902fe
Parameter 2       : 0xb61e25b0
Parameter 3       : 0xb61e22ac
Parameter 4       : 0xf7b76e16
Caused By Driver  : Ntfs.sys
Caused By Address : Ntfs.sys+24e16
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : 32-bit
Computer Name     : 
Full Path         : C:\Users\jab\Documents\share\Dumpfiles\Mini032111-01.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 2600
Dump File Size    : 90,112
==================================================

==================================================
Dump File         : Mini031811-01.dmp
Crash Time        : 3/18/2011 4:20:09 PM
Bug Check String  : PFN_LIST_CORRUPT
Bug Check Code    : 0x0000004e
Parameter 1       : 0x00000099
Parameter 2       : 0x0002e790
Parameter 3       : 0x00000000
Parameter 4       : 0x00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+606ba
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : 32-bit
Computer Name     : 
Full Path         : C:\Users\jab\Documents\share\Dumpfiles\Mini031811-01.dmp
Processors Count  : 1
Major Version     : 15
Minor Version     : 2600
Dump File Size    : 90,112
==================================================


#4 Allan

Allan

  • BC Advisor
  • 8,629 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:01:43 PM

Posted 24 March 2011 - 11:32 AM

OS?

Also, What is new or different since the last time everything worked properly (ie, new hw, new sw, virus, error, etc)?

#5 ijabit

ijabit
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:11:43 AM

Posted 24 March 2011 - 11:35 AM

OS?

Also, What is new or different since the last time everything worked properly (ie, new hw, new sw, virus, error, etc)?


I'm analyzing the dump files on my machine, the machine that is crashing is XP SP3 Pro. There was recently some memory added but as I said earlier we've replaced all of the memory with a brand new stick. Then we tried another brand new stick, still the same. Other than that, the user doesn't recall adding any software and definitely not hardware. The only thing that makes me suspicious is the PCI video card installed.

#6 Allan

Allan

  • BC Advisor
  • 8,629 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:01:43 PM

Posted 24 March 2011 - 11:43 AM

If this all began after the new ram was added, try going back to the original ram and see what happens. Let's not look for zebras if we don't have to. If that is not possible for some reason we CANNOT rule out the possibility of the new ram being the problem, regardless of what you've tried. Still, we can try some other things. Please do all of the following (and yes, I read your first post):

1) Disable the pagefile. Then boot to the Recovery Console and run chkdsk /r (as opposed to chkdsk /f). Again, please do that from the Recovery Console. After you boot back into the OS you can re-enable the pagefile.

2) To check the ram, download memtest (http://www.memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.

3) Update all drivers. Get them from the OEM websites, not from Windows Update

4) Check for a bios update

5) Then boot back into the OS. Do you still get blue screens? If so, boot to safe mode. If you still get blue screens in safe mode then it is definitely a hardware issue. If not, do the following:

Open msconfig and on the General tab choose "selective startup" (disable everything from loading) and reboot. Does the problem still occur? If not, start adding items back to msconfig one or two at a time, rebooting after each change, until the problem reappears and you'll have identified the offending process. This is clearly a time consuming process, but it is the best way to determine if some process loading with the system is the cause of your problem.

Edited by Allan, 24 March 2011 - 11:45 AM.


#7 ijabit

ijabit
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:11:43 AM

Posted 24 March 2011 - 01:50 PM

If this all began after the new ram was added, try going back to the original ram and see what happens. Let's not look for zebras if we don't have to. If that is not possible for some reason we CANNOT rule out the possibility of the new ram being the problem, regardless of what you've tried. Still, we can try some other things. Please do all of the following (and yes, I read your first post):

1) Disable the pagefile. Then boot to the Recovery Console and run chkdsk /r (as opposed to chkdsk /f). Again, please do that from the Recovery Console. After you boot back into the OS you can re-enable the pagefile.

2) To check the ram, download memtest (http://www.memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.

3) Update all drivers. Get them from the OEM websites, not from Windows Update

4) Check for a bios update

5) Then boot back into the OS. Do you still get blue screens? If so, boot to safe mode. If you still get blue screens in safe mode then it is definitely a hardware issue. If not, do the following:

Open msconfig and on the General tab choose "selective startup" (disable everything from loading) and reboot. Does the problem still occur? If not, start adding items back to msconfig one or two at a time, rebooting after each change, until the problem reappears and you'll have identified the offending process. This is clearly a time consuming process, but it is the best way to determine if some process loading with the system is the cause of your problem.



Okay, I have 3 new bluescreens, here's what happened. The machine was running fine for a couple of hours and I got your last post. I took the brand new single 1GB stick out of it and put all for of the old sticks back in, BSOD. So then I took all four out again and put in the same single 1GB stick, BSOD! Then I booted into Bart's PE disc and ran chkdsk /r for a while, BSOD. I've never had a BSOD in Bart's PE before but I'm thinking this is a hardware issue SOMEWHERE. The only thing I didn't do was to disable the pagefile.

#8 Allan

Allan

  • BC Advisor
  • 8,629 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:01:43 PM

Posted 24 March 2011 - 01:56 PM

No need. If you're getting a blue screen in a Bart's then it's a hardware issue.

#9 ijabit

ijabit
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:11:43 AM

Posted 24 March 2011 - 02:14 PM

No need. If you're getting a blue screen in a Bart's then it's a hardware issue.



So it's just figuring if it's the hard drive, video card, or mobo. I don't think it's memory since I've tried so many different sticks. I'm running chkdsk again to see if it's maybe disk related. Do you think the video card could even cause something like this?

#10 Allan

Allan

  • BC Advisor
  • 8,629 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:01:43 PM

Posted 24 March 2011 - 02:18 PM

Easy enough to check - just try a different card. But I'd guess it's memory related since this all started when you changed the ram (or mobo if something happened to the ram slots themselves during the ram switching). But that's simply a guess - hard to tell from here :)




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users