Go Back   Tech Support Forum > Microsoft Support > BSOD, App Crashes And Hangs

User Tag List

BSOD issues -_- (maybe ram related)

This is a discussion on BSOD issues -_- (maybe ram related) within the BSOD, App Crashes And Hangs forums, part of the Tech Support Forum category. Ok so i've been getting BSOD errors for the past year, some due to unstable CPU which i fixed pretty


Closed Thread
 
Thread Tools Search this Thread
Old 12-19-2011, 04:56 AM   #1
Registered Member
 
Join Date: Sep 2009
Location: Australia
Posts: 33
OS: vista 64-bit sp2



Ok so i've been getting BSOD errors for the past year, some due to unstable CPU which i fixed pretty much right away. But i've had issues with my ram and it's timings as I'm using a lanparty t3eh9 i5 mobo. Specs are as follows:

CPU- i5 760 @ 4ghz 1.27v
RAM - Ripjaws 2x4gb @ 1600mhz 1.66v (mobo only allows 1.64 or 1.66 not 1.65)
GPU - GTX 570 msi twin frozr II SLi @ 850mhz core/2000mhz mem 1.075v
PSU - Antec 900w gamer edition

As far as power goes, never had a power-down due to overload, had all benchmarks running (prime95+3dmark11/furmark sli). I honestly dunno what to make of this, i thought i solved the problem by running a higher vtt but keeping it within the ram limitations of course. This mobo really does'nt like xmp settings for ram so I set it myself and it seemed great. This system has only had these hiccups since playing bf3 not generally during any other game apart from earlier this year when i was oc'ing (which i stabilized). You'll find minidump files attached (i may know how to OC and use the registry but screw reading error codes). I always use task manager to shut down all apps apart from those which i use (games), this includes win update, steam, spybot, adobe, nvidia update etc...

Each post i've seen with my error codes suggests ram but i have NEVER had a bad stick and really don't want to think i have one now. Also in those posts their additional error codes (not read by me but professionals) have been different to mine including their stamps (not date stamps). Sorry for the long post but I want to give as clear of a picture as possible. And no on my oc's i never had a hang becuase i pushed it too far, only from undervolting. I have never oc'd this ram, always kept it @ 1200mhz or 1600mhz and never over 1.66v so i dunno how it could be the ram. Please help im at my wits end :(.

Sincerely,

Rob.

P.S. the minidump is only since the start of december as the rest may be misleading or too long due to OC instabilities (again due to undervoltage).

P.P.S. for some reason your site is showing 32-bit instead of 64-bit for my OS.... also another note, in my BIOS settings i recently enabled 32-bit calculations and S.M.A.R.T on my primary (OS) but left it to auto on my data drive (although i enabled 32-bit on that too just in case). I dunno if that makes a difference but I really do appreciate any help that can be offered :).
Attached Files
File Type: zip MaulerMiniDump.zip (483.0 KB, 35 views)
Mauler1987 is offline  
Sponsored Links
Advertisement
 
Old 12-19-2011, 05:20 AM   #2
Registered Member
 
Join Date: Sep 2009
Location: Australia
Posts: 33
OS: vista 64-bit sp2



Not allowing me to edit for some reason but just saw the BSOD report instructions and find additional file attached (2nd one in another post as its .39mb over the allowed limit for .rar).
Attached Files
File Type: zip Mauler Perfmon Report.zip (134.2 KB, 36 views)
Mauler1987 is offline  
Old 12-19-2011, 05:23 AM   #3
Registered Member
 
Join Date: Sep 2009
Location: Australia
Posts: 33
OS: vista 64-bit sp2



Sorry about all this :(.
Attached Files
File Type: zip Windows7_Vista_jcgriff2.zip (3.48 MB, 43 views)
Mauler1987 is offline  
Sponsored Links
Advertisement
 
Old 12-19-2011, 05:29 AM   #4
TSF Enthusiast
 
Join Date: Apr 2011
Posts: 388
OS: windows 7



I would advise downloading memtest Memtest86+ - Advanced Memory Diagnostic Tool
Burn that to a CD/DVD and test each stick individually.
efx8 is offline  
Old 12-19-2011, 05:31 AM   #5
Registered Member
 
Join Date: Sep 2009
Location: Australia
Posts: 33
OS: vista 64-bit sp2



Quote:
Originally Posted by efx8 View Post
I would advise downloading memtest Memtest86+ - Advanced Memory Diagnostic Tool
Burn that to a CD/DVD and test each stick individually.
I did a while back (before the vtt changes to make it more stable while playing bf3) and it passed 4 hours no errors =/. That's why i'm really confused :S.
Mauler1987 is offline  
Old 12-19-2011, 05:41 AM   #6
TSF Enthusiast
 
Join Date: Apr 2011
Posts: 388
OS: windows 7



Try using one stick and then play battlefield and see if the BSOD happens again.

Check the temperatures of the CPU/GPU you can try this software SpeedFan - Free software downloads and software reviews - CNET Download.com
efx8 is offline  
Old 12-19-2011, 05:54 AM   #7
Registered Member
 
Join Date: Sep 2009
Location: Australia
Posts: 33
OS: vista 64-bit sp2



Ok sooooooo, we may have found the culprit (i dunno, hopefully) I tried the verifier while waiting for a response and i got a BSOD before the desktop even booted (crashed right on loading). Except in the minidump i cant see any new files created so im hoping maybe 1 got overwritten ? :S. I did see 2 of the (unknown) unsigned drivers before i started the verifier and rebooted had minidump and minidump_dump in their names...maybe related ?.
Attached Files
File Type: zip Mini030711-01.zip (1.31 MB, 37 views)
Mauler1987 is offline  
Old 12-19-2011, 05:58 AM   #8
Registered Member
 
Join Date: Sep 2009
Location: Australia
Posts: 33
OS: vista 64-bit sp2



Quote:
Originally Posted by efx8 View Post
Try using one stick and then play battlefield and see if the BSOD happens again.

Check the temperatures of the CPU/GPU you can try this software SpeedFan - Free software downloads and software reviews - CNET Download.com
Haven't tried individual sticks yet but as you can see from my most recent post the culprit may be found, thinking maybe a virus or malware that spybot or malwarebytes hasn't picked up. I have constantly checked temps though as I do with all new games as im an avid benchmarker and ocd sufferer :P my gpu temps stay around 60c with the bottom card reaching a peak of 5c more than the top so around 65-67c, the cpu i keep cooled with the nh-d14 from noctua stays a reasonable temp of below 70c even in this tropical summer heat :) (australian tropics sucks for oc'ing lol).
Mauler1987 is offline  
Old 12-19-2011, 06:01 AM   #9
Registered Member
 
Join Date: Sep 2009
Location: Australia
Posts: 33
OS: vista 64-bit sp2



By the way amazing reply times even for members, Didn't expect that kind of dedication :).
Mauler1987 is offline  
Old 12-19-2011, 06:08 AM   #10
Registered Member
 
Join Date: Sep 2009
Location: Australia
Posts: 33
OS: vista 64-bit sp2



Also one more mention, In BF3 im having to use a dos command to allow it to use 2500 mb of ram (or so im led to believe) as the game wouldn't even load without that change it would just stay on the loading screen and need to be ended via task manager. It is a common problem that 1000's of people have suffered, And through that number alone im guessing it is not one of the causes. BF3.exe stops responding error while loading multiplayer fix - YouTube

Above is the cmd i used, please get back to me if this could cause major issues (other games have not had an issue as of yet).
Mauler1987 is offline  
Old 12-19-2011, 07:07 AM   #11
TSF - Enthusiast
 
Join Date: Jan 2009
Location: Toronto
Posts: 5,760
OS: Windows 10 Pro 64 Bit

My System


EA is famous for releasing games before all the kinks have been ironed out. Have you checked for any game patches?
Amd_Man is offline  
Old 12-19-2011, 01:02 PM   #12
Registered Member
 
Join Date: Sep 2009
Location: Australia
Posts: 33
OS: vista 64-bit sp2



Origin (EA's version of steam) downloads them automatically.
Mauler1987 is offline  
Old 12-20-2011, 03:14 AM   #13
Registered Member
 
Join Date: Sep 2009
Location: Australia
Posts: 33
OS: vista 64-bit sp2



Ok weird, tried both stick individually.....4 hours of play no errors on either.....strange :S. It usually BSOD's within an hour or even 30 minutes.
Mauler1987 is offline  
Old 12-20-2011, 05:57 PM   #14
Registered Member
 
Join Date: Sep 2009
Location: Australia
Posts: 33
OS: vista 64-bit sp2



bump, still getting bsod's although less frequent. Looked closer at the unsigned drivers in verifier and googled them. Most of which are DRM from microvision and other things but ill list them here;

atksgt.sys (unknown)
dump_atapi.sys (unknown)
dump_dumpata.sys (unknown)
lirsgt.sys (unknown)
rtcore64.sys (unknown)
atmfd.dll (Adobe Systems)
elbycdio.sys (Elaborate Bytes AG)
e1k60x64.sys (Intel Corporation)
secdrv.sys (Macrovision Corporation Europe)
sscdcm.sys (MCCI Corporation)
sscdwh.sys (MCCI Coproration)
scdemu.sys (Power Software Ltd)
rtkvhd64.sys (Realtek Semiconductor Corp.)
elbycdfl.sys (Slysoft, Inc.) <-- clone dvd used to bypass Witcher 2 performance issues.
cpuz134_x64.sys (Windopws (R) Win 7 DDK provider)


This problem is most frustrating -_-.
Mauler1987 is offline  
Old 12-21-2011, 08:42 AM   #15
Registered Member
 
Join Date: Sep 2009
Location: Australia
Posts: 33
OS: vista 64-bit sp2



ok so memtest86 and prime95 blend are showing no issues, what the hell ???? -_- if the sticks were unstable surely i would get some errors or workers stopping =/. Any idea ?
Mauler1987 is offline  
Old 12-21-2011, 07:01 PM   #16
Registered Member
 
Join Date: Sep 2009
Location: Australia
Posts: 33
OS: vista 64-bit sp2



Bump, anybody ? =/.
Mauler1987 is offline  
Old 12-22-2011, 01:45 AM   #17
Registered Member
 
Join Date: Sep 2009
Location: Australia
Posts: 33
OS: vista 64-bit sp2



BSOD again! this time when just opening origin (ea's steam) before it even went to launch bf3.....dump file is attached its a 1e code...if someone familiar in these codes could have a look i would be extatic.
Attached Files
File Type: zip Mini122211-01.zip (20.5 KB, 37 views)
Mauler1987 is offline  
Old 12-24-2011, 09:08 PM   #18
Administrator
Manager, Microsoft Support
Acting Manager, Security
BSOD Kernel Dump Expert
Microsoft Windows Insider MVP
 
jcgriff2's Avatar
 
Join Date: Sep 2007
Location: New Jersey Shore
Posts: 34,347
OS: Windows 10, 8.1 + Windbg :)



See if Driver Verifier flags any 3rd party drivers -

https://www.techsupportforum.com/foru...ed-473665.html
jcgriff2 is online now  
Old 12-26-2011, 12:48 AM   #19
Registered Member
 
Join Date: Sep 2009
Location: Australia
Posts: 33
OS: vista 64-bit sp2



Quote:
Originally Posted by jcgriff2 View Post
See if Driver Verifier flags any 3rd party drivers -

https://www.techsupportforum.com/foru...ed-473665.html
Well it seems it doesnt matter what driver im verfying it bsod's before the os even boots, has the loading symbol then it crashes. Doesn't create a dump file but i did manage to see it was a c9 error which is a driver failure. As mentioned in a few posts above i tried every single one of those drivers and it bsod'd, took the better part of a day to do with all the system restores taking place. And i know the dump driver is a windows driver even though it says unknown as it was loaded in safe mode :S. This is quite strange but i did however download and use whocrashed ill copy and paste the few it lists.

System Information (local)
--------------------------------------------------------------------------------

computer name: MAULER-PC
windows version: Windows Vista Service Pack 2, 6.0, build: 6002
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8578605056 total
VM: 2147352576, free: 1993723904



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 25/12/2011 1:57:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini122511-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800032F4E8E, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 25/12/2011 1:57:02 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800032F4E8E, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 24/12/2011 6:58:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini122411-01.dmp
This was probably caused by the following module: hal.dll (hal+0x78BA)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8009E30030, 0xB6000000, 0x100125)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 which cannot be identified at this time.


On Fri 23/12/2011 1:56:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini122311-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0xA (0x82F, 0x2, 0x0, 0xFFFFF80003078E42)
Error: 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 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 which cannot be identified at this time.


On Thu 22/12/2011 9:38:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini122211-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003331E8E, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 19/12/2011 12:29:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121911-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800032B70E2, 0x1, 0x18)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 19/12/2011 12:22:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121911-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x50 (0xFFFFF2800945F184, 0x0, 0xFFFFFA60010129BE, 0x7)
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
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 14/12/2011 9:46:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121411-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x109 (0xA3A039D89DDBB63A, 0xB3B7465EF058836E, 0xFFFFF800030B8E00, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 which cannot be identified at this time.


On Sun 11/12/2011 11:53:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121111-10.dmp
This was probably caused by the following module: unknown_module_00000000`0000000.sys (Unloaded_Unknown_Module_00000000`0000000+0x50)
Bugcheck code: 0x50 (0xFFFFF8004BE81984, 0x8, 0xFFFFF8004BE81984, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
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: unknown_module_00000000`0000000.sys .
Google query: unknown_module_00000000`0000000.sys PAGE_FAULT_IN_NONPAGED_AREA




On Sun 11/12/2011 6:40:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121111-09.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000303C15A, 0x0, 0x7EFA0000)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 11/12/2011 6:37:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121111-08.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000332FE8E, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 11/12/2011 6:05:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121111-07.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800032FDE8E, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 11/12/2011 5:40:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121111-06.dmp
This was probably caused by the following module: hal.dll (hal+0x78BA)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8009FA1030, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 which cannot be identified at this time.


On Sun 11/12/2011 5:34:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121111-05.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0xA (0x38, 0x2, 0x0, 0xFFFFF8000308E5E8)
Error: 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 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 which cannot be identified at this time.


On Sun 11/12/2011 5:21:46 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121111-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x50 (0xFFFFB80067E13AB7, 0x0, 0xFFFFF80003088E74, 0x7)
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
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\Mini011911-01.dmp
C:\Windows\Minidump\Mini013011-01.dmp
C:\Windows\Minidump\Mini021011-01.dmp
C:\Windows\Minidump\Mini050611-01.dmp
C:\Windows\Minidump\Mini050611-02.dmp
C:\Windows\Minidump\Mini050611-03.dmp




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

On your computer a total of 77 crash dumps have been found. Only 71 could be analyzed. Only 15 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 290.53 , NVIDIA Corporation)

unknown_module_00000000`0000000.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.



Ok now i rolled back and did driver sweeper in between each nvidia change, still crashes. The driver i don't understand is the unknown module 0000000.sys etc.. i googled it and nothing came up. ntoskrnl.exe is related to the kernel obviously but i couldnt figure as to why it was causing crashes, i found a few forums where people have stated to download and update the processor drivers etc... but i use an i5 760 and could find no actual drivers apart from a graphics driver for it (strange!). Thank you for your reply jcgriff2 I'm just really confused as this is a problem i've had for a while and multiple codes pointing to different things. I also might mention that my motherboard is a now out of date lanparty DK t3eh9 p55 board. I've noticed the bottom pci-ex slot for my 2nd 570 doesnt hold the card in very well it seems the board relies more heavily on the screws at the I/O plate. Dunno if that helps or not but yeah :S. Very sorry about all this, and merry christmas as i see its the 25th in america and hope you all have a happy new year :).

Sincerely,

Rob.
Mauler1987 is offline  
Old 12-26-2011, 01:00 AM   #20
Registered Member
 
Join Date: Sep 2009
Location: Australia
Posts: 33
OS: vista 64-bit sp2



I might add in that ive done more memtests with over 8 passes and did a few prime95's for about 6 hours with no workers failing. I've increased the VTT core so maybe it was the memory controller but i still get bsod's while only playing battlefield 3. The codes i can remember seeing most of the time are 0x124, 0x50 and 0x1a. Even though thats included in the dump files. Most of which point to bad ram but the ram seems stable, although it does get hot to the touch. Im out of ideas as to what it could be but im no code whiz although i wish i was.

Sincerely,

Rob.
Mauler1987 is offline  
Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Similar Threads
Thread Thread Starter Forum Replies Last Post
upgraded ram, having issues
Hi. I built my current computer last winter and recently upgraded my RAM from 2x2G to 2x4G. The problem I'm having, however, is that my computer has suddenly decided to crash on me and being that I just upgraded my RAM I'm tempted to think that's the culprit. When running several applications...
nadrii RAM and Power Supply Support 10 10-26-2011 06:23 AM
BSOD issues...multiple different errors
Computer is a custom built PC OS - Windows 7 x64 · original installed OS on system? - none, this was the first · full retail version (YOU purchased it from retailer) · Age of system - 1 year · Age of OS installation - 1 year - no reinstalls · CPU - Intel Core i7-860 Newegg.com - Intel Core...
boondockheel BSOD, App Crashes And Hangs 5 04-15-2011 07:17 AM
BSOD, Possibly videocard related?
Hey, I've been having alot of BSOD problems, and infact got stuck in a sort of infinite loop until I uninstalled my video drivers on my integrated graphic card. This started happening after I went to overclock my videocard slightly, and I noticed, it'd BSOD everytime I'd attempt to move the memory...
TheKobrakai BSOD, App Crashes And Hangs 5 03-07-2011 01:56 AM
Performance issues after BSOD recovery
Hello, Summary: I recently had isator.sys BSOD errors I think it was the TDSS virus. I basically with a recovery CD fixed boot, fixed MBR and rebuiltBCD at the command prompt screen. So my computer works now, without any BSOD issues. But I am now having some performance issues. Startup...
SuperChargers Resolved HJT Threads 25 02-01-2011 06:02 PM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is on
Smilies are on
[IMG] code is on
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Post a Question


» Site Navigation
 > FAQ
  > 10.0.0.2
Powered by vBadvanced CMPS v3.2.3


All times are GMT -7. The time now is 12:55 PM.


Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2020, vBulletin Solutions, Inc.
vBulletin Security provided by vBSecurity v2.2.2 (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.1.0 (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
Copyright 2001 - 2018, Tech Support Forum

Windows 10 - Windows 7 - Windows XP - Windows Vista - Trojan Removal - Spyware Removal - Virus Removal - Networking - Security - Top Web Hosts