BSOD from multiple drivers

[cosmicpig]

I have been getting these crashes over and over for a very long time, but it only started getting unbearable since i started playing Battlefield 3. The crashes inexplicably increases the occurrence of crashes from randomly to about 75% of the time upon running the game for a short period. The latest crash appears to be caused by my graphics driver which i updated today so if you say all my problems are caused by that one driver it is unlikely (though i don't entirely discount it, simply doubt). Finally while I was getting the crash dumps together for this thread and a random error occurred which i have NEVER seen before, i copied and pasted the information i saw in a txt file in hopes that it may help. I should also note that i have done a bunch of research on resolving the issue myself, but everything that they are asking others to do is just enough over my head that applying it to my issue flabbergasts me. I also don't have my install disc to windows 7 ultimate x64, so if you conclude a system repair is required i don't think i will be able to do it (just letting any of you know). Finally i will post some information on my latest crashes from whocrashed in the possibility it will help along with my dmp files attached (and the aforementioned txt file).

Thank you for any and all help in advance


[FONT=Segoe UI, Arial]On Thu 1/17/2013 5:55:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011613-23571-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]nvlddmkm.sys[/FONT] (nvlddmkm+0x205D21)
Bugcheck code: 0xA (0xFFFFEE7FFFFFFFD8, 0x2, 0x1, 0xFFFFF800032EFFD4)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: [FONT=Segoe UI, Arial]NVIDIA Windows Kernel Mode Driver, Version 310.90 [/FONT]
company: [FONT=Segoe UI, Arial]NVIDIA Corporation[/FONT]
description: NVIDIA Windows Kernel Mode Driver, Version 310.90
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 310.90 , NVIDIA Corporation).
Google query: [FONT=Segoe UI, Arial]nvlddmkm.sys NVIDIA Corporation IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]

[FONT=Segoe UI, Arial]On Thu 1/17/2013 5:55:14 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFEE7FFFFFFFD8, 0x2, 0x1, 0xFFFFF800032EFFD4)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]On Wed 1/16/2013 7:59:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011613-26332-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800032C5810, 0xFFFFF8800C323970, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 1/15/2013 4:00:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011513-21684-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
Bugcheck code: 0x1 (0x76E9FA1A, 0x0, 0xFFFF0000, 0xFFFFF8800783CCA0)
Error: [FONT=Segoe UI, Arial]APC_INDEX_MISMATCH[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 1/15/2013 3:13:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011413-25256-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
Bugcheck code: 0x4A (0x76D2FC0A, 0x2, 0x0, 0xFFFFF880096A2CA0)
Error: [FONT=Segoe UI, Arial]IRQL_GT_ZERO_AT_SYSTEM_SERVICE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 1/15/2013 2:43:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011413-29281-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x90FD4)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003295FD4, 0xFFFFF880009A9968, 0xFFFFF880009A91D0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 1/15/2013 2:32:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011413-22869-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
Bugcheck code: 0x34 (0x50830, 0xFFFFF8800319A548, 0xFFFFF88003199DB0, 0xFFFFF800032EDFD4)
Error: [FONT=Segoe UI, Arial]CACHE_MANAGER[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a problem occurred in the file system's cache manager.
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.
[/FONT]

[FONT=Segoe UI, Arial]On Mon 1/14/2013 10:47:57 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011413-23431-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
Bugcheck code: 0x34 (0x50830, 0xFFFFF880031856C8, 0xFFFFF88003184F30, 0xFFFFF800032BF7A5)
Error: [FONT=Segoe UI, Arial]CACHE_MANAGER[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a problem occurred in the file system's cache manager.
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.
[/FONT]

[FONT=Segoe UI, Arial]On Mon 1/14/2013 5:40:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011313-19796-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
Bugcheck code: 0xA (0x48, 0x2, 0x1, 0xFFFFF800033400BF)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]On Mon 1/14/2013 5:31:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011313-19843-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800032CF7A5, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]On Sun 1/13/2013 12:39:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011313-25755-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
Bugcheck code: 0x1A (0x401, 0xFFFFF6FB831FDE50, 0x80000000134FB863, 0xFFFFF6BB831FDE50)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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 which cannot be identified at this time. [/FONT][FONT=Segoe UI, Arial][FONT=Segoe UI, Arial]
[/FONT][/FONT]

 

[Northernsoul55]

Hi cosmicpig,

I can take a look at your crash dumps although i am not a BSOD expert.

Firstly can you please update to Wndows 7 Service pack 1, then post a fresh mini dump after the next BSOD occurs. As this will provide more stability to your system.

Cheers

Dave

 

[cosmicpig]

Hi cosmicpig,

I can take a look at your crash dumps although i am not a BSOD expert.

Firstly can you please update to Wndows 7 Service pack 1, then post a fresh mini dump after the next BSOD occurs. As this will provide more stability to your system.

Cheers

Dave

I have tried 3 times to update to service pack one, the update always fails.

 

[Northernsoul55]

Hi cosmicpig,

I can take a look at your crash dumps although i am not a BSOD expert.

Firstly can you please update to Wndows 7 Service pack 1, then post a fresh mini dump after the next BSOD occurs. As this will provide more stability to your system.

Cheers

Dave

I have tried 3 times to update to service pack one, the update always fails.

Hi,

You could try install SP1 as a stand alone install, please read and then pick the correct one for your system:

Download Windows 7 and Windows Server 2008 R2 Service Pack 1 (KB976932) from Official Microsoft Download Center

The one you need is:

windows6.1-KB976932-X64.exe 903.2Mb

Try that and post back

cheers

Dave

 

[cosmicpig]

Hey dave,

Thanks for the responses, you can call me Travis as that is my name! So im installing windows 7 service pack 1 right now, but im going to upload another dmp as it may give you a compare and contrast directly before the update installation as it crashed moments after the download completed.

 

[Northernsoul55]

hey travis,
I will look @ yourfiles tomorrow and hopefully find a solution for you. I need sleep now
SP1 should help stabilise your system :-D
Also run an elevated command and type SFC /scannow after SP1 installed.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

cheers
Dave

 

[cosmicpig]

Hey,

So i finally got windows 7 service pack 1 installed and good, ran a SFC scan and it turned up no integrity violations. I will run battlefield 3 and see if i can force my computer to crash and upload to dump file if it does.

Travis

 

[Northernsoul55]

Hey Travis,

ok so the first BSOD related to a memory exception (perhaps caused by a driver)
Please run these two tests to verify your memory and find which driver/s are causing the problem.

Memtest.

Please follow this guide:
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

and leave it running for at least 7 or 8 passes and post results.

Driver verifier:

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Ok also could do with your msinfo32.nfo file:

Please upload your msinfo32.nfo file. To get this: Start Menu>Type msinfo32 into the Search programs and files box.
When it opens, go to File, Save>Save as msinfo32.nfo and save in a place you will remember.
Let it finish the process of gathering and saving the system info>Right click the .nfo file.
click send to compressed (zipped) folder>Upload the .zip file here.

ok next:

BugCheck 24,
Probably caused by : Ntfs.sys

Cause

One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error.
Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.

Please run (again from an elevated command)

Chkdsk /f /r to detect and resolve any file system structural corruption.

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

A lot of the other crashes are related to Battlefield 3 etc
I suggest you update your Graphics drivers to the latest release,
Once you post the msinfo32 I can help identify any problem drivers.

After all that is done, post back your dump files after the next crash.

Cheers
Dave

 

[cosmicpig]

Ok so i ran memtest86 for like 10 passes and it turned up some errors i think, if errors are denoted by a red line. I don't know what the errors are though. Is there a file i can upload for you to look at the results? and i will attach my MSINFO32 in this post, also thus far no crashes, but that is saying very little. Also i haven't had time to do driver verifier yet as i have work tonight. Chances are i'll start it up when i get home from work, but i heard it can take up to 36 hours.

 

[Golden]

Hi,

Since the memory tests failed, you now need to work out if its the actual RAM chips, or the RAM slots on the motherboard. To do that follow these steps:

1. Remove all RAM chips
2. Install ONE RAM chip into slot 1 on the motherboard and run MemTest86+ for 7 passes
3. If it passes, remove that RAM chip and insert the next RAM chip and repeat until all RAM chips have passed the test
- that means that slot 1 on the motherboard is good, repeat the exercise with slot 2 on the motherboard etc. etc. until you find the defective slot
4. If a RAM chip fails in step 2, insert it into slot 2 and run the tests to confirm its the RAM chip.
- test all the RAM chips in all the slots this way to ensure you dont have both a defective RAM chip and defective RAM slot.

Regards,
Golden

 

[cosmicpig]

I won't have time likely to run that memory test until this thursday as i am going out of town. I will upload the latest dump files, but then it is likely i won't be able to look at my computer until that day. So if you have no other suggestions, please just imagine this thread on temporary hiatus.

Travis.