Sign in with
Sign up | Sign in
Your question

In need of real, sincere quickfire help for random BSODs striking my XP Home OS

Tags:
  • MemTest
  • Drivers
  • BlueScreenView
  • Desktops
  • Hard Drives
  • IDE
  • Service Pack 3
  • Crash
  • SATA
  • RAM
  • X64
  • Windows XP
  • Notebooks
  • x86
  • Windows
  • Blue Screen
  • WhoCrashed
  • Random
  • Freeze
  • Hang-ups
  • MiniDumps
Last response: in Windows XP
Share
September 11, 2014 10:56:25 PM

I had encountered a spine-tingling BSOD today, but would also like to draw your attention to the annoying fact that a couple of BSODs had already occurred in July 2014 as well. It all seems to be pretty random [If I remember carefully, the BSODs might have all occurred when I was muting and unmuting sound during web surfing, but I again muted and unmuted sound while browsing a while back, and did not have any luck for reproducing the BSODs]. Note that my OS is XP Home Service Pack 3 having the latest versions of all necessary drivers installed. I had installed XP probably in April 2014, and for the first 3 months, it did not give me any headaches relating to the nasty BSODs.

It's a matter of serious concern. Kindly take a close look at what the popular BSOD diagonistic software, WhoCrashed, had to make of my three BSOD errors [2 in July, none in August, and 1 today]. You may be able to find that these 3 errors are cognate in the sense that all of them point to the ntoskrnl.exe module, and all the errors have been titled MEMORY_MANAGEMENT.

[1] BSOD error of today:

This was probably caused by the following module: ntoskrnl.exe (nt+0x22F33)
Bugcheck code: 0x1A (0x41284, 0x7002001, 0x3A11D, 0xFFFFFFFFC0883000)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

[2] BSOD error in the first part of July 2014

This was probably caused by the following module: ntoskrnl.exe (nt+0x22F33)
Bugcheck code: 0x1A (0x41284, 0xA9C0001, 0x3E19F, 0xFFFFFFFFC0883000)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

[3] BSOD in the last part of July 2014

This was probably caused by the following module: ntoskrnl.exe (nt+0x22F33)
Bugcheck code: 0x1A (0x41284, 0xD668001, 0xA292, 0xFFFFFFFFC0883000)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

More about : real sincere quickfire random bsods striking home

a b \ Driver
September 11, 2014 11:04:01 PM

Run memtest86. I bet your ram is faulty eg not in right slots, not properly in slots, incompatible with mobo, etc etc
m
0
l
September 11, 2014 11:24:00 PM

I'm curious: why did you install XP right when support for it officially ended?

it might also be that the latest drivers that you installed are not compatible with Windows XP since you're not supposed to have it any longer either
m
0
l
September 12, 2014 1:45:36 PM

i7Baby said:
Run memtest86. I bet your ram is faulty eg not in right slots, not properly in slots, incompatible with mobo, etc etc


I am using a notebook, and had not touched my RAM sticks for over 2 years now. It may be a RAM issue, but I am afraid to touch my RAM sticks. Also, I believe running Memtest86 could damage healthy RAM. Suggest a other solution.
m
0
l
September 12, 2014 1:50:44 PM

Entomber said:
I'm curious: why did you install XP right when support for it officially ended?

it might also be that the latest drivers that you installed are not compatible with Windows XP since you're not supposed to have it any longer either


How can the latest drivers not be compatible with XP? I was given the option to choose either from Windows 7 or Windows XP while downloading drivers from my laptop manufacturer's official website. I am damn sure that I had selected the XP-specific drivers and they installed on my system without a hitch.

If possible, I would install Windows 7 later to check if it's a XP-only issue. But, I feel that Windows 7 is a bogus when compared with XP.

m
0
l
September 12, 2014 2:07:20 PM

Hotserena said:
i7Baby said:
Run memtest86. I bet your ram is faulty eg not in right slots, not properly in slots, incompatible with mobo, etc etc


I am using a notebook, and had not touched my RAM sticks for over 2 years now. It may be a RAM issue, but I am afraid to touch my RAM sticks. Also, I believe running Memtest86 could damage healthy RAM. Suggest a other solution.


Look, your BSOD error codes indicate faulty RAM. We asked you to run a check on your RAM to see if it is good or not, and you refused. What else are we supposed to do?

Why do you think memtest damages RAM? Do you also believe that going to the doctor to get a checkup will cause you to get sick?
m
0
l
a b \ Driver
September 12, 2014 3:31:57 PM

All I can do is offer advice. You don't want to take it then you're on your own.
m
0
l
!