Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD - Help wanted to analyse Minidump log [Windows 7 Pro -- Dell XPS 1340 '09]


  • Please log in to reply
25 replies to this topic

#1 decoy

decoy

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:11:08 PM

Posted 05 January 2013 - 04:43 PM

Hey bros,

I need help decoding the following Minidump log files retrieved by following your guide.

It's for my Dell XPS Studio 1340 from '09.

I recently formatted the laptop, so I've only had the BSOD twice. The reason why I formatted the laptop was because I started getting DLL errors -- but other than that, it worked.

Log file 1:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02a55000 PsLoadedModuleList = 0xfffff800`02c99670
Debug session time: Fri Jan  4 13:15:22.402 2013 (UTC + 1:00)
System Uptime: 0 days 0:00:34.275
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000006, fffff80002b5362e, fffff8800b09d658, fffff8800b09ceb0}

Probably caused by : hardware_disk

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

1: 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: ffffffffc0000006, The exception code that was not handled
Arg2: fffff80002b5362e, The address that the exception occurred at
Arg3: fffff8800b09d658, Exception Record Address
Arg4: fffff8800b09ceb0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - Instruktionen ved 0x%p refererede hukommelse ved 0x%p. De kr vede data blev ikke skrevet i hukommelsen pga. I/O-fejlstatus 0x%x.

FAULTING_IP: 
nt!XpressDecodeCreate+5e
fffff800`02b5362e 448b12          mov     r10d,dword ptr [rdx]

EXCEPTION_RECORD:  fffff8800b09d658 -- (.exr 0xfffff8800b09d658)
ExceptionAddress: fffff80002b5362e (nt!XpressDecodeCreate+0x000000000000005e)
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000450000
   Parameter[2]: 00000000c000009c
Inpage operation failed at 0000000000450000, due to I/O error 00000000c000009c

CONTEXT:  fffff8800b09ceb0 -- (.cxr 0xfffff8800b09ceb0)
rax=00000000001bfd63 rbx=000000000044ffe1 rcx=0000000000000000
rdx=000000000044fffe rsi=fffff8a0017fe700 rdi=0000000000000001
rip=fffff80002b5362e rsp=fffff8800b09d898 rbp=0000000000010000
 r8=00000000001bfd3f  r9=fffff8a0017fe700 r10=0000000000000000
r11=00000000001bfce1 r12=000000000026c0c1 r13=fffff8a001e77094
r14=000000000000000e r15=000000000044d5ed
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
nt!XpressDecodeCreate+0x5e:
fffff800`02b5362e 448b12          mov     r10d,dword ptr [rdx] ds:002b:00000000`0044fffe=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000006 - Instruktionen ved 0x%p refererede hukommelse ved 0x%p. De kr vede data blev ikke skrevet i hukommelsen pga. I/O-fejlstatus 0x%x.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000450000

EXCEPTION_PARAMETER3:  00000000c000009c

IO_ERROR: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR

BUGCHECK_STR:  0x7E

EXCEPTION_STR:  0xc0000006_c000009c

FOLLOWUP_IP: 
+5e
00000000`00450000 ??              ???

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware_disk

IMAGE_NAME:  hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  kb

FAILURE_BUCKET_ID:  X64_0x7E_IMAGE_hardware_disk

BUCKET_ID:  X64_0x7E_IMAGE_hardware_disk

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

1: 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: ffffffffc0000006, The exception code that was not handled
Arg2: fffff80002b5362e, The address that the exception occurred at
Arg3: fffff8800b09d658, Exception Record Address
Arg4: fffff8800b09ceb0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - Instruktionen ved 0x%p refererede hukommelse ved 0x%p. De kr vede data blev ikke skrevet i hukommelsen pga. I/O-fejlstatus 0x%x.

FAULTING_IP: 
nt!XpressDecodeCreate+5e
fffff800`02b5362e 448b12          mov     r10d,dword ptr [rdx]

EXCEPTION_RECORD:  fffff8800b09d658 -- (.exr 0xfffff8800b09d658)
ExceptionAddress: fffff80002b5362e (nt!XpressDecodeCreate+0x000000000000005e)
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000450000
   Parameter[2]: 00000000c000009c
Inpage operation failed at 0000000000450000, due to I/O error 00000000c000009c

CONTEXT:  fffff8800b09ceb0 -- (.cxr 0xfffff8800b09ceb0)
rax=00000000001bfd63 rbx=000000000044ffe1 rcx=0000000000000000
rdx=000000000044fffe rsi=fffff8a0017fe700 rdi=0000000000000001
rip=fffff80002b5362e rsp=fffff8800b09d898 rbp=0000000000010000
 r8=00000000001bfd3f  r9=fffff8a0017fe700 r10=0000000000000000
r11=00000000001bfce1 r12=000000000026c0c1 r13=fffff8a001e77094
r14=000000000000000e r15=000000000044d5ed
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
nt!XpressDecodeCreate+0x5e:
fffff800`02b5362e 448b12          mov     r10d,dword ptr [rdx] ds:002b:00000000`0044fffe=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000006 - Instruktionen ved 0x%p refererede hukommelse ved 0x%p. De kr vede data blev ikke skrevet i hukommelsen pga. I/O-fejlstatus 0x%x.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000450000

EXCEPTION_PARAMETER3:  00000000c000009c

IO_ERROR: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR

BUGCHECK_STR:  0x7E

EXCEPTION_STR:  0xc0000006_c000009c

FOLLOWUP_IP: 
+5e
00000000`00450000 ??              ???

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware_disk

IMAGE_NAME:  hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  kb

FAILURE_BUCKET_ID:  X64_0x7E_IMAGE_hardware_disk

BUCKET_ID:  X64_0x7E_IMAGE_hardware_disk

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


Log file 2:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02a0f000 PsLoadedModuleList = 0xfffff800`02c53670
Debug session time: Fri Jan  4 13:19:03.182 2013 (UTC + 1:00)
System Uptime: 0 days 0:00:32.805
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000006, fffff80002b0d62e, fffff8800ae8a658, fffff8800ae89eb0}

Probably caused by : hardware_disk

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

1: 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: ffffffffc0000006, The exception code that was not handled
Arg2: fffff80002b0d62e, The address that the exception occurred at
Arg3: fffff8800ae8a658, Exception Record Address
Arg4: fffff8800ae89eb0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - Instruktionen ved 0x%p refererede hukommelse ved 0x%p. De kr vede data blev ikke skrevet i hukommelsen pga. I/O-fejlstatus 0x%x.

FAULTING_IP: 
nt!XpressDecodeCreate+5e
fffff800`02b0d62e 448b12          mov     r10d,dword ptr [rdx]

EXCEPTION_RECORD:  fffff8800ae8a658 -- (.exr 0xfffff8800ae8a658)
ExceptionAddress: fffff80002b0d62e (nt!XpressDecodeCreate+0x000000000000005e)
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000450000
   Parameter[2]: 00000000c000009c
Inpage operation failed at 0000000000450000, due to I/O error 00000000c000009c

CONTEXT:  fffff8800ae89eb0 -- (.cxr 0xfffff8800ae89eb0)
rax=00000000001bfd63 rbx=000000000044ffe1 rcx=0000000000000000
rdx=000000000044fffe rsi=fffff8a001d312d0 rdi=0000000000000001
rip=fffff80002b0d62e rsp=fffff8800ae8a898 rbp=0000000000010000
 r8=00000000001bfd3f  r9=fffff8a001d312d0 r10=0000000000000000
r11=00000000001bfce1 r12=000000000026c0c1 r13=fffff8a001e1e094
r14=000000000000000e r15=000000000044d5ed
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
nt!XpressDecodeCreate+0x5e:
fffff800`02b0d62e 448b12          mov     r10d,dword ptr [rdx] ds:002b:00000000`0044fffe=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000006 - Instruktionen ved 0x%p refererede hukommelse ved 0x%p. De kr vede data blev ikke skrevet i hukommelsen pga. I/O-fejlstatus 0x%x.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000450000

EXCEPTION_PARAMETER3:  00000000c000009c

IO_ERROR: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR

BUGCHECK_STR:  0x7E

EXCEPTION_STR:  0xc0000006_c000009c

FOLLOWUP_IP: 
+5e
00000000`00450000 ??              ???

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware_disk

IMAGE_NAME:  hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  kb

FAILURE_BUCKET_ID:  X64_0x7E_IMAGE_hardware_disk

BUCKET_ID:  X64_0x7E_IMAGE_hardware_disk

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


Thanks in advance for any assistance you guys can provide.

EDIT: if this helps any:

Posted Image

By the way, I've not installed the nvidia graphics drivers as that causes issues. Before, it would "hang" post login/welcome screen and then a day after there would be major boot problems followed by the BSOD's.

Edited by decoy, 05 January 2013 - 04:57 PM.


BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,571 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:06:08 PM

Posted 05 January 2013 - 04:55 PM

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

Also, what do you mean you were getting "dll errors"? I don't know what that means.

And after you formatted and reinstalled the OS, did you install all drivers including the chipset driver? Look in Device Manager - any yellow or red symbols?

#3 decoy

decoy
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:11:08 PM

Posted 05 January 2013 - 05:32 PM

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

Thanks for the reply.

==================================================
Dump File : 010413-22245-01.dmp
Crash Time : 04-01-2013 13:20:01
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000006
Parameter 2 : fffff800`02b0d62e
Parameter 3 : fffff880`0ae8a658
Parameter 4 : fffff880`0ae89eb0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+fe62e
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+fe62e
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\010413-22245-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 282.720
==================================================

==================================================
Dump File : 010413-21730-01.dmp
Crash Time : 04-01-2013 13:16:20
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000006
Parameter 2 : fffff800`02b5362e
Parameter 3 : fffff880`0b09d658
Parameter 4 : fffff880`0b09ceb0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+fe62e
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+fe62e
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\010413-21730-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 282.720
==================================================

Also, what do you mean you were getting "dll errors"? I don't know what that means.


What I mean is, when it would enter Windows it would immediately pop up with a notice where it mentioned problems with a DLL file. Unable to recall exactly what it said. But it was one of the reason I formatted.

And after you formatted and reinstalled the OS, did you install all drivers including the chipset driver? Look in Device Manager - any yellow or red symbols?

I have installed everything. Nothing missing in Device Manager. Chipset drivers are also from Nvidia -- same with Ethernet controller. Only driver I don't have installed atm is the Nvidia graphics one.

#4 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:06:08 PM

Posted 05 January 2013 - 06:01 PM

Hello decoy,

I know that you have already posted information about your computer and what you have accomplished with a new re-install; however, BlueScreenView is not helping us much.

If we could gather a little more information about the problem computer, it might prove helpful in pointing toward a solution.

Please follow this link: BSOD Posting Instructions Windows 8 - Windows 7 - Vista.
  • Follow all instructions with the exception of:
    • Creating a new thread HERE and attach the file(s) after step 4
  • Note: Both files of Step 1 need to be in the Documents folder.
Upload the zipped folder to a File Sharing website of your choosing because Bleeping Computer has a 512 K only upload limit and this file will be much larger.
In addition:

To help us get a better look at your computer's hardware, please download and install Speccy by Piriform. (mirror site)
  • Run Speccy and from the top menu, select File --> Publish Snapshot. Click "Yes" to proceed.
  • Click, Copy to Clipboard and paste this address into your next post.

Regards,
Brooks



 


#5 Allan

Allan

  • BC Advisor
  • 8,571 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:06:08 PM

Posted 05 January 2013 - 06:08 PM

1) What is new or different since the last time everything worked properly (ie, new hw, new sw, virus, error, etc)?

2) The fact that installing the video driver causes problems is clearly an issue. Have you checked for a bios update at Dell Support? Also, have you tried a different display adapter? If not, and if you have access to a different card, I'd suggest trying it. My guess is you either have a bad video card or it is somehow at the root of your problem.

3) Do you have disc caching or shadowing enabled in bios? If so, try disabling them.

4) Two other basic troubleshooting steps (almost certainly not related to your problem but no harm in checking) would be checking the ram and the hd (see below):

To check the ram, download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.


To run checkdisk, right-click on a command prompt icon and open as administrator. In the command prompt window type: chkdsk /r (then press ENTER). You'll be told the disk is in use and asked if you want to run checkdisk on the next boot. Say yes, exit the command prompt window, and reboot.

Edited by Allan, 05 January 2013 - 06:09 PM.


#6 decoy

decoy
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:11:08 PM

Posted 06 January 2013 - 03:44 AM

1) What is new or different since the last time everything worked properly (ie, new hw, new sw, virus, error, etc)?

Nothing is new in either hw, sw or virus. Have avast installed and fully updated, which is the first thing i did before connecting to the net. Before the formatting, the only error I got was that DLL one at startup, but it was a simple "OK". Didn't appear to actually alter or do anything performance wise.

2) The fact that installing the video driver causes problems is clearly an issue. Have you checked for a bios update at Dell Support? Also, have you tried a different display adapter? If not, and if you have access to a different card, I'd suggest trying it. My guess is you either have a bad video card or it is somehow at the root of your problem.

I agree. My first thought was obviously the video card. It's running on the standard VGA right now, which obviously doesn't activate every part of the card which the nvidia driver will, and hence my first thought was that it had to be the culprit. Then the BSOD happened, but with a few reboots I was able to get it into Safe Mode and uninstall everything Nvidia related.

I then ran Driver Sweeper to completely remove everything (this was including chipset drivers) and then I reinstalled the chipset drivers. I then ran a couple of chkdsk at boot, which took hours each and did appear to fix bad sectors on the HDD. So now I'm thinking it might not be the video card, but a HDD problem, which is why I ran the Debugging Tool.

I have had every driver updated from the Dell site. Including BIOS.

I have also tried with 4 legacy drivers from Nvidia (several of which have worked in the past) and it's the same issue. I make sure to remove each fully using Driver Sweeper in Safe Mode each time.

I don't have access to a different card, a) because it's integrated and B) it's a laptop.

3) Do you have disc caching or shadowing enabled in bios? If so, try disabling them.

I have not.

4) Two other basic troubleshooting steps (almost certainly not related to your problem but no harm in checking) would be checking the ram and the hd (see below):

To check the ram, download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.

That was actually in my next plan of action.

To run checkdisk, right-click on a command prompt icon and open as administrator. In the command prompt window type: chkdsk /r (then press ENTER). You'll be told the disk is in use and asked if you want to run checkdisk on the next boot. Say yes, exit the command prompt window, and reboot.

I did this twice. It appeared to fix something each time.

Thanks for your time.

#7 decoy

decoy
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:11:08 PM

Posted 06 January 2013 - 03:46 AM

Hello decoy,

I know that you have already posted information about your computer and what you have accomplished with a new re-install; however, BlueScreenView is not helping us much.

If we could gather a little more information about the problem computer, it might prove helpful in pointing toward a solution.

Please follow this link: BSOD Posting Instructions Windows 8 - Windows 7 - Vista.

  • Follow all instructions with the exception of:
    • Creating a new thread HERE and attach the file(s) after step 4
  • Note: Both files of Step 1 need to be in the Documents folder.
Upload the zipped folder to a File Sharing website of your choosing because Bleeping Computer has a 512 K only upload limit and this file will be much larger.
In addition:

To help us get a better look at your computer's hardware, please download and install Speccy by Piriform. (mirror site)
  • Run Speccy and from the top menu, select File --> Publish Snapshot. Click "Yes" to proceed.
  • Click, Copy to Clipboard and paste this address into your next post.

Hey Artrooks,

Have you seen my original post? It has both Speccy and BSOD logs in it.

#8 decoy

decoy
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:11:08 PM

Posted 06 January 2013 - 04:10 AM

Okay, so there's a small update.

Booting the laptop today (didn't change anything from yesterday, apart from a Windows automatic update that installed when I closed it -- a small one), it's now telling me:

Dropbox.exe - Corrupted file
The file or folder \Users\XPS\AppDate\Roaming\Dropbox\bin\Microsoft.VC90.CRT is corrupted and cannot be read. Run the Chkdsk tool.


Which I've already done - twice.

Edited by decoy, 06 January 2013 - 04:11 AM.


#9 AustrAlien

AustrAlien

    Inquisitor


  • BC Advisor
  • 6,772 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Cowra NSW Australia
  • Local time:08:08 AM

Posted 06 January 2013 - 04:15 AM

... my original post? It has both Speccy and BSOD logs in it.

Both Artrooks and myself wish to debug the minidump files ourselves, as we can get more information from them than you have provided.
Also, by publishing the actual Speccy report and providing a link so that we can view it, we can get much more information that the simple screenshot of the Summary that you posted.

I ask that you please follow Artrooks instructions.
AustrAlien
Google is my friend. Make Google your friend too.

Posted Image

#10 decoy

decoy
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:11:08 PM

Posted 06 January 2013 - 05:45 AM


... my original post? It has both Speccy and BSOD logs in it.

Both Artrooks and myself wish to debug the minidump files ourselves, as we can get more information from them than you have provided.
Also, by publishing the actual Speccy report and providing a link so that we can view it, we can get much more information that the simple screenshot of the Summary that you posted.

I ask that you please follow Artrooks instructions.

No worries. Thought it was the same info. Didn't see the Speccy upload option -- thought I had to do a screenshot of what it presented me.

System Health HTML file in .rar:
http://bit.ly/1057lRP

Windows7_Vista_jcgriff2.rar:
http://bit.ly/138azTf

Speccy:
http://bit.ly/UWfpQD

EDIT: Added the full minidump files:
http://bit.ly/TTBMnJ

Thanks for the assistance guys.

Edited by decoy, 06 January 2013 - 07:50 AM.


#11 Allan

Allan

  • BC Advisor
  • 8,571 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:06:08 PM

Posted 06 January 2013 - 08:50 AM

I don't see anything in your Speccy report that raises a red flag. Assuming the ram passed memcheck (did it?) - I keep coming back to your display adapter or hard drive. Can you please download the Western Digital diagnostic utility from their site and run a full scan on your drive? Let's either rule in or out the hd.

Are by the way, are you still getting the bsods? Do they occur at random or when you are doing something specific?

Also, while this is not related I'd suggest you disable Defender (by disabling the Windows Defender Service). It's a complete waste of resources. You can download the free version of MalwareBytes and run scans once in a while instead.

#12 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:06:08 PM

Posted 06 January 2013 - 10:09 AM

decoy,

I don't see anything in your Speccy report that raises a red flag. Assuming the ram passed memcheck (did it?) - I keep coming back to your display adapter or hard drive. Can you please download the Western Digital diagnostic utility from their site and run a full scan on your drive? Let's either rule in or out the hd.

Are by the way, are you still getting the bsods? Do they occur at random or when you are doing something specific?

Also, while this is not related I'd suggest you disable Defender (by disabling the Windows Defender Service). It's a complete waste of resources. You can download the free version of MalwareBytes and run scans once in a while instead.


The Windows permon report has flagged the hard drive as dirty. The minidump files, as you have previously posted, point to hardware.

As Allan has requested, please test your hard drive with either:

Let us know the results.

Regards,
Brooks



 


#13 decoy

decoy
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:11:08 PM

Posted 06 January 2013 - 10:21 AM

Allan and Artrooks: Thanks bros. Will get on it right away. Stay tuned

#14 decoy

decoy
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:11:08 PM

Posted 06 January 2013 - 10:28 AM

Assuming the ram passed memcheck (did it?)

Running it now. Will keep you posted on results.

I keep coming back to your display adapter or hard drive. Can you please download the Western Digital diagnostic utility from their site and run a full scan on your drive? Let's either rule in or out the hd.

I will run one of the two Artrooks suggested and post results.

Are by the way, are you still getting the bsods? Do they occur at random or when you are doing something specific?

I've only gotten them two times (pre checkdisk runs). They occured simply by logging into windows (right after the welcome screen).

Also, while this is not related I'd suggest you disable Defender (by disabling the Windows Defender Service). It's a complete waste of resources. You can download the free version of MalwareBytes and run scans once in a while instead.

Duly noted.

#15 decoy

decoy
  • Topic Starter

  • Members
  • 24 posts
  • OFFLINE
  •  
  • Local time:11:08 PM

Posted 06 January 2013 - 12:15 PM

Memtest update: I let it run for 3 cycles and no errors were found.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users