Finding a corrupted driver

[ShadeZeRO]

Finding a corrupted driver cpc please check out

hey, I was wondering, how would I go about trying to find a corrupted driver??

I have minidumps, and I a lack of knowledge in verifier.exe...

 

[ShadeZeRO]

I have several minidumps if you need them. I suppose they would help because all bsod are related to bad drivers.

 

[howard_hopkinso]

I have several minidumps if you need them. I suppose they would help because all bsod are related to bad drivers.

I`m sorry, but that is not always the case.

ShadeZeRO. Are you receiving any error messages? If so what do they say?

What exactly is happening when your computer crashes?

As much info as possible will help us to help you.

Regards Howard

 

[ShadeZeRO]

I`m sorry, but that is not always the case.

ShadeZeRO. Are you receiving any error messages? If so what do they say?

What exactly is happening when your computer crashes?

As much info as possible will help us to help you.

Regards Howard

Ok well, i get alot of 0x50, 0x8e, and other random bsod:

• IRQL_NOT_LESS_OR_EQUAL 0xA
• PAGE_FAULT_IN_NONPAGED_AREA 0x50
• PAGE_FAULT_IN_NONPAGED_AREA 0x50
• SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION 0xC1

Those are the main ones, and once in a while I get the 0x24, but thats once every long so often.

Full system specs (I mean FULL)

Case/PSU:
-ThermalTake VM3000 Skull Screwless Case (Black) w/ Fan Controller
-Aspire 550w PSU, Clear with Blue LED's
-Total 9 Fans in Case
**4: 35CFM 80mm Fans
**2: PSU Fans (Blue Led)
**1: VGA Fan
**1: Vantec Tornado CPU Cooler
**1: 35CFM Exhaust Blower

Essentials:
-AMD Athlon64 3400+ (1MB clawhammer)
**With Alpha Heatsink
**With Vantec Tornado 80mm Fan
**With Arctic Silver 5
-ASUS K8V SE Deluxe
-1GB Corsair XMS TwinX PC4400 DDR RAM
**With Platinum Heatspreaders

Audio/Video Cards:
-Sapphire X850XT Platinum Edition
**2-Slot Design
-Creative Sound Blaster Audigy 2 ZS Limited Gamer Edition

Optical Drives:
-16x Sony DVD-ROM
-52x/24x/52x Lite-On CD-RW
-16x NEC DVD +/- RW

Floppy Drives:
-Samsung 3.5" Floppy Drive

Hard Drives:
-120GB Seagate Barrecuda 7200.7 RPM SATA-150 *broke*
-250GB Western Digital Caviar 7200 RPM SATA-150
-80GB Western Digital Extrernal USB 2.0 w/ 80GB 7200RPM Caviar Drive

 

[howard_hopkinso]

Cpc2004 is the forum guru around here, when it comes to reading minidump files.

I`m sure he will take a look at your minidumps when he gets time.

The fact that you`re getting various bsod`s, could be due to faulty ram.

Test your ram using the Memtest86+ programme from www.memtest.org.

Let the programme run for at least seven passes. If you don`t have a floppy drive, there is a pre-built iso version, that you can burn to cd, and then boot from that.

Regards Howard

 

[ShadeZeRO]

I used memtest all night a few days ago, over 55 passes, 0 errors.

 

[howard_hopkinso]

Take a look at this article HERE

It shows you how to use the driver verifier to diagnose your drivers.

Regards Howard

 

[ShadeZeRO]

Thats what I used, tho, it helped with my cpu lag, but I still dont kinda undsterstand it..-_-

but for all I know it might be a hardware problem, i just dont know it, cuz i dont know what my minidumps mean.

CPC Please check :wave:

 

[howard_hopkinso]

The fact that your ram has passed memtest, doesn`t always mean that it`s not a ram problem.

Post some more minidumps, if you can, and wait for cpc2004, or send him a pm.

Regards Howard

 

[ShadeZeRO]

Ok, more mini dumps.

 

[cpc2004]

Hi

Everyday I receive 5 to 6 new cases. I have over 20 opened cases on hand. After investigation, the culprit is faulty ram. Some faulty ram can pass memtest.

The debug report of your problem
Mini092805-11.dmp 8E (c0000005, 805d6675, f55d0b84, 00000000) nt!RtlCompareUnicodeString+2b
Mini092805-12.dmp 0A (89bac548, 00000002, 00000001, 8051e129) nt!ProbeForWrite+0x39 -> nt!MiRemovePageByColor+8b
Mini092805-13.dmp 8E (c0000005, bf8029cd, b39216f8, 00000000) win32k!PhkFirstGlobalValid+16
Mini092905-01.dmp 0A (865ee7b8, 00000000, 805346ab, 00000000) nvcoafl51+f8f -> nt!ExRemoveHeadNBQueue+63
Mini092905-05.dmp 0A (8e292a74, 00000002, 00000001, 804ff3a6) USBPORT!USBPORT_DM_TimerDpc+20d -> nt!KiInsertTimerTable+4e
Mini092905-06.dmp 0A (8e24d2fc, 000000ff, 00000000, 8053196a) win32k!GreAcquireSemaphore+18 -> nt!ExAcquireResourceExclusiveLite+36
Mini092905-07.dmp 8E (c0000005, bfa22a17, b2572cc8, 00000000) ati2cqag+10a17
Mini092905-08.dmp 8E (c0000005, bf813756, ba13b248, 00000000) win32k!ESTROBJ::vCharPos_H3+15a

Suggestion
1. Reseat the memory stick to another memory slot
2. Downclock the ram
3. Clean the inside the computer case
4. Make sure that the ram is compatible to the motherboard
If it still crashes, diagnostic which memory stick is faulty
1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
2. If you have only one memory stick, replace the ram

 

[ShadeZeRO]

Thank you, I'm filing for RMA now at the corsair forums.

 

[cpc2004]

What is the meaning of RMA?

 

[ShadeZeRO]

I have a lifetime warrenty with my ram. I can send it back to the manufacturer anytime, and they will fix/replace the modules if they EVER messup. This process is RMA...

My ram used to be :hotbounce now its :hotouch: haha, i love the smilies here.

Is there a chance it could be my motherboard?

 

[howard_hopkinso]

What is the meaning of RMA?

RMA=Return Merchandise Authorization.

Is there a chance it could be my motherboard?

Unfortunately yes there is a chance that it`s your mobo.

However, hopefully it won`t be. Once you get the new ram I guess you`ll find out

Regards Howard

 

[cpc2004]

I have a lifetime warrenty with my ram. I can send it back to the manufacturer anytime, and they will fix/replace the modules if they EVER messup. This process is RMA...

My ram used to be :hotbounce now its :hotouch: haha, i love the smilies here.

Is there a chance it could be my motherboard?

Hi,

Some problem owners confirm the solution of their problem. Base upon my past record, over 90% of similar cases are faulty ram and no confirmed case is related to faulty motherboard for memory corruption. A few cases are reported to overheat or PSU. I hope you can report your solution after your problem is fixed.