Page Fault in Non Paged Area

Status
Not open for further replies.
cpc, i tested my RAM with MEMTEST 86. (i had ram installed backwards in two different slots for about a month). in slot one and two i get RAM error on test #5. In bank 3 which i havent touched until today, i have no errors at all and i let memtest run all night. does this mean bank 1 and 2(the two i installed ram in backwards) are fried? and that no errors on bank 3(the one i never touched til today) is the only unfried slot? does this indicate that i need a new mombo? does this mean that my ram is good? its just the pins on the mombo that are fried? if i buy the same exact mombo will my xp boot up normaly without me formating again? thanks in advance...
 
TrunkZ said:
as i mentioned in my post, i already updated the drivers to 61.77 but the problem still occurs but less frequently.
Click to expand...
Your timestamp of your nv4_disp.dll is not 61.77
The timestamp of version 61.77
nv4_disp.dll Tue Jul 13 08:23:35 2004 (40F32B87)
Re-install nVidia DIsplay card driver version 61.77 or buy a ATI video display card.
 
dae_amp_ika_dtp said:
cpc, i tested my RAM with MEMTEST 86. (i had ram installed backwards in two different slots for about a month). in slot one and two i get RAM error on test #5. In bank 3 which i havent touched until today, i have no errors at all and i let memtest run all night. does this mean bank 1 and 2(the two i installed ram in backwards) are fried? and that no errors on bank 3(the one i never touched til today) is the only unfried slot? does this indicate that i need a new mombo? does this mean that my ram is good? its just the pins on the mombo that are fried? if i buy the same exact mombo will my xp boot up normaly without me formating again? thanks in advance...
Click to expand...
I am not a hardware enginneer and you had better post your question to hardware forum. If the RAm cannot pass memtest, it is definitely RAM problem. Vice versa if the RAM pass memtest, it does not imply the ram is good because some faulty ram can pass memtest. Usually I prefer to swap the ram and diagnostic which memory stick is faulty.
 
I posted on this thread a long time ago and got some help from cpc2004 (which was helpful). But before I go any make any purchases, I want to get his or anyone else's opinion on some of my minidump results.

They seem to be all over the place, and from what I've heard, this could be hardware-related. I am thinking of purchasing a new PSU. Please try not to laugh, but the one I have now (that came with my system) is a 300W Power Man PSU. I read this thread: http://www.hardforum.com/showthread.php?t=792566 over on HardForum and it says that if a PSU doesn't have a website on it, it's probably welfare. Also I should point out that my exhaust fan (I'm not sure if this is the right name for it, but it's about the diameter of the PSU's fan and it's built-in to the case) is not spinning right now, and it wasn't spinning last week when I last opened up my case.

Also, my drwtsn32.log file is huge (45 MB). That is nothing to be proud of.

Anyway below are some copy and pasted lines from various minidumps.

Thanks for any help that you can offer.

atrice


2/5/05
BugCheck 10000050, {9f8046c7, 0, 9f8046c7, 0}
Probably caused by : win32k.sys ( win32k!dhpdevRetrieveLdev+32 )

4/29/05
BugCheck 10000050, {be801815, 0, be801815, 2}
Probably caused by : win32k.sys ( win32k!ValidateHandleSecure+58 )

5/14/05
BugCheck 24, {1902fe, f8a599b0, f8a596ac, f0444464}
Probably caused by : Ntfs.sys ( Ntfs!NtfsRemoveScb+88 )

5/28/05
BugCheck 10000050, {d8411af4, 0, d8411af4, 0}
Probably caused by : Ntfs.sys ( Ntfs!NtfsGetSizeForMappingPairs+65 )

6/4/05
BugCheck 24, {1902fe, f8a25adc, f8a257d8, d844441e}
Probably caused by : Ntfs.sys ( Ntfs!NtfsRemoveScb+88 )

6/11/05
BugCheck 10000050, {be801815, 0, be801815, 2}
Probably caused by : win32k.sys ( win32k!ValidateHandleSecure+58 )
 
Atrice,

Your DrWatson has 45MB and it is another evidence of hardware error. You should rename DrWatson log to another name. Zip the DrWatson log and attach here. Maybe I can find out the which hardware component is the culprit. If your fan is not spinning and the PSU is only 300W. It had better to replace them. Actually I am not sure which hardware component is the culprit hence I need your DrWatson log. If your DrWatson log have the hardware related NT status code, I can confirm which hardware component is faulty.
 
There have a lot of access violation at different application. Three entries fails with usual nt status codes. I believe that it is RAM problem.

Application exception occurred:
App: C:\Program Files\Mozilla Firefox\firefox.exe (pid=2988)
When: 5/25/2005 @ 00:39:47.312
Exception number: c000001d (illegal instruction)

Application exception occurred:
App: C:\WINDOWS\Explorer.EXE (pid=268)
When: 5/25/2005 @ 23:03:27.281
Exception number: 80000007

Application exception occurred:
App: T:\Program Files\Sierra\SWAT 4\Content\System\Swat4.exe (pid=3388)
When: 5/31/2005 @ 11:22:30.703
Exception number: c0000096 (privileged instruction)
 
I will try running the system with one stick of memory at a time after the next crash. Thank you for the help.

Also, does the Windows Event Viewer help in situations such as these? It creates an entry every time the system crashes, and the descriptions are something lke this:

Error code 10000050, parameter1 be801815, parameter2 00000000, parameter3 be801815, parameter4 00000002.

The Microsoft Help and Support Center says that the Symbolic Name is: ER_KRNLCRASH_LOG.

I usually look at the Event Viewer after a major crash, but I don't know if it's showing anything useful.
 
Need help yet

Please, I need some help. I have posted some messages before, about my problem. My computer is rebooting from time to time and I don't know why. I have tried all the sugestions until now but no there is no solution. cpc told me to test ram and I tried. I used mem386+, 7 times (run) and I found just one error. I removed that ram (512MB). I have used mem386+ again and I have found no erros, but the pc is still rebooting. It is driving me crazy... My work depends on it...
Please, look at the minidumps attached and, please, give some help...
 
Some information... again

Tks, cpc2004, for your kindness and attention.

BTW, please, I need some help (urgent).
I am still having problems with some unexpected restarts in my system.

Basics: Win XP, MB ASUS P4S333, P4 1.6 MHz, 1 GB RAM, Nvidia MX440, an so on, as many I have seen here...
I tried some nvidia display drivers (the last of them, for example). Now, I am using the 61.77, as some advices in here. Nothing seems to help...

Another facts: recently, I installed a new HD, Samsung SP1604N, 160 GB. After that, I have made a fresh installation of Win XP Pro plus all security updates, plus SP1 (but not sp2 - I prefer to wait sometime...).
Well, after that I have two problems now: sometimes, the video monitor goes into standby mode while I'm using the computer. Then, the cpu appears to be
halted until restart (unexpected or forced).

In another times, the video monitor goes into standby mode while I'm using the computer, but it restarts alone and unexpected. I have changed the log from dump to minidump and the problem apparently has gone (I am saying: the problem linked to the monitor going to standby mode alone and then restarts).

But the cpu is restarting from time to time, generating minidumps like the ones you have studied. A lot of minidumps... so many reboots!!!

Then, I ask: do you think the "restarting problem" could be linked to ram problems, to the new 160 GB HD or some hardware else?

I have tested the memory sticks (using mem386+): using the more accurate settings, I have found an error in one of the sticks. I have removed that stick (512 MB). The other two sticks (256MB x 2) show no errors. But the reboots still go on... No solution yet.

Do you think the problems should be linked to ram? Incompabilities?

In the first times, I thought that it was the video card, but than I changed it, and the problem is still ocurring. Than I tested the memory with the Microsoft Crash Analysys test, and it found no errors, as I said. And the monitor going to standby mode alone and not returning back until forced restart sometimes has ocurred before the new HD...

Well, that is the situation. Can you help me please?

***I need help asap***.
My work depends on that and it is being delayed beyond the reasonable...

Some minidumps are in the message before that one.

Tks for all.
 
Some more info (power font)

BTW, I have changed the power font (power supply), iniside the computer, just to see if this change could help. No, no help. Reboots... more reboots...
Tks for all, in advance.
 
2 minidumps have memory corruption 1 minidump has invalid call. They are symptoms of faulty motherborad or CPU. According to my experience, 80% is faulty M/B and 20% is faulty CPU.

Mini061005-03.dmp
BugCheck 10000050, {bf7fc94c, 0, bf7fc94c, 0}
Probably caused by : hardware
*** Possible invalid call from bf81c595 ( win32k!EngLpkInstalled+0x2d16 )
*** Expected target bf800d5a ( win32k+0xd5a )

Mini061405-01.dmp
BugCheck 1000007F, {8, 80042000, 0, 0}
Probably caused by : memory_corruption
CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
31 errors : !nt (804dd907-804dd9ff)
804dd900 db 89 7d 2c 0f 23 fb *00 8b 3d 20 00 00 00 8b *c9 ..},.#...= .....
804dd910 f8 02 00 00 8b 8f fc *00 00 00 0f 23 c3 0f 23 *0f ...........#..#.
804dd920 8b 9f 00 03 00 00 8b *24 04 03 00 00 0f 23 d3 *23 .......$.....#.#
804dd930 23 d9 8b 9f 08 03 00 00 8b 8f 0c 03 00 00 0f *04 #...............
804dd940 f3 0f 23 f9 eb 78 8b *0d 8b 85 84 00 00 00 8b *45 ..#..x.........E
804dd950 88 00 00 00 8b 4d 7c *1d 95 80 00 00 00 66 89 *04 .....M|......f..
804dd960 50 66 89 5d 30 66 89 *41 34 66 89 55 38 eb 41 *00 Pf.]0f.A4f.U8.A.
804dd970 66 c7 44 24 02 00 00 *00 53 56 57 0f a0 bb 30 *9d f.D$....SVW...0.
804dd980 00 00 66 8e e3 64 8b *66 00 00 00 00 53 83 ec *8e ..f..d.f....S...
804dd990 50 51 52 1e 06 0f a8 *c4 b8 23 00 83 ec 30 66 *98 PQR......#...0f.
804dd9a0 d8 66 8e c0 8b ec f7 *1d 24 70 00 00 02 00 75 *3d .f......$p....u=
804dd9b0 fc f6 05 50 f0 df ff *24 0f 85 0a ff ff ff 83 *00 ...P...$........
804dd9c0 54 f0 df ff 00 0f 85 *00 01 00 00 8b c4 2b 05 *a1 T............+..
804dd9d0 f0 df ff 05 8c 00 00 *01 74 15 83 f8 90 72 10 *0f ........t....r..
804dd9e0 18 f0 df ff 0b c0 7e *f0 e8 3d dd ff ff 8d 09 *fb ......~..=......
804dd9f0 20 d7 80 3d 91 51 54 *00 00 0f 85 92 fe ff ff *00 ..=.QT.........

MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
STACK_COMMAND: kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
BUCKET_ID: MEMORY_CORRUPTION_STRIDE


Mini061005-01.dmp
BugCheck 1000008E, {c000001d, 804dd970, f4a57d54, 0}
Probably caused by : memory_corruption

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
59 errors : !nt (804dd900-804dd97b)
804dd900 *d8 *02 *00 *00 0f 23 fb 64 *00 *00 *0f *23 00 00 8b 9f .....#.d...#....
804dd910 *89 *9b 00 *03 8b 8f fc 02 *04 *03 *00 *00 c3 0f 23 c9 ..............#.
804dd920 *23 *d9 *ab *9f 00 00 8b 8f *8b *8f *0c *03 0f 23 d3 0f #............#..
804dd930 *54 *b0 *00 *83 08 03 00 00 *01 *00 *00 *8b 00 00 0f 23 T..............#
804dd940 *88 *00 *00 *00 eb 78 8b ff *95 *80 *00 00 00 00 8b 9d .....x..........
804dd950 *00 00 *66 *8e 8b 4d 7c 8b *00 *00 00 00 00 66 89 45 ..f..M|......f.E
804dd960 *66 *c7 *44 *24 30 66 89 4d *53 *56 *57 *0f 38 eb 41 90 f.D$0f.MSVW.8.A.
804dd970 *f0 *0b *01 *f9 02 00 00 55 *8b *85 *84 *00 a0 bb 30 00 .......U......0.

MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
BUCKET_ID: MEMORY_CORRUPTION_STRIDE
 
hello!
i'm new in forum..

I have a problem, with my PC with XP SP2
randomly BSOD with following words:

PFN_LIST_CORRUPTED
0x0000004E (0x0000008F, 0x0003DBFF, 0x0003DBFE, 0x00000000)

BSOD is appear, only when i enabling the Cool and Quiet A64 function in the BIOS.
i have the latest BIOS for my motherboard (1.7)
running the memtest86 same time, and every result 100% pass the tests.
complete (default) test twice, test No. 5 about a hour and Test No. 9 three times..

sorry my bad english..

the dump files attached.

- Debilon -
 
Hi Debelion,

This is memory corruption and I believe that it is faulty RAM or faulty cache memory of the CPU. It is no need to run the memtest as memtest cannot report the whether it is RAM or cache memory problem. Reseat the memory to new memory slot. If the problem still exist, take out a memory stick. If the problem still occurs, it is cache memory of the CPU.

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000008f, The free or zeroed page listhead is corrupt
Arg2: 00035ff7, new page
Arg3: 00035ff6, old page
Arg4: 00000000, 0

Debugging Details:
------------------

PFN_PAGE_SINGLE_BIT_ERROR: Bugcheck args 2 and 3 differ by a bit, its hardware error.

MEMORY_CORRUPTOR: ONE_BIT
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
 
Hello cpc2004!

thanks the quick answer!

this is a strange thing to me, because hangup my PC, just when C'n'Q enabled. any other state is work correctly and stable through hours and hours..

hm..weak PSU don't caused this error?
because my PSU is a Chieftec 300W unit.
the +12 V rail only 13A..

but i have a new dump file, BSOD with MEMORY_MANAGEMENT error
0x0000001A (0x00041785, 0xC0E00000, 0x000307B6, 0x00000000)

- Debilon -
 
Your new minidump also have working set list is corrupt which is another evidence of memory corruption.


MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041785, The working set list is corrupt.
Arg2: c0e00000
Arg3: 000307b6
Arg4: 00000000
 
Some questions (in reply to cpc2004)

Hello, cpc2004, thanks for your help.

Your new reply told me that:"2 minidumps have memory corruption 1 minidump has invalid call. They are symptoms of faulty motherborad or CPU. According to my experience, 80% is faulty M/B and 20% is faulty CPU."

Now, I would like to change some info: yesterday, I have removed all the memory sticks (I had 512MB+256MB+256MB). After that, I put back just one of them: 256 MB. From that time until now, I had no more reboots. 24 hours have gone ok.
Just to do some "hardware stress", I have made a fresh win xp install, some softwares, I have ran some antivirus scan (just to access the hd´s),
I have copied several archives, from hd to hd, using some other softwares... and it seems to be ok. No unexpected reboots yet. Until now...

Then, I ask 3 questions: 1) could be all the problems related to some faulty ram? Even "memory corruption" and "invalid call", as you have pointed?
2) If yes, may my MB and CPU be ok?
3) If yes, I think (and I hope) the problems could be solved just removing all memories and buying new ram.Tks for your kindness and attention.

Tks for your kindness.
 
cpc2004 said:
Your new minidump also have working set list is corrupt which is another evidence of memory corruption.
Click to expand...

thanks!
i now probe the memory modules swap and use other dimm slots..
now dimm1 and dimm3 slots are memory sticks.

i probe the memory sticks in my friend PC, and absolute error free.. :mad: or :bounce: i don't decide this..

now i have this dump file, it was after win32k.sys error..
0x0000008E (0xC0000005, 0xBF801872, 0xAA86ACBC, 0X00000000)

can you see this last dump file..and my drwatson's log?:(

IMPORTANT! my DrWatson log language is hungarian..maybe not wrong..

My DrWatson log file
 
Help - Page fault in non paged area

Hi,

I just joined this forum in the hopes that someone can give me a clue what's going on. A little background....

The PC only seems to crash when stressed. I have 4 internal SCSI disks, they are mirrored (via Windows 2000 disk management). Every time the PC crashes, the disks must re-sync which goes on for about an hour. Sometimes, it can't get through that even though I run nothing while doing it. In other times, it happens while doing something graphic like running Photoshop.

It tanks with one of two errors:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xb111b000, 0x00000001, 0x80463693, 0x00000000). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\MEMORY.DMP.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000002c, 0x00000002, 0x00000000, 0x80444148). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\MEMORY.DMP.

I am suspecting memory here as this machine started acting kinda similar a year ago...I replaced the memory and all was well...but realize this could be caused by any number of problems.

I've attached a minidump... if anyone could look at it and tell me what it says, I'd be most appreciative!

Patti
 
pattir7 said:
Hi,

I just joined this forum in the hopes that someone can give me a clue what's going on. A little background....

The PC only seems to crash when stressed. I have 4 internal SCSI disks, they are mirrored (via Windows 2000 disk management). Every time the PC crashes, the disks must re-sync which goes on for about an hour. Sometimes, it can't get through that even though I run nothing while doing it. In other times, it happens while doing something graphic like running Photoshop.

It tanks with one of two errors:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xb111b000, 0x00000001, 0x80463693, 0x00000000). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\MEMORY.DMP.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000002c, 0x00000002, 0x00000000, 0x80444148). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\MEMORY.DMP.

I am suspecting memory here as this machine started acting kinda similar a year ago...I replaced the memory and all was well...but realize this could be caused by any number of problems.

I've attached a minidump... if anyone could look at it and tell me what it says, I'd be most appreciative!

Patti
Click to expand...
Your nVidia Display card driver is incompatible with SP2. Install http://www.nvidia.com/object/winxp_2k_61.77.html
 
How do you know?

Hi,

Thanks for the quick response. How do you know? Is there something in the minidump file that points to it? Could you possibly post what the minidump deciphers to?

I only ask because the PC had been running fine with this driver for about a year....and now all of a sudden, it is unstable.

Thanks so much!

Patti
 
Pattir7,

You only attached a minidump here and the nVidia Display card driver is the known issue that I find from your dump. Refer this webpage starting at page 3 to page 8 and there have a lot of problem relating to nVidia Display card driver. If you can provide more information, I will have more finding. Don't expect one 90K minidump have the solution. Usually you have to provide 6 to 8 minidumps for trouble shooting.

cpc2004.
 
Error while formatting

OK i am getting really wierd errors.

When i try to format i either get the "page fault in non paged area" error or a "Irq not less or equal to" error.

The computer was working fine before i formatted it tho i did notice on anonamly that when i went to back up some data by putting the HDD in another computer i could not access "my documents" folder in one of the user accounts.

ANY help is greatly appreciated.
 
I've been having restart problems for awhile. Before, I just repaired the installation of windows and everything was fine. Now, I'm getting STOP error 000...50. It's a PAGE_FAULT_IN_NON_PAGED_AREA, being caused by a missing or corrupted ntfs.sys. I bought new RAM and installed it, no dice. I try to run the recovery console, but as soon as the console starts, I bluescreen to the STOP 000...50. I can't load windows, period, and I can't even reinstall or repair the installation. Is my computer being so overworked at startup that it shuts down like this? Is my power supply insufficient? Is my harddrive toast? I honestly have no idea what to do next. Any help would be greatly appreciated.
 
Hello, cpc 2004

Hello, I have posted this message https://www.techspot.com/vb/post160130-267.html, after your message below and I would like to know your opinion about the problem.

Thanks for all.


cpc2004 said:
2 minidumps have memory corruption 1 minidump has invalid call. They are symptoms of faulty motherborad or CPU. According to my experience, 80% is faulty M/B and 20% is faulty CPU.

Mini061005-03.dmp
BugCheck 10000050, {bf7fc94c, 0, bf7fc94c, 0}
Probably caused by : hardware
*** Possible invalid call from bf81c595 ( win32k!EngLpkInstalled+0x2d16 )
*** Expected target bf800d5a ( win32k+0xd5a )

Mini061405-01.dmp
BugCheck 1000007F, {8, 80042000, 0, 0}
Probably caused by : memory_corruption
CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
31 errors : !nt (804dd907-804dd9ff)
804dd900 db 89 7d 2c 0f 23 fb *00 8b 3d 20 00 00 00 8b *c9 ..},.#...= .....
804dd910 f8 02 00 00 8b 8f fc *00 00 00 0f 23 c3 0f 23 *0f ...........#..#.
804dd920 8b 9f 00 03 00 00 8b *24 04 03 00 00 0f 23 d3 *23 .......$.....#.#
804dd930 23 d9 8b 9f 08 03 00 00 8b 8f 0c 03 00 00 0f *04 #...............
804dd940 f3 0f 23 f9 eb 78 8b *0d 8b 85 84 00 00 00 8b *45 ..#..x.........E
804dd950 88 00 00 00 8b 4d 7c *1d 95 80 00 00 00 66 89 *04 .....M|......f..
804dd960 50 66 89 5d 30 66 89 *41 34 66 89 55 38 eb 41 *00 Pf.]0f.A4f.U8.A.
804dd970 66 c7 44 24 02 00 00 *00 53 56 57 0f a0 bb 30 *9d f.D$....SVW...0.
804dd980 00 00 66 8e e3 64 8b *66 00 00 00 00 53 83 ec *8e ..f..d.f....S...
804dd990 50 51 52 1e 06 0f a8 *c4 b8 23 00 83 ec 30 66 *98 PQR......#...0f.
804dd9a0 d8 66 8e c0 8b ec f7 *1d 24 70 00 00 02 00 75 *3d .f......$p....u=
804dd9b0 fc f6 05 50 f0 df ff *24 0f 85 0a ff ff ff 83 *00 ...P...$........
804dd9c0 54 f0 df ff 00 0f 85 *00 01 00 00 8b c4 2b 05 *a1 T............+..
804dd9d0 f0 df ff 05 8c 00 00 *01 74 15 83 f8 90 72 10 *0f ........t....r..
804dd9e0 18 f0 df ff 0b c0 7e *f0 e8 3d dd ff ff 8d 09 *fb ......~..=......
804dd9f0 20 d7 80 3d 91 51 54 *00 00 0f 85 92 fe ff ff *00 ..=.QT.........

MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
STACK_COMMAND: kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
BUCKET_ID: MEMORY_CORRUPTION_STRIDE


Mini061005-01.dmp
BugCheck 1000008E, {c000001d, 804dd970, f4a57d54, 0}
Probably caused by : memory_corruption

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
59 errors : !nt (804dd900-804dd97b)
804dd900 *d8 *02 *00 *00 0f 23 fb 64 *00 *00 *0f *23 00 00 8b 9f .....#.d...#....
804dd910 *89 *9b 00 *03 8b 8f fc 02 *04 *03 *00 *00 c3 0f 23 c9 ..............#.
804dd920 *23 *d9 *ab *9f 00 00 8b 8f *8b *8f *0c *03 0f 23 d3 0f #............#..
804dd930 *54 *b0 *00 *83 08 03 00 00 *01 *00 *00 *8b 00 00 0f 23 T..............#
804dd940 *88 *00 *00 *00 eb 78 8b ff *95 *80 *00 00 00 00 8b 9d .....x..........
804dd950 *00 00 *66 *8e 8b 4d 7c 8b *00 *00 00 00 00 66 89 45 ..f..M|......f.E
804dd960 *66 *c7 *44 *24 30 66 89 4d *53 *56 *57 *0f 38 eb 41 90 f.D$0f.MSVW.8.A.
804dd970 *f0 *0b *01 *f9 02 00 00 55 *8b *85 *84 *00 a0 bb 30 00 .......U......0.

MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
BUCKET_ID: MEMORY_CORRUPTION_STRIDE
Click to expand...
 
Status
Not open for further replies.

Similar threads

M
Front Page Cache Issues?
Replies
13
Views
548
BbN48
B
AGenericFool
Help - Valid Windows 10 Licenses deactivate after two days?!
Replies
1
Views
365
Nelson28
N
J
The machine starts with no screen signal
Replies
1
Views
590
bazz2004
B

Latest posts

Back