BSOD (random ones at random times) Windows 7

[Plasma Ecto]

I have a random BSOD issue. I thought I had fixed it but still having issues.

windows version: Windows 7 , 6.1, build: 7600
Hardware: ASUSTeK Computer INC., M2N-SLI
CPU: AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ AMD586
RAM: 4GB total

I recently installed Windows 7 home premium edition to a new hard drive. I was having issues with a small older drive, so I went with fresh install thinking it would fix my issues.

nope. New drive and new windows install and I still get BSOD at random times, and its not the same errors.



So I got a program to read what was causing crashes, Info below. ( not too good at forum formatting ether...) I also did the log dump program recommended on forums. its been attached.

Help? I have no clue as to why or what is going on anymore...I have read on these forums and googled my issue/error codes so much, with no solid fix. Its beyond frustrating.

On Wed 10/21/2015 11:37:43 PM GMT your computer crashed
This was probably caused by the following module: amdk8.sys (amdk8+0x1BB6)
Bugcheck code: 0xA (0x51, 0xFF, 0x1, 0xFFFFFFFF82E04BF2)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\amdk8.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 10/21/2015 11:37:43 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal+0x811D)
Bugcheck code: 0xA (0x51, 0xFF, 0x1, 0xFFFFFFFF82E04BF2)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL



On Wed 10/21/2015 10:12:21 PM GMT your computer crashed
This was probably caused by the following module: amdk8.sys (amdk8+0x1BB6)
Bugcheck code: 0xA (0x63, 0xFF, 0x1, 0xFFFFFFFF82E05BF2)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\amdk8.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.






On Wed 10/21/2015 9:34:04 PM GMT your computer crashed
This was probably caused by the following module: fileinfo.sys (fileinfo+0x712A)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8B33C12A, 0xFFFFFFFFA40FAB34, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 10/21/2015 9:10:55 PM GMT your computer crashed
This was probably caused by the following module: ntfs.sys (Ntfs+0x9C85E)
Bugcheck code: 0x50 (0xFFFFFFFF98D03AB8, 0x1, 0xFFFFFFFF8B4A185E, 0x1)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 10/21/2015 3:13:31 AM GMT your computer crashed
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
Bugcheck code: 0xA (0xFFFFFFFFC0005950, 0x0, 0x0, 0xFFFFFFFF826D4068)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Pauly]

Had a look through your dumps and all of them blame a various core windows driver for the crash, as this cannot truly be the cause then some further testing will be required
Initially I would run an sfc scan to check for any corruption within windows itself http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
Next I would run memtest to perform a thorough test of the RAM, preferably overnight for a minimum of 8 passes http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

I notice you have no windows updates installed, it would be good to get this done as missing SP1 means you are a long way behind

Depending on the outcome of these will determine what else needs to be done but as the problem has transcended to a new HDD & OS then more hardware testing is likely

 

[Plasma Ecto]

I have run the memtest, 2 or 3 times, all passes. I am running the sfc scan now.

I am unable to install updates for windows as the pc will crash or fail to reboot upon a restart. It will start bios, logo splash screen, and throw a BSOD and shut down.

I have swapped out or removed every component I can. I have tried different keyboard, mouse, video card, ram sticks, tested each one with and without. I still get a BSOD.

I think as you have, that windows install is corrupted somehow, yet this is a fresh install.. it has been doing this since before install.


I will post results of scan when I have them. Thank you !

 

[Plasma Ecto]

Scan completed - 100% complete
Windows resource protection did not find any integrity violations.




I am so baffled..

 

[Pauly]

Interesting indeed, from what you say I would assume it has to be a hardware problem with ram being the most likely culprit

Have you run memtest for 8 consecutive passes, if not then I would do this to double check all is ok
Other things I would do would be a bios update/bios reset to default settings, ensuring you have the correct sata mode selected ie ide or ahci depending on how you installed windows

It would be good if we could run more hardware tests but most require windows to be booted to run them, if you can get to a desktop try Prime95 and Furmark but be sure to closely monitor system temperatures during these tests with something like speccy as temps can rise fast !

 

[Plasma Ecto]

sorry it took so long to get back..
I did the tests and they ran fine. No errors.
While doing one test, pulling a ram stick out and testing remaining one, I did notice my CPU fan wasnt spinning very fast. Normally sounds like a wind turbine. ( I was taking photos of the ram sticks in slots, and had side of case open, wasnt actively removing anything while on)

I went into bios and noticed the RPM was around 850 on average. I just ordered a new fan/cooler setup for my motherboard. Cleaned and did housekeeping while in the case, dust, wire tidying etc.

I havent had any more BSOD since then. Would a fan that cant keep the cpu cool cause all my issues? my cpu sits right by one of the ram slots. ( bad or poor design in my opinion)


I have been watching for my BSOD tho... *fingers crossed* nothing so far.....

 

[Pauly]

Its possible, too much heat can never be a good thing
Let us know how you get on, any more BSODs then run the tool again and upload any new files