Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Random XP BSODs...


  • Please log in to reply

#1
philuk20

philuk20

    New Member

  • Member
  • Pip
  • 3 posts
Hey all thanks for checking out my post, I hope you can help
For quite a while now I have been recieving these random BSOD with various error reports I will list them below but I guess my system spec would be best first. (sorry if this in wrong place to post)

Spec:[/b
]
Operating System Microsoft Windows XP Professional
OS Service Pack Service Pack 2
CPU Type DualCore Intel Core 2 Duo E6750, 2666 MHz (8 x 333)
Motherboard Name Gigabyte GA-N650SLI-DS4 (3 PCI, 2 PCI-E x1, 2 PCI-E x16, 4 DDR2 DIMM, Audio, Gigabit LAN, IEEE-1394)
Motherboard Chipset nVIDIA nForce 650i SLI
System Memory 2048 MB (DDR2-800 DDR2 SDRAM)
DIMM1: Corsair XMS2 CM2X1024-6400C4 1 GB DDR2-800 DDR2 SDRAM (5-5-5-18 @ 400 MHz) (4-4-4-13 @ 270 MHz)
DIMM2: Corsair XMS2 CM2X1024-6400C4 1 GB DDR2-800 DDR2 SDRAM (5-5-5-18 @ 400 MHz) (4-4-4-13 @ 270 MHz)
Video Adapter NVIDIA GeForce 8800 GTS (320 MB)
Seagate Disk Drive ST3320620AS (320 GB, 7200 RPM, SATA-II)
Seagate Disk Drive ST3400820AS (400 GB, 7200 RPM, SATA-II)
PSU Hiper R series 580watt

(I can provide the full report from EVEREST, if needed)

Ok back to the probelm I have been getting these very random BSODs which seem to have no pattern to them, they usally vary in errors and dont happen at any specific time or point.
[b]BSODs

-STOP:0x0000001A (applied a windows update)
-Driver_IRQL_NOT_LESS_OR_EQUAL:0x000000D1 ( updated rtkhdaud.sys)
-0x0000007F
-STOP:0x0000008E (win32k.sys was mentioned with this bsod)

After seeing these I tried various tests, firstly was memtest86+ I ran this for 26 passes with no errors. So im not sure now if my RAM is faulty.
Using speedfan I seen that my CPU temps were pretty high (44-46c normal, 64-65c 100% load) I am planning to replace the current intel stock HSF. could overheating be the issue?
I also checked HDD using the speedfan SMART utility but again came back with "ok" results so that should not be a probelm. I have noticed that my HDD does make alot of noise (grinding, from time to time and once even a clicking sound).

So does anyone have any advice they could give or point me in the right direction to fixing this probelm? Any help is really appreciated!

Not sure if this is relevant but could be worth adding.
[Im not sure if this will help but speedfan does show some voltage information:
Vcore1: 1.14V Vcore2:1.94V +3.3V: 3.36V +5V: 4.89V +12v:0.45V
-12V: -16.97V -5v: -5.41V +5V: 5.16v Vbat: 3.10V]
  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Hello and welcome to GeeksToGo, Below I have found some information on the two errors you have provided:

0X0000001a MEMORY_MANAGEMENT is a type of Stop message or commonly known as a BSOD message. 0×0000001a usually occurs because of a race condition in the memory manager or sometimes caused by a defective memory or simply it is overheated.


STOP:0x0000008E is a device error
Now lets see what is causing both errors for sure. Two files I need you to download. Please download them in the order I give and post results of each as requested

Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloadedand run it
Put a tick in accept thenclick on next
Put a tick in the don't create a start menu folder then click next
Put a tick in create a desktop icon then click on install and make sure there is a tick in launch whocrashed before clicking finish
Click Analyze ...
It will want to download the debugger and install it...say yes...
WhoCrashed will create report...you have to scroll down to see it
Copy and paste it into your next reply...



Let's check your memory and make sure there is no issue with it.Donwload memtest86 from the link in my signature below.


Get the file that is named Download - The one you want is "Download - Pre-compiled Bootable ISO (.zip). When it downloads, it will be labeled "memtest86+2.11.iso.zip"
Unzip the file once you download it. You should have a .iso file in the unzipped directory.

if you don't have a burning program that will burn .ISO files get burncdcc in my signature below.

NOTE...do not put a blank cd in until burncdcc opens the tray for you
1. Start BurnCDCC
2. Browse to the ISO file you want to burn on cd/dvd ....in this case its memtest86.iso
3. Select the ISO file
4. click on Start

Make sure the bios is set for the cd drive as the first boot device
Put the cd in the cd drive and then boot your computer.

Running the Diagnostic Program:

The basic diagnostic screen has five main sections of relevant information. Three at the top which are labeled, PASS %, TEST %, and TEST #. This will basically show you the total progress of the current test, the overall progress of the diagnostic test, and the test number is currently performing.

On the middle left hand side of the of the program interface there is a “Wall Time” section that will keep track of how long the diagnostic test has been running for. This just gives you an idea if you are not attending the testing process.

The main section to look for is the lower half of the screen which is usually blank. As long as the memory testing is going ok with no errors this section of the screen should remain blank. If the diagnostic program finds any serious faults in the memory you will see it display a memory dump of address’s in this section. This is similar to what is displayed on your screen when you encounter a blue screen of death.

You now have most everything you need to know about setting up and testing your memory with diagnostic programs. This guide should help you get to the source of any intermittent problems related to your memory.


Run memtest for at least 2 hours
If it starts showing any errors during that time then you will have to replace the memory
If there are no errors after 2 hours press Esc and that will end the tests
We will then try other options
  • 0

#3
philuk20

philuk20

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts
Thanks for the reply. Here is my whocrashed report Crash dump directory:

Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


Too many crashes have been detected. Only the latest 40 crashes will be displayed.

On Fri 17/04/2009 09:22:26 your computer crashed
This was likely caused by the following module: tdi.sys
Bugcheck code: 0x1000000A (0x4215A000, 0x1C, 0x1, 0x804FCC8B)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\tdi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TDI Wrapper
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 17/04/2009 07:17:06 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007F (0x8, 0x80042000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 16/04/2009 19:05:51 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x1000008E (0xC000001D, 0xBF8288E2, 0xA953B7D0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware





On Tue 14/04/2009 23:35:41 your computer crashed
This was likely caused by the following module: vsdatant.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x0, 0xA8380C40, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\vsdatant.sys
product: TrueVector Device Driver
company: Check Point Software Technologies LTD
description: TrueVector Device Driver



On Fri 10/04/2009 18:27:14 your computer crashed
This was likely caused by the following module: nv4_mini.sys
Bugcheck code: 0x7F (0x0, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\WINDOWS\system32\drivers\nv4_mini.sys
product: NVIDIA Compatible Windows 2000 Miniport Driver, Version 180.48
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Miniport Driver, Version 180.48



On Fri 10/04/2009 00:01:50 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x100000D1 (0xDB65045D, 0x2, 0x1, 0xB3569523)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware





On Thu 09/04/2009 19:37:52 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x4128B, 0x3C7E2201, 0x0, 0xC0883000)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 09/04/2009 02:04:43 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x80525976, 0xA8D89B20, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 07/04/2009 23:02:54 your computer crashed
This was likely caused by the following module: tcpip.sys
Bugcheck code: 0x100000D1 (0x5AD140B, 0x2, 0x1, 0xAF1045FB)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Protocol Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 03/04/2009 20:20:29 your computer crashed
This was likely caused by the following module: nv4_mini.sys
Bugcheck code: 0x100000D1 (0x0, 0x2, 0x1, 0xB917A77F)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\nv4_mini.sys
product: NVIDIA Compatible Windows 2000 Miniport Driver, Version 180.48
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Miniport Driver, Version 180.48



On Thu 02/04/2009 23:29:06 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE58CC00C, 0x1, 0x8054AFD2, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 28/03/2009 23:11:04 your computer crashed
This was likely caused by the following module: afd.sys
Bugcheck code: 0x10000050 (0xF4E6D91A, 0x1, 0xABCD2A83, 0x2)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 26/03/2009 23:14:19 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0x9A8C62BC, 0x0, 0x8052347A, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 18/03/2009 20:42:15 your computer crashed
This was likely caused by the following module: vsdatant.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x8054A10D, 0xA9F30278, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\vsdatant.sys
product: TrueVector Device Driver
company: Check Point Software Technologies LTD
description: TrueVector Device Driver



On Mon 16/03/2009 15:09:09 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0x9C005F00, 0x0, 0x0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 15/03/2009 13:34:03 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x9664D00C, 0x2, 0x0, 0x80510C65)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 03/03/2009 16:19:48 your computer crashed
This was likely caused by the following module: nv4_disp.dll
Bugcheck code: 0x10000050 (0xE4324EF4, 0x1, 0xBFAA990F, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 180.48
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 180.48



On Sat 28/02/2009 21:21:16 your computer crashed
This was likely caused by the following module: memory_corruption
Bugcheck code: 0x4E (0x99, 0x0, 0x1, 0x0)
Error: PFN_LIST_CORRUPT
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on memory_corruption





On Sat 28/02/2009 03:35:17 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xFFFFFF60, 0x0, 0x8052591F, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 22/02/2009 00:11:20 your computer crashed
This was likely caused by the following module: rtkhdaud.sys
Bugcheck code: 0x100000D1 (0x300, 0x2, 0x0, 0xB4462CC2)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\rtkhdaud.sys
product: Realtek® High Definition Audio Function Driver (HRTF data Copyright 1994 by MIT Media Lab)
company: Realtek Semiconductor Corp.
description: Realtek® High Definition Audio Function Driver



On Tue 10/02/2009 23:10:08 your computer crashed
This was likely caused by the following module: nvenetfd.sys
Bugcheck code: 0x1000008E (0xC000001D, 0xBA4FCF40, 0x8055024C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\nvenetfd.sys
product: NVENETFD
company: NVIDIA Corporation
description: NVIDIA Networking Function Driver.



On Tue 10/02/2009 14:58:35 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0x51995C44, 0x1C, 0x1, 0x805021A8)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 06/02/2009 16:00:02 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1902FE, 0xA8CE4898, 0xA8CE4594, 0xBA50CEB8)
Error: NTFS_FILE_SYSTEM
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 02/02/2009 13:14:23 your computer crashed
This was likely caused by the following module: nv4_disp.dll
Bugcheck code: 0x1000007E (0xC0000005, 0xBFAF1F86, 0xA8B9CC3C, 0xA8B9C938)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 180.48
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 180.48



On Fri 30/01/2009 22:25:33 your computer crashed
This was likely caused by the following module: vsdatant.sys
Bugcheck code: 0x100000D1 (0x0, 0x2, 0x0, 0xB2739AB0)
Error: Unknown
file path: C:\WINDOWS\system32\vsdatant.sys
product: TrueVector Device Driver
company: Check Point Software Technologies LTD
description: TrueVector Device Driver



On Mon 26/01/2009 20:45:08 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x1000008E (0xC0000005, 0x8051C4EE, 0xAF12FAD8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware





On Tue 20/01/2009 22:34:20 your computer crashed
This was likely caused by the following module: nv4_disp.dll
Bugcheck code: 0x10000050 (0xE33CC218, 0x0, 0xBF9D8D67, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 180.48
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 180.48



On Tue 06/01/2009 14:51:01 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFFFFFE, 0x2, 0x0, 0x804F4672)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 30/12/2008 16:58:20 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xBF805487, 0xAAA9D85C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 29/12/2008 14:14:43 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x80, 0x1, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 28/12/2008 03:29:24 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xBF80193A, 0xB589EC44, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 23/12/2008 14:01:59 your computer crashed
This was likely caused by the following module: nv4_disp.dll
Bugcheck code: 0x10000050 (0xEB7D78E0, 0x0, 0xBFAF6920, 0x2)
Error: Unknown
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 180.48
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 180.48



On Sun 21/12/2008 04:13:52 your computer crashed
This was likely caused by the following module: nv4_disp.dll
Bugcheck code: 0x10000050 (0xB5CC1004, 0x0, 0xBFB19507, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 180.48
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 180.48



On Mon 08/12/2008 21:16:34 your computer crashed
This was likely caused by the following module: atapi.sys
Bugcheck code: 0x100000D1 (0x58, 0x5, 0x1, 0xBA5F7906)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 04/12/2008 01:01:47 your computer crashed
This was likely caused by the following module: kmixer.sys
Bugcheck code: 0x10000050 (0xEAEA7F21, 0x0, 0xACF1BCE7, 0x2)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\kmixer.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Audio Mixer
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Fri 21/11/2008 10:52:48 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x805143C8, 0xAC67BAD8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 19/11/2008 08:57:12 your computer crashed
This was likely caused by the following module: pnkbstrk.sys
Bugcheck code: 0x1000007F (0x8, 0x80042000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\drivers\pnkbstrk.sys



On Mon 17/11/2008 04:49:06 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000007F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 16/11/2008 01:13:57 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFD655C24, 0x0, 0x0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

129 crash dumps have been found on your computer. Only 39 have been analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


(sorry for the large amount of text, alot of errors :) )



As for memtest, I actually an this before for a total of 11 hours and getting 26 passes without any errors.
Once again thanks alot for you help, its really appreciated.
  • 0

#4
philuk20

philuk20

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts
Just another update, after running seatools DOS for my HDD they seem to have passed, but my hdd is still very nosiey :) Im not sure where to go now.
  • 0

#5
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
The errors you are showing are pointing to memory, cpu, or mb

Since memtest says everything is good then lets move on and check the mb




Disconnect everything from the Motherboard except

* keyboard
* mouse
* video output
* 20+4 powercable
* 4/8 pin 12v wire both coming from the powersupply,
* Cpu fan wire
* power and reset button to the case
*case speaker

Now you should have NOTHING connected to the motherboard except what was listed above.

The goal here is just to test the mobo:

If the computer still will not boot up the please remove the motherboard from the computer along with the power supply

place the motherboard on a piece of card board larger than the motherboard,

this will eliminate a short from the mobo to the case witch could be a possibility

Install the cpu with, 1 stick ram in dimm 1, power supply, video card, case switch and case speaker
Connect ps2 mouse and keyboard along with the monitor
Repeat the above and power on

If the computer now boots into bios you most likely had a case short so make sure when installing the motherboard in the case that you use standoffs and they line up with the mounting holes in the motherboard and none of the standoffs touch anything else on the underside of the board.


Thanks to Cbarnard for these instructions
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP