I too was having the same problem with my computer crashing and then I would receive an error message that the error was caused by a device driver.
I spent many hours with the MS Support staff and one person that I was working with told me that the same thing had happened to him recently and here is the fix that he stumbled into;
Make sure that your RAM memory sticks are properly installed and in their slots tightly.
I checked mine, they were loose and BINGO = problem solved.
This may not be your problem but I would suggest trying it.
Good luck !
Dave Kousgaard
402-554-1965

Thanks for the tip, I have checked that a long time ago.

Hi CPC, it looks like the PSU was bad after all. I had it replaced with a new one, and the comp has been running for more than 24 hours straight with no errors whatsoever, which had never happened before.

Thanks for all ur help, it's only after u said that my problem might be caused by more than one culprit that i started to re examine everything again, and it turned out that both my memory sticks and my PSU were bad. It's really difficult to single out the culprit when there are more than one.

Oh, and for Wizkid, this kind of errors can be caused by many things (sometimes by more than one thing, like what happened to me), if u can, try to swap ur PSU, ur memory sticks, and ur processor (actually, because of this problem, i've replaced virtually everything in my comp except my HD, casing, optical drive and video card). As CPC once said to me, this problem is mainly caused by faulty memory, but it can mean the processor cache memory or the M/B too, although it's usually caused by bad RAM.

Have u tried running memtest on each of your memory stick? Sometimes each stick, although from the same brand with the same type, can work at different latency (One of mine works at 2,5, while the other at 3). They work fine if used separately, but can generate unpredictable errors if used together (even more so at dual channel). U can see the latency time on the memtest display.

Have u ever got different kind of errors with ur computer, i mean different than the usual "error caused by a device driver" one? If u have, then maybe it's caused by something else, maybe a bad PSU.

PS: 4X video card works just fine in 8X supported M/B. If u want to be sure, read ur M/B manual, they usually give u a warning about the types of video card NOT to use (usually 2X, very old video cards)

Good Luck, i know u'll need that

I have had this problem for a very long time. I do not play games anymore because I'd only annoy myself.

I have checked a lot of things so far, ran dozens of tools...

I'll more than likely buy a Kingston RAM tomorrow, and see if the problem goes away. If it isn't, I'll get a new PSU, and so on, until I can find out what gave me the headaches all these months. My puter is an old one, so it is possible that every single element is faulty in it.

The error itself is always the same, and appears at random times (sometimes I can play half a day without any problem, sometimes it happens after 15 mins) during playing a 3D game (MoHAA, NOLF1+2 all had this kind of error). The monitor just seems to go into stand-by mode (screen goes black, led flashes green). Weird thing is I can still hear the sound (of me being killed ), but there is no way to get the monitor back in business. Only way is to reboot the whole machine.


Good Luck, i know u'll need that --- Thanks, tho luck has nothing to do with it anymore.

Happened again after switching RAM-positions.

Nothing in the event-log and no minidump.

Removed one of them RAMs.

cpc, does this shed any new light on the problem?

Wizkid,

If the ram is faulty, reseat the ram does not fix the BSOD. Diagnostic which memory stick is faulty. Have you try downclock the ram?

For off, thanks cpc for all your help. I've been reading these forums for a couple days now and you've helped solve a couple issues that have been plaguing me for months.

Ok, down to business. My company has several (15) new computers. Half of them take our image, half of them blue screen (see attached mini dumps).

We've been unable to find any hardware differences between each group and we've sent a couple to HP and HP SWEARS the memory is in working order (all 4GB of it).

Any help will be appreciated. Thanks!

Attached Files

Mini092805-06.zip (89.6 KB, 3 views)

Hi Jiffylueb,

You attached 4 minidumps and each are crashed with different symptom. It implies it is occurs randomly and it is symptom of hardware problem or storage overlaid by faulty device driver. In order to confirm whether it is hardware or software error, you must attach 7 7o 8 minidumps.

Mini092805-05.dmp is inaccesible by windbg and this is the symptom of faulty ram.

mini092905-01.dmp crashed at PC-Cillian. The root cause may be bad ram or software error at PC-Cillian.

mini092805-07.dmp crashed with stack is overlaid with 0x1023963.

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 7
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
LAST_CONTROL_TRANSFER: from 35350030 to 805344eb

STACK_TEXT:
b6256080 35350030 00000000 f7a50f78 00000000 nt!KiTrap0E+0x23
WARNING: Frame IP not in any known module. Following frames may be wrong.
b6256094 0707070d 2d070707 35353516 0d150a2a 0x35350030
b6256118 80514d19 f7a50f78 f7a50000 b6259ce4 0x707070d
f7a50f78 01023963 01024963 01025963 01026963 nt!MmAccessFault+0x5b
f7a50f8c 01028963 01029963 0102a963 0102b963 0x1023963
f7a50f90 01029963 0102a963 0102b963 0102c963 0x1028963
f7a50f94 0102a963 0102b963 0102c963 0102d963 0x1029963
f7a50f98 0102b963 0102c963 0102d963 0102e963 0x102a963
f7a50f9c 0102c963 0102d963 0102e963 0102f963 0x102b963
f7a50fa0 0102d963 0102e963 0102f963 01030963 0x102c963
f7a50fa4 0102e963 0102f963 01030963 01031963 0x102d963
f7a50fa8 0102f963 01030963 01031963 01032963 0x102e963
f7a50fac 01030963 01031963 01032963 01033963 0x102f963
f7a50fb0 01031963 01032963 01033963 01034963 0x1030963
f7a50fb4 01032963 01033963 01034963 01035963 0x1031963
f7a50fb8 01033963 01034963 01035963 01036963 0x1032963
f7a50fbc 01034963 01035963 01036963 01037963 0x1033963
f7a50fc0 01035963 01036963 01037963 01038963 0x1034963
f7a50fc4 01036963 01037963 01038963 01039963 0x1035963
f7a50fc8 01037963 01038963 01039963 0103a963 0x1036963
f7a50fcc 01038963 01039963 0103a963 0103b963 0x1037963
f7a50fd0 01039963 0103a963 0103b963 0103c963 0x1038963
f7a50fd4 0103a963 0103b963 0103c963 0103d963 0x1039963
f7a50fd8 0103b963 0103c963 0103d963 0103e963 0x103a963
f7a50fdc 0103c963 0103d963 0103e963 0103f963 0x103b963
f7a50fe0 0103d963 0103e963 0103f963 01040963 0x103c963
f7a50fe4 0103e963 0103f963 01040963 01041963 0x103d963
f7a50fe8 0103f963 01040963 01041963 01042963 0x103e963
f7a50fec 01040963 01041963 01042963 0003a163 0x103f963
f7a50ff0 01041963 01042963 0003a163 00000000 0x1040963
f7a50ff4 01042963 0003a163 00000000 00000000 0x1041963
f7a50ff8 0003a163 00000000 00000000 00000000 0x1042963
01042963 00000000 00000000 00000000 00000000 0x3a163

FOLLOWUP_IP:
nt!KiTrap0E+23
805344eb 1e push ds

SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KiTrap0E+23
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4178b6af
STACK_COMMAND: kb
FAILURE_BUCKET_ID: 0x7f_8_nt!KiTrap0E+23
BUCKET_ID: 0x7f_8_nt!KiTrap0E+23

mini09280-06.dmp maybe crashed by bad ram
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: f05c371c, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 804fff6a, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)

Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: f05c371c

FAULTING_IP:
nt!MiLocateAndReserveWsle+48
804fff6a 8b0c87 mov ecx,[edi+eax*4]

MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 6
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x50
LAST_CONTROL_TRANSFER: from 8050aed2 to 804fff6a

STACK_TEXT:
b565dc3c 8050aed2 89880fa0 c00003e8 8163fd90 nt!MiLocateAndReserveWsle+0x48
b565dc54 8050d01e 000fa110 c00003e8 8163fd90 nt!MiAddValidPageToWorkingSet+0x82
b565dc80 8050d300 000fa110 c00003e8 89880da8 nt!MiResolveTransitionFault+0x372
b565dcf8 8051599e 00000000 000fa110 c00003e8 nt!MiDispatchFault+0x100
b565dd4c 80534584 00000000 000fa110 00000001 nt!MmAccessFault+0xce0
b565dd4c 1001b470 00000000 000fa110 00000001 nt!KiTrap0E+0xbc
WARNING: Frame IP not in any known module. Following frames may be wrong.
02fe2e5c 00000000 00000000 00000000 00000000 0x1001b470

FOLLOWUP_IP:
nt!MiLocateAndReserveWsle+48
804fff6a 8b0c87 mov ecx,[edi+eax*4]

SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!MiLocateAndReserveWsle+48
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4178b6af
STACK_COMMAND: kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x50_nt!MiLocateAndReserveWsle+48
BUCKET_ID: 0x50_nt!MiLocateAndReserveWsle+48

Thanks for your quick response.

Here are 4 more minidumps

Attached Files

Mini092805-02.zip (79.5 KB, 1 views)

And 2 more again...

Attached Files

Mini092705-01.zip (74.6 KB, 1 views)

And 4 more just to be safe. There's another 20 or so in there just from the past week.

Attached Files

Mini092305-06.zip (95.5 KB, 2 views)

Hi Jiffylueb,

Are all the attached minidump from a PC or several PCs? After further investigation, the culprit is faulty ram unless it is random storage overlaid at windows control blocks by a faulty device driver.

As you know the minidump is only snapshot of the real memory when the crash occurs. If the storage overlaid occurs a few second before it crashes. If it is very hard to find out the culprit.

Finding
1) 3 more minidumps are inaccesible.
mini092605-01.dmp
mini092705-01.dmp
mini092305-07.dmp
You can raise a question to HP why the above minidumps are inacessible by windbg?

2) Mini092805-01.dmp is crashed at timer routine. Most probably it is caused by faulty ram
BugCheck 1000008E, {c0000005, bf8012e7, ba7dca58, 0}
Probably caused by : win32k.sys ( win32k!TimersProc+43 )

3) Mini092805-02.dmp is crashed with stack overflow. It may caused by software device driver. However it requires full memory to determine which process used up the kernel stack.

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffffb, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 804fff6a, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: fffffffb

FAULTING_IP:
nt!MiLocateAndReserveWsle+48
804fff6a 8b0c87 mov ecx,[edi+eax*4]

MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 804f9798 to 805f3881

EXCEPTION_RECORD: b5897d10 -- (.exr ffffffffb5897d10)
ExceptionAddress: 77f75dac
ExceptionCode: c00000fd (Stack overflow) <--- ??
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 0006bfe8

STACK_TEXT:
b5897940 804f9798 0006bfe8 000002cc 00000004 nt!ProbeForWrite+0x37
b5897cf4 80532259 b5897d10 00000000 b5897d64 nt!KiDispatchException+0x1aa
b5897d5c 8053220a 804d78e0 ffffffff b5776d8c nt!CommonDispatchException+0x4d
b5897d6c 805b4ed6 00000000 00000000 00000000 nt!KiExceptionExit+0x18a
b5897ddc 8053602a b07e3a52 896cf2a0 00000000 nt!PspTerminateThreadByPointer+0x50
b5897de8 00000000 0020027f 038b0000 023b123c nt!KiThreadStartup+0x16

FOLLOWUP_IP:
nt!MiLocateAndReserveWsle+48
804fff6a 8b0c87 mov ecx,[edi+eax*4]

SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!MiLocateAndReserveWsle+48
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4178b6af
STACK_COMMAND: .trap ffffffffb58978c8 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x50_nt!MiLocateAndReserveWsle+48
BUCKET_ID: 0x50_nt!MiLocateAndReserveWsle+48

All of minidumps are all on the same PC.

**EDIT**

Not sure if this will be of any help, but I was looking at the time stamp on each of the .dmp files. Seems most of the errors come within the same vicinity of one another. Once it happens once, it happens a couple more times all within 20 or 30 minutes after working fine all morning. For instance, on Sept 23rd, there were no errors until 12:10pm. Between that time and 2:37pm, there a total of 7 .dmp files. Then there were no more until the 24th...

Could it be a power supply or maybe the CPU is getting too hot? These are the machines we bought for our developers so I'm sure they experience high processor utilization. They have P4 3.0 HT processors, which should handle the .NET apps just fine but I could be wrong. At least the other half of the computers we bought are.

How many PCs have BSOD?

Out of the 15 we ordered, there's at least 5 of them that encounter it. Others are working along just fine with no issues whatsoever. Same image, same software loaded, same hardware. We ordered 7 and deployed those. Others said they wanted them, so we ordered 8 more. We've been trying to determine if HP updated the 2nd order somehow to make it different from the first but have been unable to do so. Can't find any difference yet. Could be a bad batch of RAM though.

Ordered new RAM & VGA today, I'll report on what happens.

Hi guys, i got the exact same problem as wizkid's and i solved it by replacing my PSU, but then another problem comes up. While the problem came up at random before (sometimes the screen just went black although the comp was almost idle), now it only came up when i was playing games, any games. In the middle of the game, the comp just freezed, showing no sign of life at all, sometimes i can play for hours before the comp freezed, but sometimes it's as early as a minute into the game.

There is no BSOD, no error in the event log, no minidump, the comp just freezed. I tried running memtest for a few hours, no errors. I tried using only one of the memory sticks, freeze. I tried using the other memory stick on different slot, freeze. I thought maybe it was the video card, so i replaced it with an older, working video card from my other comp, freeze. I formatted my system drive and reinstalled windows, freeze. I checked the temp, but it's fairly normal (at 57-58 C). I plan to replace the PSU again, because this kind of error didn't happen before i replaced it.

Oh, and at one of the errors, there is a beeeeeep.... sound with the freeze, so i thought it was bad RAM, but then i used the RAM one by one and the error still occured. Those 2 sticks of RAM are new ones, i claimed the warranty for the old ones and got them replaced (along with the M/B). Unless i can prove those RAM are faulty, i doubt i can get them replaced again. My M/B supports 400 DDR, and those 2 sticks of RAM are 400 DDR, i set the BIOS to automatically detect the RAM clock, and they're detected as 400.

edit: it's the PSU after all. I had it replaced and my computer worked perfectly these 24 hours without any problems whatsoever, whether i used it for gaming or for everything else.

I am yet another person to encounter this problem and would gladly appreciate anybodies help. Usually when i am trying to convert video or play video games my computer either restarts or i get "the blue screen of death" When i turn my computer back on i get the message that my computer has suffered from a serious error. I then get directed to the microsoft page telling me that it was caused by a device driver. I have tried:

- Installing all the latest updates and drivers
- Replacing RAM
- Replacing Video Card
- and Reinstalling Windows (Multiple times)

Please if anyone could help i would be very gratefull.

Attached Files

Minidumps (2).zip (65.7 KB, 2 views)

Hi Nachoman,

One of your minidump is inaccessible which is symptom of faulty ram. Maybe your ram is incompatible to the motherboard.

You can run memtest to stress the ram. If memtest reports the ram is faulty, ram is bad. However Memtest is not a perfect tool to test the memory as some faulty can pass memtest.

Suggestion
1. Reseat the memory stick to another memory slot
2. Downclock the ram
3. Clean the inside the computer case
4. Check the manul of your motherboard. 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, report the problem to microsoft to confirm whether it is faulty ram or not.