Solved Constant and Random BSOD even after Reformat

Hello Guys, I'm getting BSODs even after I reformatted. It was the ntoskrnl.exe file that was giving me problems so I followed advice and just reformatted my computer. However the BSODs are still happening. Could someone help me please. I've attached my dmp files here.

Thanks in advance.

Welcome

I see no antivirus listed. Can you tell me what antivirus you're using?

I'll post suggestions after seeing your answer

Hello! Thanks for the reply. I am currently not using any anti-virus software yet.

Why not
Anyway, run this tool How to remove malware belonging to the family Rootkit.Win32.TDSS (aka Tidserv, TDSServ, Alureon)? let me know if it finds anything

Hey, I've done the scan but it shows no errors.:huh:

Alright


Your Ralink RT2870 series USB802.11n Wireless Adapter Driver needs to be updated.
Try getting it from here Driver Reference Table

Run the system file checker to repair any damaged files within windows:
:ar: http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Then run disk check:
:ar: http://www.sevenforums.com/tutorials/433-disk-check.html

Hard drive test both short and long with:
:ar: SeaTools for Windows

* Additional:

One of your dumps indicate memory corruption.

Check your ram for errors for 8 passes (overnight):
:ar: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

For the USBPORT.sys errors, go though the tutorial below for a possible fix:
:ar: http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html

Post back results

Hey, so I've done everything you ask me to do, all yielding no error messages. Except the ram test, which I did and now my windows can't load anymore :shock:. It also tells me it can't be repaired.

I did some checks and realized my BIOSTAR motherboard doesnt seem to support (at least they didn't list down in their list of rams) Crosair rams. Could that be a possible cause of my random BSOD?

My motherboard is the Biostar H61MLV and my rams at the Crosair 4gb DDR3 (x2)

Updated your network drivers?
Did you get any bsods?

Hey yes i did. I followed all the steps above. So, I just reformatted my computer, checked my hard disk for any bad sectors and It all was clean. Nothing wrong could be identified.

So currently with my recently formatted computer, I installed
1. google chrome
2. My Belkin Wireless Driver
3. My Nvidia latest driver (Clean install)
4. Turned on my driver verifier

Then, while transferring some files over to my external Hard disk for backup, a BSOD appeared again. So i installed Whocrashed and did a check. This was the result:

On Thu 9/27/2012 1:33:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092712-14648-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0xFFFFDA804E4CD734, 0x8, 0x0, 0xFFFFF8800F133686)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.


On Thu 9/27/2012 1:33:31 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x89686)
Bugcheck code: 0xD1 (0xFFFFDA804E4CD734, 0x8, 0x0, 0xFFFFF8800F133686)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 306.23
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 306.23
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 306.23 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL




On Thu 9/27/2012 1:31:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092712-15662-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x6D6A7)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800F1486A7, 0xFFFFF880039D4D38, 0xFFFFF880039D4590)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 306.23
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 306.23
Bug check description: This indicates that a system thread 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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 306.23 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

I'm really lost here, I have no idea what is causing this problem. It always seems to be a different driver that is causing problems.

So I am wondering if its my Ram that is causing an issue as my motherboard H61MLV does not list my Crosair 4Gb DDR3 rams in its supported rams list.

It surely would be your ram as its not in the supported with your mobo.
Do you have a friend who can lend you ram? (compatible with your mobo of course)

Hmm, I will have to check on that. People don't thank you guys enough! U guys have been awesome! I will get back to you after Ive done that.

Sure.
Post back when you're ready

Hey, Problem Solved. RAM incompatibility...