Hi CPC, I can see that you've helped countless individuals with their random crashes. I seem to have problems of the same sort and was wondering if you might lend some assistance as well. I understand that you require "minidumps" but I'm not sure what that is exactly. But here is an example of the errors I recieve in the event viewer after a blue screen:

Error code 1000007f, parameter1 00000008, parameter2 80042000, parameter3 00000000, parameter4 00000000.

Error code 1000000a, parameter1 00000118, parameter2 00000002, parameter3 00000001, parameter4 805001f9.

Error code 10000050, parameter1 fcff06be, parameter2 00000001, parameter3 f76476a6, parameter4 00000000.

Error code 1000000a, parameter1 0000011c, parameter2 00000002, parameter3 00000000, parameter4 804edd8f.

Error code 1000008e, parameter1 c0000005, parameter2 00000000, parameter3 f4cac170, parameter4 00000000.

Error code 100000d1, parameter1 c8def595, parameter2 00000002, parameter3 00000001, parameter4 a49512a7.

Error code 1000000a, parameter1 00000004, parameter2 00000002, parameter3 00000000, parameter4 804fb184.

Error code 0000004e, parameter1 00000099, parameter2 0001a5f3, parameter3 00000000, parameter4 00000000.

If you need more info I would be glad to provide it. Thanks very much, in advace, for your assistance.

Hi CPC here are the error messages in more detail. Sometimes after recieving the BSOD I have to restart my PC two or three times before it will generate an error message as you can see from the time stamps. It will also stack several error messages into one session.

As far as how these error messages began, here's the story. I've built a computer with the following specs over a year ago, and it had been running stable ever since. In the beginning I used to have trouble with my Audigy 2 ZS card, and it would blue screen on me all the time. Then I installed the latest drivers and it resolved the issue. Here are my computer specs:

A8N-SLI deluxe motherboard
2x512mb OCZ DDRAMs
WD 10k RPM 74gb SATA HD
WD 7200RPM 250GB SATA HD
ATI x800 PCI-E video card
SB Audigy 2 ZS audio card
420W power supply

What's funny is that these error messages happened for about 15 days on my Windows XP SP2 Pro before I decided to reformat my PC. I decided to upgrade the OS to MCE 2005 since I recently bought an ATI HDTV wonder card. After a few days I got the BSODs again with some of the same error messages: page_fault, IRQL_error, etc... So I decided to remove the audiy 2 zs card and removed all the drivers thinking that might be the problem, but again I recieved the same error message. Only a few things changed after which I began recieving the error messages...I removed my MS wireless bluetooth keyboard/mouse combo and replaced them with a wired MS keyboard and logitech MX500 optical mouse. I attached them with USB adapters so they go right into the PS2 ports. Also, I just realized that I may have inadvertantly turned off the HD cooler that I installed, but I'm not sure if the error started soon after that. Anyway, my hard drive is now being cooled, but again I recieved the same error messages.

Here are a few of the most recent messages.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/30/2005
Time: 11:12:52 AM
User: N/A
Computer: AMD64BIT3500
Description:
Error code 1000007f, parameter1 00000008, parameter2 80042000, parameter3 00000000, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 37 1000007
0020: 66 20 20 50 61 72 61 6d f Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 38 2c 20 000008,
0038: 38 30 30 34 32 30 30 30 80042000
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 30 30 30 30 00, 0000
0050: 30 30 30 30 0000

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/30/2005
Time: 11:12:11 AM
User: N/A
Computer: AMD64BIT3500
Description:
Error code 1000000a, parameter1 00000118, parameter2 00000002, parameter3 00000001, parameter4 805001f9.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 30 1000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 31 31 38 2c 20 000118,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 31 2c 20 38 30 35 30 01, 8050
0050: 30 31 66 39 01f9

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/27/2005
Time: 10:22:15 AM
User: N/A
Computer: AMD64BIT3500
Description:
Error code 10000050, parameter1 fcff06be, parameter2 00000001, parameter3 f76476a6, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 35 1000005
0020: 30 20 20 50 61 72 61 6d 0 Param
0028: 65 74 65 72 73 20 66 63 eters fc
0030: 66 66 30 36 62 65 2c 20 ff06be,
0038: 30 30 30 30 30 30 30 31 00000001
0040: 2c 20 66 37 36 34 37 36 , f76476
0048: 61 36 2c 20 30 30 30 30 a6, 0000
0050: 30 30 30 30 0000


Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/27/2005
Time: 10:22:06 AM
User: N/A
Computer: AMD64BIT3500
Description:
Error code 1000000a, parameter1 0000011c, parameter2 00000002, parameter3 00000000, parameter4 804edd8f.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 30 1000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 31 31 63 2c 20 00011c,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 38 30 34 65 00, 804e
0050: 64 64 38 66 dd8f


Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/27/2005
Time: 10:21:26 AM
User: N/A
Computer: AMD64BIT3500
Description:
Error code 1000008e, parameter1 c0000005, parameter2 00000000, parameter3 f4cac170, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 30 30 30 30 30 30 30 30 00000000
0040: 2c 20 66 34 63 61 63 31 , f4cac1
0048: 37 30 2c 20 30 30 30 30 70, 0000
0050: 30 30 30 30 0000



Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/25/2005
Time: 7:43:46 PM
User: N/A
Computer: AMD64BIT3500
Description:
Error code 100000d1, parameter1 c8def595, parameter2 00000002, parameter3 00000001, parameter4 a49512a7.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 64 100000d
0020: 31 20 20 50 61 72 61 6d 1 Param
0028: 65 74 65 72 73 20 63 38 eters c8
0030: 64 65 66 35 39 35 2c 20 def595,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 31 2c 20 61 34 39 35 01, a495
0050: 31 32 61 37 12a7


Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/25/2005
Time: 12:52:53 PM
User: N/A
Computer: AMD64BIT3500
Description:
Error code 1000000a, parameter1 00000004, parameter2 00000002, parameter3 00000000, parameter4 804fb184.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 30 1000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 34 2c 20 000004,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 38 30 34 66 00, 804f
0050: 62 31 38 34 b184



Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/25/2005
Time: 12:24:50 AM
User: N/A
Computer: AMD64BIT3500
Description:
Error code 0000004e, parameter1 00000099, parameter2 0001a5f3, parameter3 00000000, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 34 0000004
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 39 39 2c 20 000099,
0038: 30 30 30 31 61 35 66 33 0001a5f3
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 30 30 30 30 00, 0000
0050: 30 30 30 30 0000



Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/25/2005
Time: 12:08:54 AM
User: N/A
Computer: AMD64BIT3500
Description:
Error code 1000000a, parameter1 00000118, parameter2 00000002, parameter3 00000001, parameter4 805001f9.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 30 1000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 31 31 38 2c 20 000118,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 31 2c 20 38 30 35 30 01, 8050
0050: 30 31 66 39 01f9

I think that's enough for now ;-)
Thanks again for any help you could provide me with!

minidump zip files

Here are the five most previous dumps attached as a zip file.

Next four dumps

Here are the next four. If you would like me to generate complete dumps, please let me know. Thanks!

Reload: Latest mobo drivers, then vid card drivers. Check & post...

I actually just updated my A8N-SLI deluxe board to 1016 and latest audio and chipset drivers thinking that might be the problem. I also have catalyst 5.13 installed. I also disconnected my mx500 optical mouse and keyboard from the PS2 and attached them to the USB port in case that was causing the problem. I still generated this latest minidump.

You stated in the last post some problems with the power supply and bad memory. Does that pertain to my problem? Thanks for all your help.

This last dump is too generic to be meaningful.

Diable BIOS caching (in the BIOS) - system & video.

Check the primary disk & defrag it.

Power supplies and faulty ram are possibilities - not in this case though.

Hi Ruder, thanks for the input. There actually aren't options to disable caching or shadowing on the newer A8N-SLI deluxe board. I will continue to check on driver updates in the meantime. One thing I've noticed on the ASUS probe is that my RAM voltages dip quite a bit. But I think it's been doing that since I've built the system, and hasn't given me trouble before. I also use a 420 watt supply which might be pushing it considering the amount of peripheral I have attached. What do you think?

Faulty ram

Hi,

The culprit is faulty ram.
Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
Make sure that the CPU fan works properly
2. Reseat the memory stick to another memory slot. Reseat video card as well.
3. Downclock the ram. Check to default setting if you video card is overclocked.
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
6. Check the bios setting about memory timing and make sure that it is on
For example : DIMM1 and DIMM2 do not have the same timing.
DIMM1: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (2.5-3-3-8 @ 200 MHz) (2.0-3-3-7 @ 166 MHz)
DIMM2: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
DIMM3: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
7. Make sure that your PSU have adequate power to drive all the hardware including USB devices
8. Run chkdsk /r at command prompt
9. Run 3DMark 2005 to test your video card
10. Upgrade BIOS and make sure that the motherboard has no leaking capacitors

If it still crashes, diagnostic which memory stick is faulty
Take out one memory stick. If windows does not crash, the removed memory stick is faulty.

Debug report
Mini122405-01.dmp BugCheck 4E, {99, 0, 0, 0}
Probably caused by : memory_corruption ( nt!MiRestoreTransitionPte+124 ) <- faulty ram or CPU

Mini122405-02.dmp BugCheck 1000000A, {118, 2, 1, 805001f9}
Probably caused by : ntkrnlpa.exe ( nt!KiUnlinkThread+53 ) <- faulty ram

Mini122505-01.dmp BugCheck 4E, {99, 1a5f3, 0, 0}
Probably caused by : win32k.sys ( win32k!HeavyFreePool+bb ) <- faulty ram or CPU

Mini122505-02.dmp BugCheck 1000000A, {4, 2, 0, 804fb184}
Probably caused by : ntkrnlpa.exe ( nt!KeReleaseSemaphore+12 ) <- faulty ram

Mini122605-01.dmp BugCheck 1000008E, {c0000005, 0, f4cac170, 0}
Probably caused by : win32k.sys ( win32k!cCapString+59 ) <- Maybe faulty ram

Mini122605-02.dmp BugCheck 1000000A, {11c, 2, 0, 804edd8f}
Probably caused by : vax347b.sys ( vax347b+2f47 ) <-- No idea

Mini122705-01.dmp BugCheck 10000050, {fcff06be, 1, f76476a6, 0}
Probably caused by : hardware (Ntfs!NtfsInitializeIrpContext+0xed) <- faulty ram

Mini122905-01.dmp BugCheck 1000000A, {118, 2, 1, 805001f9}
Probably caused by : ntkrnlpa.exe ( nt!KiUnlinkThread+53 ) <-- faulty ram

Mini123005-01.dmp BugCheck 1000007F, {8, 80042000, 0, 0} <-- hardware error
Probably caused by : ntkrnlpa.exe ( nt!KiTrap0E+24 ) <- faulty ram

= ASPI SCSI driver for Daemon Tools Ver 3.47

The RAM voltage should be 2.60V ~10% ... if lower causes instability.

Check the other voltages for variances.

Thanks so much CPC for reporting your findings in such detail. I will try your suggestions. So far I have cleaned out the dust (Which isn't much considering I have a 300.00 dollar Lian Li noiseless aluminum case) and have reseated the RAM in different slots. I still get the errors but less now. I will try to upgrade the power supply and see if that helps...I think I need a new one anyway.

Ruder, thank you as well for your viewpoint. According to my ASUS probe, the only voltage readings I am getting for the 3.3, 5.0, and 12.0 are ~3.20, ~4.70 and ~11.50. Sometimes I get a warning that my 5.0V is dipping below the tolerated +/- 10% voltage mark. My Vcore is 1.39, whatever that might be.

I will keep you both updated on my progress. All the best, and Happy New Years!

Hi Bra201,

Do you have any update?

Strange happenings

Hi CPC, sorry for taking some time in getting back. I've been getting killed at the hospital. Anyway this has given me some time to make some minute adjustments and see how my computer responded. Well, I uninstalled my sound card and removed the card physically. Since that time my computer had only been BSODing every three days or so (I keep my computer on 24/7). Then it began happening somewhat more frequently and I took a look at the power adapter from the ATX power supply, and it looked like the adapter that converts the motherboard power cable to one compatible for my ASUS A8N SLI board had a loose pin! Anyway I fixed it and the errors looked like they subsided.

Now a couple weeks ago I turned off my computer before it's usual three day BSOD and when I turned it on again I got BSODs on startup! now this was the first time. I restarted the computer at least 10 times and even in safe mode and just got this fruitbasket of varying BSOD messages 0x00000008E 5A 1E, etc...I installed XP w/ the repair option and my computer began working normally again with it's usual three day BSODs. Now just yesterday I turned off my computer before it had a chance to BSOD and I got the same thing!

Now before I explain further let me explain my motherboard memory configuration. I have 512MB Corsair memory installed in slots 1 and 3 with slots 2 and 4 empty. I forgot exactly why I had it setup this way but it has something to do with them working in parallel.

Now this time instead of reinstalling XP I removed the 512MB RAM from slot 3 and it worked! Now I took that same memory and placed it in slot 1 and it worked! Then I took both pieces of memory and placed them in slot 1 and 2 and they work! But when I put them in slot 1 and 3 I BSOD on startup again. I just made this change so let's see what happens over the next few days. I feel like my PC is falling apart and it could be the memory, board, drive or PS. I just don't have the funds to change too many things right now! I'll keep you posted on the outcome of this new change.

Maybe dust inside the memory slot

Hi bra201,

Maybe it is related to the dust into the memory slot. Clean the dust inside the memory slot may resolve the blue screen problem.

Resolved???

Well it's almost the end of the month. After installing, and reinstalling drivers, removing internal components, changing IRQ's and the whole shabang, it seems that the one thing I really needed to do was fix the short-circuited pin on the ATX 20 to 24 pin motherboard adapter and move both memory sticks to the slot 1 and 2 position. That was it! I mean, it sounds like the stupidest thing on earth but ever since I tweaked that pin and shuffled the memory, I haven't had a single BSOD. It all really came down to a power supply and/or memory problem, in essence. I think the next step at this point is to get a real PS w/o the need for a PCI-e or motherboard adapter like the coolermaster 680 watt power supply. Then I'll go back to reinstalling all the peripheral devices I removed, and see what happens from there. I'll keep the site posted in case anyone is benefiting from my problems! I think I'll also contact ASUS for a new board since it makes no sense why memory shouldn't work in slots 1 and 3.

Thanks to all of you! I have a laptop at work doing same sort of thing, I'll just log warranty request saying bad memory or do you think its more of a mobo problem? Doesn't matter much, I'm just wondering. This was the only site from my quick google I could find.

Problem almost solved

I thought I'd give an important update at this juncture. After removing all the dust from within the case, amking sure all the peripheral cards were properly plugged in, upgrading to a 680 watt power supply with the latest ATX power standards I have made the following discovery. When my OCZ memory is placed in slots 1 and 3, technically known as slots A1 and B1 which allows the memory to operate in dual channel mode, my PC blue screens at random. But when the memory is placed in slots 1 and 2, technically known as B1 and B2, it then operates in single channel mode and my PC remains running stable 24/7 for weeks until I manually shut down. Apparantly this is not a unique problem. I've found similar posts all over the web. Here's one example:
http://www.bleedinedge.com/forum/printthread.php?t=8006

According to that post which had the exact same problem as mine, there is not a problem with memory or the motherboards since both were RMA'd and the problem reoccured when the memory was placed in dual channel mode.

The fact that this happened so suddenly last year leads me to believe that either the CPU is fried or the bios that I installed at the time has caused some compatibility problems for memory in dual channel. Anyway, until I figure out the exact cause I'll keep my memory in single-channel mode.

Solution

OK, I don't know if anyone has been following this thread but I finally figured out what was going wrong. After noticing that people had similar posts which started around July of last year...almost the same time as me...I began to wonder. The latest bios revision I had for my A8N-SLI deluxe board is 1017. I decided to roll back the bios to the one in July and see what happens. When I rolled back to 1011 my PC would BSOD every 15 minutes instead of every other day! Then I decided to roll back the BIOS all the way to when I knew for a fact my PC was rock solid stable...That was revision 1006. I've been using this BIOS revision with my memory in dual-channel mode for the last 2 1/2 weeks and my PC has been running 24/7 ever since. There you have it. ASUS and their nuts-for-brains techs changed something in the BIOS since 1006 that caused dual-channel mode to run unstable and that buggy program has been trailing forth ever since.

I have met so many people with Asus boards that were flakey (to include myself) it isn't funny. I use MSI only now.