Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

No BSODs for months, now four in one day

Started by QPhysics , Jan 23 2013 08:23 PM

  • Please log in to reply

#1
QPhysics
Posted 23 January 2013 - 08:23 PM

QPhysics

    New Member

  • Member
  • Pip
  • 7 posts
I have not added any new hardware or even installed any new software in the past few weeks, but for some reason I've started having BSODs. Debuggers don't seem to tell me much specifically that's helpful. The culprit always seems to be a system file like cng.sys, ntkrnlmp.exe, ntoskrnl, etc. I've heard that those are generally not the actual problem (and I've fun sfc /scannow and it tells me I have no errors in the system files) but a driver that was called by those system files.
I would attach the three dump files, but when I try, I get, "Error You aren't permitted to upload this kind of file"

Well...guess what...another BSOD as I was typing this, so we're up to FIVE today.
Since it won't let me paste the actual .dmp files, here's the output from BlueScreenView.exe for the four that wrote a minidump (the fifth was during boot and it didn't write anything).

If anyone can give me a good idea of even what to check next, I'd really appreciate it.
Thanks!

012313-20545-01.dmp 23Jan13 21:14:45 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff960`000fe018 fffff880`0895d9b0 00000000`00000000 rdprefmp.sys rdprefmp.sys+5bdc9b0 x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\012313-20545-01.dmp 4 15 7601 287,604

012313-24570-01.dmp 23Jan13 19:34:49 SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`038aa068 fffff880`031bcfc8 fffff880`031bc820 amdppm.sys amdppm.sys+1601d170 x64 ntoskrnl.exe+54068 C:\Windows\Minidump\012313-24570-01.dmp 4 15 7601 288,372

012313-63554-01.dmp 23Jan13 14:30:25 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`038a187b fffff880`0216fe40 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+7efc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17944 (win7sp1_gdr.120830-0333) x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\012313-63554-01.dmp 4 15 7601 276,960

012313-25662-01.dmp 23Jan13 13:29:59 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`038b487b fffff880`0963ee40 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+7efc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17944 (win7sp1_gdr.120830-0333) x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\012313-25662-01.dmp 4 15 7601 276,960
  • 0

Advertisements

#2
QPhysics
Posted 23 January 2013 - 08:27 PM

QPhysics

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
Here is the output from WinDbg for the latest BSOD, hopefully this means more to someone smarter than me :-)


Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\012313-20545-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Symbols;SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`03804000 PsLoadedModuleList = 0xfffff800`03a48670
Debug session time: Wed Jan 23 21:13:21.705 2013 (UTC - 5:00)
System Uptime: 0 days 1:38:54.938
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960000fe018, fffff8800895d9b0, 0}

Probably caused by : win32k.sys ( win32k!bDeleteBrush+a0 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960000fe018, Address of the instruction which caused the bugcheck
Arg3: fffff8800895d9b0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
win32k!bDeleteBrush+a0
fffff960`000fe018 44397608 cmp dword ptr [rsi+8],r14d

CONTEXT: fffff8800895d9b0 -- (.cxr 0xfffff8800895d9b0)
rax=0000000000000001 rbx=0000000000000001 rcx=fffff900c021e8e8
rdx=fffff900c021e8e8 rsi=fffbf900c26f3a10 rdi=000000002810145f
rip=fffff960000fe018 rsp=fffff8800895e390 rbp=fffff8800895e750
r8=0000000000000001 r9=000000000000145f r10=0000000000003d1d
r11=0000000000000006 r12=0000000000290d08 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
win32k!bDeleteBrush+0xa0:
fffff960`000fe018 44397608 cmp dword ptr [rsi+8],r14d ds:002b:fffbf900`c26f3a18=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff960000b7fea to fffff960000fe018

STACK_TEXT:
fffff880`0895e390 fffff960`000b7fea : 00000000`2810145f 00000000`00000000 fffff900`00000001 fffff900`00000000 : win32k!bDeleteBrush+0xa0
fffff880`0895e440 fffff960`000af0c9 : 00000000`00000010 00000000`00000001 00000000`00000000 fffff960`00078081 : win32k!NtGdiDeleteObjectApp+0x82
fffff880`0895e470 fffff800`0388215c : fffffa80`100db060 fffff880`0895e750 00000000`fffffffc fffff900`c43cfac0 : win32k!NtGdiFlushUserBatch+0xd45
fffff880`0895e6d0 00000000`775e913a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceGdiTebAccess+0x25
00000000`0362fa38 fffff800`0387a610 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775e913a
fffff880`0895e8b0 00000000`00000000 : 00000000`00000000 00000000`00000001 fffff880`0895e960 00000000`00000001 : nt!KiCallUserMode


FOLLOWUP_IP:
win32k!bDeleteBrush+a0
fffff960`000fe018 44397608 cmp dword ptr [rsi+8],r14d

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!bDeleteBrush+a0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 50aeecc6

STACK_COMMAND: .cxr 0xfffff8800895d9b0 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k!bDeleteBrush+a0

BUCKET_ID: X64_0x3B_win32k!bDeleteBrush+a0

Followup: MachineOwner
---------
  • 0

#3
QPhysics
Posted 26 January 2013 - 07:51 AM

QPhysics

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
And another one overnight...
Does anyone see anything here that might help me figure out where to look for a cause?
I've run RAM tests and chkdsk /f and there are no errors.

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\012613-23181-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Symbols;SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`03868000 PsLoadedModuleList = 0xfffff800`03aac670
Debug session time: Sat Jan 26 06:04:10.024 2013 (UTC - 5:00)
System Uptime: 1 days 11:00:18.632
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff800038bc068, fffff880033cafc8, fffff880033ca820}

Probably caused by : cng.sys ( cng!GatherRandomKey+294 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800038bc068, The address that the exception occurred at
Arg3: fffff880033cafc8, Exception Record Address
Arg4: fffff880033ca820, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!ExpGetLookasideInformation+8c
fffff800`038bc068 0fb742c0 movzx eax,word ptr [rdx-40h]

EXCEPTION_RECORD: fffff880033cafc8 -- (.exr 0xfffff880033cafc8)
Cannot read Exception record @ fffff880033cafc8

CONTEXT: fffff880033ca820 -- (.cxr 0xfffff880033ca820)
rax=0000000000000070 rbx=0000000000000ff4 rcx=fffff8800af00b30
rdx=fffbf880009ebce0 rsi=0000000000000000 rdi=0000000000000001
rip=fffff800038bc068 rsp=fffff880033cb200 rbp=000000000000004e
r8=fffff80003a84400 r9=0000000000000000 r10=0000000000000000
r11=0000fffffffff000 r12=fffff880033cb2d0 r13=000000000001fe90
r14=fffff880033cb840 r15=0000000000000000
iopl=0 nv up ei ng nz na pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010283
nt!ExpGetLookasideInformation+0x8c:
fffff800`038bc068 0fb742c0 movzx eax,word ptr [rdx-40h] ds:002b:fffbf880`009ebca0=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003b16100
ffffffffffffffff

FOLLOWUP_IP:
cng!GatherRandomKey+294
fffff880`01434244 85c0 test eax,eax

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff80003becc08 to fffff800038bc068

STACK_TEXT:
fffff880`033cb200 fffff800`03becc08 : 00000000`00000000 00000000`00000ff4 fffff880`033cb2d0 00000000`00000000 : nt!ExpGetLookasideInformation+0x8c
fffff880`033cb290 fffff800`03bed029 : fffff8a0`3d000170 00000000`00000000 00000000`00000004 00000000`00000000 : nt!ExpQuerySystemInformation+0x15e8
fffff880`033cb640 fffff800`038e6253 : fffff8a0`3d010000 fffff800`038e51fd 00000000`00000041 fffff8a0`3d000000 : nt!NtQuerySystemInformation+0x4d
fffff880`033cb680 fffff800`038e2810 : fffff880`01434244 00000000`00020000 fffff880`033cb844 fffff8a0`3d000148 : nt!KiSystemServiceCopyEnd+0x13
fffff880`033cb818 fffff880`01434244 : 00000000`00020000 fffff880`033cb844 fffff8a0`3d000148 00000000`00000000 : nt!KiServiceLinkage
fffff880`033cb820 fffff880`0143473d : fffffa80`0d18bbb0 fffff800`038ee5d3 00000000`20206f49 00000000`00000000 : cng!GatherRandomKey+0x294
fffff880`033cbbe0 fffff800`03bd959d : 00000000`00000001 00000000`00000001 00000000`00000000 fffffa80`0c782040 : cng!scavengingWorkItemRoutine+0x3d
fffff880`033cbc80 fffff800`038f0641 : fffff800`03bc6700 fffffa80`0c782001 00000000`00000000 00000000`00000000 : nt!IopProcessWorkItem+0x3d
fffff880`033cbcb0 fffff800`03b7de5a : 00000000`00000000 fffffa80`0c782040 00000000`00000080 fffffa80`0c772040 : nt!ExpWorkerThread+0x111
fffff880`033cbd40 fffff800`038d7d26 : fffff880`03164180 fffffa80`0c782040 fffff880`0316efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033cbd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: cng!GatherRandomKey+294

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: cng

IMAGE_NAME: cng.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5037a204

STACK_COMMAND: .cxr 0xfffff880033ca820 ; kb

FAILURE_BUCKET_ID: X64_0x7E_cng!GatherRandomKey+294

BUCKET_ID: X64_0x7E_cng!GatherRandomKey+294

Followup: MachineOwner
---------
  • 0

#4
QPhysics
Posted 27 January 2013 - 07:42 AM

QPhysics

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
Anyone?
Here are some dump files and other system info. http://sdrv.ms/110xLDR
  • 0

#5
rshaffer61
Posted 27 January 2013 - 09:16 AM

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Hi Qphysics and a word of advise. When adding info to your topic before anyone responds please edit your original post as it makes your topic look like you are getting assistance. First thing i would like you to check is your memory.

A If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...


1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

Posted Image

8. Locate memtest86+-4.20.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

Posted Image

10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:


Posted Image

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

Posted Image

The following image is the test results area:

Posted Image

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.
  • 0

#6
QPhysics
Posted 27 January 2013 - 12:24 PM

QPhysics

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
I've already done this. Memtest86+ on each of the four RAM sticks individually and with all four installed...no errors.
I've also run sfc \scannow and gotten no errors. I ran chkdsk \f overnight and there were no bad sectors.
  • 0

#7
rshaffer61
Posted 27 January 2013 - 12:47 PM

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK have you recently updated any drivers or hardware just prior to this issue starting?
Secondly I would like to get a better look at the BSOD's by doing the following.




Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program
  • 0

#8
QPhysics
Posted 27 January 2013 - 02:14 PM

QPhysics

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
No new hardware. I've updated a couple drivers (nForce chipset and such) but those were through either Windows Update or the HP update assistant.

I've had BlueScreenView for quite a while. Output follows:

==================================================
Dump File : 012713-37315-01.dmp
Crash Time : 27Jan13 13:33:03
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff960`000d758e
Parameter 3 : fffff880`07811cc0
Parameter 4 : 00000000`00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+c758e
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7efc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012713-37315-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 287,604
==================================================

==================================================
Dump File : 012713-20638-01.dmp
Crash Time : 27Jan13 13:08:42
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`038b0068
Parameter 3 : fffff880`031b5fc8
Parameter 4 : fffff880`031b5820
Caused By Driver : usbaudio.sys
Caused By Address : usbaudio.sys+8912d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+54068
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012713-20638-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 287,604
==================================================

==================================================
Dump File : 012713-19094-01.dmp
Crash Time : 27Jan13 07:02:34
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`03860068
Parameter 3 : fffff880`033b5fc8
Parameter 4 : fffff880`033b5820
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+54068
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor : x64
Crash Address : ntoskrnl.exe+54068
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012713-19094-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 276,960
==================================================

==================================================
Dump File : 012713-25365-01.dmp
Crash Time : 27Jan13 00:09:05
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff960`00153354
Parameter 3 : fffff880`0874cfa0
Parameter 4 : 00000000`00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+d3354
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7efc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012713-25365-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 276,960
==================================================

==================================================
Dump File : 012613-21808-01.dmp
Crash Time : 26Jan13 11:17:17
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff880`03189830
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7efc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor : x64
Crash Address : ntoskrnl.exe+7efc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012613-21808-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 276,960
==================================================

==================================================
Dump File : 012613-21434-01.dmp
Crash Time : 26Jan13 10:52:09
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`03859068
Parameter 3 : fffff880`033c3fc8
Parameter 4 : fffff880`033c3820
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+54068
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor : x64
Crash Address : ntoskrnl.exe+54068
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012613-21434-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 276,960
==================================================

==================================================
Dump File : 012613-23181-01.dmp
Crash Time : 26Jan13 08:35:07
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`038bc068
Parameter 3 : fffff880`033cafc8
Parameter 4 : fffff880`033ca820
Caused By Driver : storport.sys
Caused By Address : storport.sys+2299
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+54068
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012613-23181-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 276,960
==================================================

==================================================
Dump File : 012413-22261-01.dmp
Crash Time : 24Jan13 12:53:52
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+3f0bf
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7ef90
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012413-22261-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 287,796
==================================================

==================================================
Dump File : 012313-20545-01.dmp
Crash Time : 23Jan13 21:14:45
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff960`000fe018
Parameter 3 : fffff880`0895d9b0
Parameter 4 : 00000000`00000000
Caused By Driver : rdprefmp.sys
Caused By Address : rdprefmp.sys+5bdc9b0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7efc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012313-20545-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 287,604
==================================================

==================================================
Dump File : 012313-24570-01.dmp
Crash Time : 23Jan13 19:34:49
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`038aa068
Parameter 3 : fffff880`031bcfc8
Parameter 4 : fffff880`031bc820
Caused By Driver : amdppm.sys
Caused By Address : amdppm.sys+1601d170
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+54068
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012313-24570-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 288,372
==================================================

==================================================
Dump File : 012313-63554-01.dmp
Crash Time : 23Jan13 14:30:25
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`038a187b
Parameter 3 : fffff880`0216fe40
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7efc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor : x64
Crash Address : ntoskrnl.exe+7efc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012313-63554-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 276,960
==================================================

==================================================
Dump File : 012313-25662-01.dmp
Crash Time : 23Jan13 13:29:59
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`038b487b
Parameter 3 : fffff880`0963ee40
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7efc0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor : x64
Crash Address : ntoskrnl.exe+7efc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012313-25662-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 276,960
==================================================

==================================================
Dump File : 012213-23025-01.dmp
Crash Time : 22Jan13 13:54:22
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff960`001de5d8
Parameter 3 : fffff880`0bda5850
Parameter 4 : 00000000`00000000
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+1ce5d8
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7efc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\012213-23025-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 276,960
==================================================

==================================================
Dump File : 011613-92368-01.dmp
Crash Time : 16Jan13 17:48:18
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`03664068
Parameter 3 : fffff880`033b5fc8
Parameter 4 : fffff880`033b5820
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+54068
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor : x64
Crash Address : ntoskrnl.exe+54068
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\011613-92368-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 276,960
==================================================
  • 0

#9
rshaffer61
Posted 27 January 2013 - 02:23 PM

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK your errors are all over the place. Something else is causing all this.

Run hard drive diagnostics: http://www.tacktech....ay.cfm?ttid=287
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (select "Write image file to disc" option), and make the CD bootable.

NOTE. If your hard drive is made by Toshiba, try the Hitachi DFT CD Image version of the software

Thanks to Broni for the instructions
  • 0

#10
QPhysics
Posted 27 January 2013 - 03:18 PM

QPhysics

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
I have run "Data Lifeguard Diagnostic for Windows" from Western Digital. Passed all tests.
I have run chkdsk /f, no bad sectors.
I have run sfc /scannow, no errors.

It's not the hard drive, and it's not the RAM. That's part of why this one has me completely stumped.

I have the driver verifier (verifier.exe) running now. I'll post any new BSOD information.
  • 0

#11
rshaffer61
Posted 27 January 2013 - 03:20 PM

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Other then a driver, corrupted OS or a infection we are looking at a serious hardware issue.
  • 0
Back to Windows Vista and Windows 7 · Next Unread Topic →




Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

  1. Geeks to Go Community
  2. → Retired Forums
  3. → Windows Vista and Windows 7

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP