Error Caused by a Device Driver

[madcow9597]

Shuttle AV49PN

Hi all, I recently bought a shuttle AV49 PN. I get BSOD errors pointing to my new video card but I will not accept that that is the problem. I suspect the AGP Driver my board which has a VIA chipset. I saw others in this thread with the exact same problem. I think VIA needs to get involved and create good drivers.

 

[Solomon]

Problem apparently solved! *looks sheepish*

For several months, my computer's been rebooting itself. After extensive research on the 'Microsoft is still researching this problem' and 'Error caused by a device driver' messages, I decided to pull the side cover off and have a look-see.

What did I find? The CPU heat sink looked like a square, extremely furry gray mouse with no tail and a fan attached to his back. Now, mind you, this is one of half a dozen computers I've built in the past five years for the house here and other people. I lecture them about maintenance, I lecture them about keeping the area around the computer free of dust bunnies and debris, but do I follow my own advice? Nooooo

So, I started cleaning, and in so doing, discovered that the CPU fan was kaput, which makes sense, considering that a few weeks prior to the crashing behavior, there was a horrendous, dying-cow noise coming from the case for a few days. Since it had quit, I chose the lazy way and decided that it had fixed itself. Pffft.

Well, after cleaning the inside of the case and spending $13 on a new heat sink and ball-bearing fan, I'm going on 2 full days without a single reboot, which has been unheard of in the past few months. I've also downloaded and installed "Mother Board Monitor", a great little program that allows you to monitor and set up alarms based on component temperatures, voltages, and fan speeds.

I'm pretty glad that I didn't wreck the whole kit and caboodle by being lazy. As a developer for 6 years, including work at several giant companies (including the biggest of them all), you'd think that I'd be geeky enough to enjoy tinkering with the hardware and such, and I generally do, but for some reason, cleaning the tower always seems to fall between the cracks.

Pop that cover off and clean your computer out! Keep yourself grounded and grab a toothbrush for those hard to reach spots while lightly vacuuming the whole thing. I try to hover the vacuum hose near the tooth brush to keep from banging into things.

Looks like I've gotten lucky this time!

Thanks,

Solomon :grinthumb

 

[SWAT]

Hello, I'm here because of the same problem as everyone else, and I'd appreciate some help. My computer's only four months old and I haven't added any hardware since I built it. The BSOD only started happening about two months ago, and it only happens about once a week, usually in the middle of the night when I let it run.

Here's some system info:
- OS: Windows XP SP 2
- CPU: AMD ATHLON 64 3500+
- RAM: OCZ DUAL CHANNEL OPTIMIZED 2X512MB DDR PC3200
- MB: DFI LANPARTY UT NF4 ULTRA-D
- Video Card:SAPPHIRE RADEON X800 XL PCI-E

Attached are some minidumps.

Thanks in advance, and I promise to give feedback on any solutions provided.

 

[cpc2004]

Hi SWAT.

Maybe you have multiple culprits. The first culprit is NVTcp.sys. Viist the nVidia WebPage and look for the solution. The second culprit may be faulty RAM.

 

[cpc2004]

For several months, my computer's been rebooting itself. After extensive research on the 'Microsoft is still researching this problem' and 'Error caused by a device driver' messages, I decided to pull the side cover off and have a look-see.

What did I find? The CPU heat sink looked like a square, extremely furry gray mouse with no tail and a fan attached to his back. Now, mind you, this is one of half a dozen computers I've built in the past five years for the house here and other people. I lecture them about maintenance, I lecture them about keeping the area around the computer free of dust bunnies and debris, but do I follow my own advice? Nooooo

So, I started cleaning, and in so doing, discovered that the CPU fan was kaput, which makes sense, considering that a few weeks prior to the crashing behavior, there was a horrendous, dying-cow noise coming from the case for a few days. Since it had quit, I chose the lazy way and decided that it had fixed itself. Pffft.

Well, after cleaning the inside of the case and spending $13 on a new heat sink and ball-bearing fan, I'm going on 2 full days without a single reboot, which has been unheard of in the past few months. I've also downloaded and installed "Mother Board Monitor", a great little program that allows you to monitor and set up alarms based on component temperatures, voltages, and fan speeds.

I'm pretty glad that I didn't wreck the whole kit and caboodle by being lazy. As a developer for 6 years, including work at several giant companies (including the biggest of them all), you'd think that I'd be geeky enough to enjoy tinkering with the hardware and such, and I generally do, but for some reason, cleaning the tower always seems to fall between the cracks.

Pop that cover off and clean your computer out! Keep yourself grounded and grab a toothbrush for those hard to reach spots while lightly vacuuming the whole thing. I try to hover the vacuum hose near the tooth brush to keep from banging into things.

Looks like I've gotten lucky this time!

Thanks,

Solomon :grinthumb

Hi Solomon,

From the debug report of your minidumps the failing module (ie ExInsertTailNBQueue+3f) is very conistent. Usually it is overheat and it is hardware problem. Hardware crash usually crashes at random pattern and the failing module is random. Anyway you resolved the problem. Repost if you need further help.

Mini081105-01.dmp 50 (e482bff8, 00000000, 804f30fd, 20000000) wdmaud+7b7 -> nt!ExInsertTailNBQueue+3f
Mini081005-02.dmp 50 (ec82bfd7, 00000000, 804f30fd, 00000000) HPZius12+37c5 -> nt!ExInsertTailNBQueue+3f
Mini081105-03.dmp 50 (d882bfe9, 00000000, 804f30fd, 00000000) wdmaud+7b7 -> nt!ExInsertTailNBQueue+3f
Mini081105-02.dmp 7E (c0000005, 804f30fd, f41c2ad4, f41c27d4) HPZius12+37c5 -> nt!ExInsertTailNBQueue+3f

 

[afi]

hopefully this wil give me some answers...i ahve no idea what is wrong with it, but i bet it is probably more then one thing. However i am uncertain as to why it only happens when i play games.

here are the minidumps..

cheers

 

[cpc2004]

Hi Afi,

Your minidumps are half years ago and I will not investigatw your minidumps.

 

[afi]

ahh **** really i must have uploaded the wrong ones.. sorry bout that....dnt worry i duno wats wrong with the thing il just format the piece of crap. thanks anyway

 

[enciel]

I am experiencing this randomly sometimes when i try to play psx this appears or when i open an application it appears T_T can anyone help me in this?

here's a zip of my My minidump


i hope anyone knows how to read this minidump and can tell me what could be the possible solution for this help is greatly appreciated!!

 

[SWAT]

An update on my situation...

Turns out the nVidia hardware firewall (which uses NVTcp.sys), generates random BSODs when running P2P software (which I was doing every time I got a BSOD). This is apparently a problem everyone using the firewall has, and the latest drivers still cannot fix it. Shutting off the firewall solved my problems. I guess I'll simply wait for drivers expected in September, or maybe get a software firewall.

As for my crashes that might be caused by faulty RAM, I'll try to run memtest this weekend and report the results here.

Thanks again cpc!

 

[BugHI]

BSOD too when tyring to connect online :-(

Hello,

You've guessed it, I'm new too :slurp:

I'm currently trying to setup a PPPoE Internet connection in Windows XP Pro via Network Connections. Everything worked fine until when it first attempts to connect. The usual connection status box displayed the normal "Registering..." message, then Windows gives me the BSOD. I'm completely at a lost to explain what happened. Someone sugggested that it might be a hardware/driver issue. Can someone please have a look at it?


Here are some info:

Specs:

T42 Thinkpad PM 1.8
512
60 GB
Intel PRO 1000 MT Mobile
Intel PRO 2200 wireless (I wasn't using wireless when the crashes occurred)



Event logs:

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 15/08/2005
Time: 11:50:14 PM
User: N/A
Computer: MOBILEBUG
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x348b0000, 0xb7eec7e8, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini081505-05.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 15/08/2005
Time: 2:26:35 AM
User: N/A
Computer: MOBILEBUG
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007f (0x0000000d, 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini081505-04.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 15/08/2005
Time: 1:30:01 AM
User: N/A
Computer: MOBILEBUG
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x10000050 (0xb7ddd14f, 0x00000001, 0x81d74a68, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini081505-03.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 15/08/2005
Time: 1:01:20 AM
User: N/A
Computer: MOBILEBUG
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007f (0x00000005, 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini081505-02.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.





Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 15/08/2005
Time: 12:56:59 AM
User: N/A
Computer: MOBILEBUG
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0xff623906, 0x00000002, 0x00000001, 0x82039a7c). A dump was saved in: C:\WINDOWS\Minidump\Mini081505-01.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

[cpc2004]

Dear All,

As this thread has 12 pages. Please open a new thread for new case. I will still response to the old cases within this thread.

cpc2004.

 

[cpc2004]

Hello,

You've guessed it, I'm new too :slurp:

I'm currently trying to setup a PPPoE Internet connection in Windows XP Pro via Network Connections. Everything worked fine until when it first attempts to connect. The usual connection status box displayed the normal "Registering..." message, then Windows gives me the BSOD. I'm completely at a lost to explain what happened. Someone sugggested that it might be a hardware/driver issue. Can someone please have a look at it?


Here are some info:

Specs:

T42 Thinkpad PM 1.8
512
60 GB
Intel PRO 1000 MT Mobile
Intel PRO 2200 wireless (I wasn't using wireless when the crashes occurred)



Event logs:

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 15/08/2005
Time: 11:50:14 PM
User: N/A
Computer: MOBILEBUG
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x348b0000, 0xb7eec7e8, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini081505-05.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 15/08/2005
Time: 2:26:35 AM
User: N/A
Computer: MOBILEBUG
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007f (0x0000000d, 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini081505-04.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 15/08/2005
Time: 1:30:01 AM
User: N/A
Computer: MOBILEBUG
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x10000050 (0xb7ddd14f, 0x00000001, 0x81d74a68, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini081505-03.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 15/08/2005
Time: 1:01:20 AM
User: N/A
Computer: MOBILEBUG
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007f (0x00000005, 0x00000000, 0x00000000, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini081505-02.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.





Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 15/08/2005
Time: 12:56:59 AM
User: N/A
Computer: MOBILEBUG
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0xff623906, 0x00000002, 0x00000001, 0x82039a7c). A dump was saved in: C:\WINDOWS\Minidump\Mini081505-01.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Hi BugHi,

ZoneAlarm is the culprit. De-install ZoneAlarm and install another firewalll software.

 

[cpc2004]

I am experiencing this randomly sometimes when i try to play psx this appears or when i open an application it appears T_T can anyone help me in this?

here's a zip of my My minidump


i hope anyone knows how to read this minidump and can tell me what could be the possible solution for this help is greatly appreciated!!

This is hardware problem and I believe that it is faulty RAM. One of your minidump has memory at XP system service table.

STACK_COMMAND: .bugcheck ; kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
804e270c-804e270f 4 bytes - nt!KiServiceTable+64
[ 49 6b 56 80:18 98 1f f9 ]
804e274c-804e274f 4 bytes - nt!KiServiceTable+a4 (+0x40)
[ 61 e7 56 80:d0 97 1f f9 ]
804e275c-804e275f 4 bytes - nt!KiServiceTable+b4 (+0x10)
[ b8 77 5b 80:20 da 1e f9 ]
804e27c4-804e27c7 4 bytes - nt!KiServiceTable+11c (+0x68)
[ 68 ee 56 80:a8 e2 1e f9 ]
804e27cc-804e27cf 4 bytes - nt!KiServiceTable+124 (+0x08)
[ 28 eb 57 80:10 99 1f f9 ]
804e2884-804e2887 4 bytes - nt!KiServiceTable+1dc (+0xb8)
[ fb 7a 56 80:94 97 1f f9 ]
804e2928-804e292b 4 bytes - nt!KiServiceTable+280 (+0xa4)
[ 71 eb 56 80:c8 e2 1e f9 ]
804e296c-804e296f 4 bytes - nt!KiServiceTable+2c4 (+0x44)
[ bb b0 56 80:66 98 1f f9 ]
804e2a6c-804e2a6f 4 bytes - nt!KiServiceTable+3c4 (+0x100)
[ 27 55 66 80:b0 90 1f f9 ]
36 errors : !nt (804e270c-804e2a6f)

MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE

 

[madcow9597]

Hey same Mobo as inexactitude

Hey I have a feeling you have the same problem as I do. I have the same shuttle Motherboard as you do and have the same BSOD message. Except I have an ATI 850 XT. The BSOD says it's my ati2caq.dll error. This has to do with VIA AGP Driver i suspect . All my attemps to repair it have failed. ATI is trying to help me. VIA has no way to help me or at least havent tried. I am going to purchase a new PSU to see if that is the problem since mine is a 300W I'll up it to 450W see if thathelps. I have a freind working on my 1GB memory dump to see what it says. I think it'll say bad hardware which i know is wrong. The only bad hardware I think i have is this new MOBO with a VIA chipset. My sis board did not have this error or any flicker of problems. VIA U SUCK!

 

[BugHI]

cpc2004, you the man (or woman... uh oh, go tmyself into a political correctness dilemma )

I got rid of ZonaAlarm and the thing worked like wonders. However, out of curiosity, I recall that it is only in the 5th minidump that there was a ZA driver mentioned. How did you get to the correct conclusion that the four others were caused by the same app?

In any case, thank you so much, now I can sleep :bounce:

 

[Otmakus]

got the same problem here

-win xp pro sp2
-mobo gigabyte GA-7N400SL (onboard LAN and sound)
-athlon XP 2000+
-2 x 512MB RAM corsair value
-pixelview GF4 MX 4000 with 7189 driver (no the 6177 driver doesn't support my video card)

I got the same problems since about 2 months ago, my machine crashed after i used it to play games (all range of games, from call of duty, battle of middle earth, to ragnarok online, which shouldn't take too much resources), usually in about an hour or so into the game (but sometimes as early as 5 minutes into the game), sometimes the game just showed me an error message and went back to windows, sometimes the machine just went blank and restarted, and then after the reboot, there is an error message "ur machine has recovered from a serious error" and after i submitted the error to microsoft, there was the "error caused by a device driver". i've searched extensively in microsoft's website and followed their instruction, trying drivers from the oldest to the latest, to no avail.

I've tried to reformat windows a few times now, the last time i only installed the drivers from the mobo's cd and nvidia driver right after i installed windows, and then play some games, and the same error happened.
I've replaced my PSU, tried to use a single stick of RAM, a single stick of borrowed Kingston RAM, and the same error still happened, so i'm pretty sure it's not my RAM or PSU.

I first thought it may be because of overheating (my CPU temperature reached 62 Celcius in the heat of the game), but after i opened the casing and placed a room fan right in front of it, the same error still happened although the temperature was 56 Celcius (my other AMD machine worked fine at 58 - 59 Celcius)

I've turned off the auto restart but haven't got the BSOD yet, and i haven't run memtest because i can't find a diskette (can i run memtest from a CD? and how?). This problem is really getting into my nerve so any help is deeply appreciated.

In event viewer, with every crash there is an error saying :
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 8/18/2005
Time: 2:02:41 AM
User: N/A
Computer: BIGZ
Description:
Error code 10000050, parameter1 87603858, parameter2 00000000, parameter3 805644ba, 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 38 37 eters 87
0030: 36 30 33 38 35 38 2c 20 603858,
0038: 30 30 30 30 30 30 30 30 00000000
0040: 2c 20 38 30 35 36 34 34 , 805644
0048: 62 61 2c 20 30 30 30 30 ba, 0000
0050: 30 30 30 30 0000

But i noticed with every crash, the error code and the parameter can be different, the other error is:
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 8/17/2005
Time: 5:44:43 PM
User: N/A
Computer: BIGZ
Description:
Error code 1000000a, parameter1 6f9373d0, parameter2 0000001c, parameter3 00000001, parameter4 806ecaa0.

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 36 66 eters 6f
0030: 39 33 37 33 64 30 2c 20 9373d0,
0038: 30 30 30 30 30 30 31 63 0000001c
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 31 2c 20 38 30 36 65 01, 806e
0050: 63 61 61 30 caa0

 

[Otmakus]

oh, i forgot, i've tried to swap my video card with another one from my old machine (which works fine for years now), and the same problem still happened. this machine is about half a year old, but i only used it as internet server before and everything worked well, so i only noticed this problem from maybe 2 months ago after i start to use this machine for gaming.

 

[cpc2004]

Hi Okmakus,

If you refer my previous post, this thread does not accept new problem as it has over 12 pages. Open a new post and I will reply to you.

 

[enciel]

hi cpc! ty for replying!! :bounce: um is there any possible solution in fixing this?will putting the RAM on another slot fix it?

 

[Reksio]

Same problem

Hi,
Ive got exactly the same problem. The only difference is that i was getting blue screens with no messages on them but once ive updated drivers for the realtek 97 audio card, a message appeared on the bs but i didnt manage to read it as my computer has restarted itself. Still it might be a hint.

My hardware config is:

AMD athlon 939 winchester 3000
AN8 Ultra Abit motherboard (1.6 bios)
Geil Ultra 1 gb dual channel ram
Sapphire Radeon x800 video
Realtek Audio 97

And here's some dumps:

 

[cpc2004]

If you refer my previous post, this thread does not accept new problem as it has over 12 pages. Open a new post and I will reply to you.

 

[Reksio]

I did open a new one. Ty in advance for your help. (Thread's title: "Error Caused by a Device Driver continued").

 

[cpc2004]

Here are my details from the BSOD I keep on getting. Please can you help me find the driver that is incorrect ?


Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 17/07/2005
Time: 17:12:08
User: N/A
Computer: PLAZMA
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000d1 (0x71a5df52, 0x00000002, 0x00000008, 0x71a5df52). A dump was saved in: C:\WINDOWS\Minidump\Mini071705-01.dmp.

Do you have any update of the problem? Your smptom is hardware error.

 

[icedark]

Hi,

I have the same problem, I quite frequently get BSOD's mostly once or twice a day. When I submit them to microsoft, I get the 'Error Caused By A Device Driver' response. About 75% of the time I get this BSOD while shutting down my computer. It also says that NDIS.sys is causing the problem or something. I have attatched 3 Minidumps that hopefully you could look at for me. I have ran tests on both of my sticks of RAM and they arent faulty.

Thanks,

icedark