Error Caused by a Device Driver

Looks like your solution worked like a charm!

cpc2004,

Looks like it worked! :bounce: I moved the sole memory stick to another slot and so far it hasn't crashed all day. I'm *so* impressed. I sincerely appreciate your advice. This is much better than having to replace the memory or install a heatsink w/ball-bearing fan as I heard I might.

One suggestion I read is that if you think the RAM is overheating you can first try running the PC with its cover off (have to use caution inserting the power cord & monitor cables since you can easily wipe out the system with a static electricity shock). If the system performs better with the cover off, try
blowing out the dust nearby and seating the RAM in another slot further from the CPU and hot components.

I think it stinks that Microsoft keeps returning software errors for a hardware issue and sends their users all over the map trying to reload device drivers etc.

Thanks again for the hints,

Dawn P.

Hi, I am new here and recently started having similar problems as the one the topic starter has stated. On the BSOD it says stuff about a Physical Memory Dump. I would like to know if there is a solution to this problem even though it is not happening as much as it is used to. I would be glad to put up the dump files if you wish to check them. Thanks in advance

hey i hope this works would have replied earlier but been busy with exams..every time i try and attach the minidumps it never works...the upload page comes up as page unavailable when i try and upload them.

Hi Afi,

You cannot attach more than 100K for each attachment. Zip the dumps and re-attach the zip files here.

CPC2004, or anyone, I'm crashing too, here's the minidumps

Any help would be appreciated!

This problem has been ongoing for a couple of months, but I can't map it to any specific changes in hardware or configuration. It just reboots randomly. I've since disabled auto reboot per your instructions, so I should at least be able to see the bluescreen. I've attached some recent associated minidumps (1001)

Thanks!

Solomon

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.

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

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.

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.

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

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

Hi Afi,

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

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

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!!

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!

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.

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.

Hi BugHi,

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

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

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!