Error Caused by Device Driver

[noxsachi]

For the past few weeks (mostly since the windows update in mid September, which I have since rolled back) my computer has been having several issues. I am not sure if they are related but I will post them both in the same thread.

-Windows XP pro SP3
-Intel Core 2 Duo E6750
-Abit IP35PRO(P35+ICH9R)
-2gig DDR2 dual channel corsair RAM
-Nvidia Gforce 9800 GTX/GTX+ using driver 6.14.11.7824

The first issue is that I have been having frequent BSODs while gaming, and at times even on start up, however those only occur following a previous BSOD.

For an example of such here is the first BSOD from event viewer followed by the second.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 10/24/2009
Time: 7:00:34 PM
User: N/A
Computer: ALEX
Description:
Error code 1000000a, parameter1 00000000, parameter2 00000002, parameter3 00000001, parameter4 804e237f.

For more information, see Help and Support Center at.
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 30 2c 20 000000,
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 34 65 01, 804e
0050: 32 33 37 66 237f

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 10/24/2009
Time: 7:03:37 PM
User: N/A
Computer: ALEX
Description:
Error code 0000004e, parameter1 00000099, parameter2 00000000, parameter3 00000000, parameter4 00000000.

For more information, see Help and Support Center at.
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 30 30 30 30 30 00000000
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

And here are several more isolated BSOD events

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 10/23/2009
Time: 9:12:38 AM
User: N/A
Computer: ALEX
Description:
Error code 1000008e, parameter1 c0000005, parameter2 805b0ed1, parameter3 b5a13bb4, parameter4 00000000.

For more information, see Help and Support Center at .
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: 38 30 35 62 30 65 64 31 805b0ed1
0040: 2c 20 62 35 61 31 33 62 , b5a13b
0048: 62 34 2c 20 30 30 30 30 b4, 0000
0050: 30 30 30 30 0000

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 10/20/2009
Time: 8:42:43 AM
User: N/A
Computer: ALEX
Description:
Error code 1000000a, parameter1 7f30eef6, parameter2 00000002, parameter3 00000001, parameter4 805172d6.

For more information, see Help and Support Center at .
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 37 66 eters 7f
0030: 33 30 65 65 66 36 2c 20 30eef6,
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 31 01, 8051
0050: 37 32 64 36 72d6

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 10/18/2009
Time: 6:49:53 PM
User: N/A
Computer: ALEX
Description:
Error code 00000019, parameter1 00000020, parameter2 8a9baa08, parameter3 8a9bb808, parameter4 89c017b0.

For more information, see Help and Support Center at
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 31 0000001
0020: 39 20 20 50 61 72 61 6d 9 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 32 30 2c 20 000020,
0038: 38 61 39 62 61 61 30 38 8a9baa08
0040: 2c 20 38 61 39 62 62 38 , 8a9bb8
0048: 30 38 2c 20 38 39 63 30 08, 89c0
0050: 31 37 62 30 17b0


My second issue which may or may not be related is that with that above mentioned windows update (the september one) on my computer while gaming my screen would become covered with artifacts and the game would show up as pink and messed up is the only way I can describe it. Alt-tabbing fixed that issue, however it took about 1min to alt-tab out of the game. This issue occurred with WoW, Aion, and WC3.

So I thought that updating my graphics drivers would resolve it. However when I updated my drivers after the windows splash screen my monitor was blank. Safe Mode worked fine, and thinking the update was to blame for my failure to upgrade drivers I rolled back and tried to update again, however I got the same result.

As I said I am not sure if these issues are related, but any help you can give me into either of them would be greatly appreciated.

 

[Route44]

The three errors we want to concentrate on at this time is the 0xA which is caused by either harware or faulty drivers. The 0x8E which are almost always caused by hardware and are especially a strong indicator of corrupted memory. And 0x4E which is a very strong indicator of corrupted memory.

Since we have no minidumps to read at the moment and since the information you have posted gives no indication as to probable cause, do t standard Memtest diagnostic on your RAM.

See the link below and follow the instructions. There is a newer version than is listed but either one should work. If you need to see what the Memtest screen looks like go to reply #21. The third screen is the Memtest screen.

Let it run for a LONG time. The rule is a minimum of 7 Passes; the more Passes after 7 so much the better. There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

If you have errors you have corrupted memory and it needs to be replaced.

Also, with errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.


Link: https://www.techspot.com/vb/topic62524.html


* Get back to us with the results.

 

[noxsachi]

How do I know what are the relevant mini dumps to submit? As well I have a copy of memtest so I can run it over the next day or something.

 

[Route44]

If you know where to find the minidumps you'll notice that each is assinged a number like 102309-1 which means it was created on October 23, 2009. If it is the second minidump of that particular day it would be followed by a -2 and so on.

 

[noxsachi]

Well I was able to find the dumps for all the errors I posted except for the 10/20 one, there is no .dmp for that date. As well I ran memtest today and got 1 error over 11 passes,
Failing Address 0006e4e1c14 - 1764.8MB
Good 6e4e1e14
Bad 6e5e1c14
Err-Bits
00100000

 

[Route44]

Before reading the dumps it is important to know that if you get any error running Memtest - even one - you have corrupted memory that needs to be replaced. Your next stepis to run Memtest on each stick individually. If you start getting errors before getting to 7 Passes stop the test. You already know it is a bad stick of RAM.

And kudos to you for running Memtest beyond the minimum 7 Passes. Too many people don't even have the patience to run it to 7.