New
#11
Suggest you run WhoCrashed and post resulting log.
Random BSOD, new system build, unresolved for weeks
-
-
Posts : 5,605 Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019New #12
All your .dmps point to memory corruption, here's one that I haven't seen:
STOP 0x00000109: CRITICAL_STRUCTURE_CORRUPTIONCode:******************************************** * * Bugcheck Analysis * ******************************************** CRITICAL_STRUCTURE_CORRUPTION (109) This bugcheck is generated when the kernel detects that critical kernel code or data have been corrupted. There are generally three causes for a corruption: 1) A driver has inadvertently or deliberately modified critical kernel code or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx 2) A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was booted. Normal breakpoints, "bp", can only be set if the debugger is attached at boot time. Hardware breakpoints, "ba", can be set at any time. 3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data. Arguments: Arg1: a3a039d895e799ad, Reserved Arg2: b3b7465ee8646913, Reserved Arg3: fffff8000296f520, Failure type dependent information Arg4: 0000000000000001, Type of corrupted region, can be 0 : A generic data region 1 : Modification of a function or .pdata 2 : A processor IDT 3 : A processor GDT 4 : Type 1 process list corruption 5 : Type 2 process list corruption 6 : Debug routine modification 7 : Critical MSR modification
Usual causes: Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)
The first place to start would be, if you're overclocking Stop! Then run as instructed:
RAM - Test with Memtest86+
Can you be more specific about that 4GB of generic ram?
-
Posts : 5,605 Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019New #13
I took an in depth look at your Event App.txt file and came up with some added problems, the first four are drivers and the last one a reset of your Windows Update Components, but we'll take this one step at a time:
- PCI\VEN_1002&DEV_6758 This is your AMD Radeon GPU, you have it listed as Asus?
- PCI\VEN_10EC&DEV_8168 This is your Realtek PCIe GBE Family Controller, Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC.
- USB\VID_046D&PID_C016 This is your Logitech Inc USB Human Interface Device: most likely your USB Optical WheelMouse. This link goes to a generic Logitech page because I don't know your model of mouse.
- USB\VID_413C&PID_2003 This is your Dell USB Keyboard. This link goes to Dell's Drivers Help page, again I don't know your model.
- base\lstring\lblob.cpp I stopped looking after this one and the .dmp file. This one involves TrustedInstaller.exe and if it is corrupt you will have problems with Windows Updates.
Where do I begin to help guide you.....
You can do the following before or after running memtest. If you are having problems running memtest or the following try Advanced Boot Options Pick the option that calls for Safe Mode with CMD prompt.
Because of the STOP109 I want you to run this CMD in an elevated CMD prompt: FSUTIL dirty query C: if your HDD is C: , if not replace C: with the letter of your Drive. If everything is okay you should see this:
Attachment 308848
If okay or not, while in the elevated CMD I want you to run chkdsk C: /F /R and after that is done SFC /scannow Depending on your HDD this can take several hours, memtest should be at least 7 to 8 passes so be patient. You may want to run memtest overnight.
That's it for now, but we have a long journey. If at any time you have a new BSOD please gather the information with the Blue Screen of Death (BSOD) Posting Instructions and upload a new report. Make sure you click on the Grab All button. The last report was missing some important files/reports that would have made this investigation easier.
The left image shows what files/reports are gathered, the right image, your upload that has five files/reports missing.
Attachment 308849
I also want you to run: System Info - See Your System Specs and use the automated feature to fill in your System Specs (Step 5), I have heard it works better if you use Internet Explorer while running/using the tool. It will give a more concise description of what you have on your machine.
-
Posts : 23 Microsoft Windows 7 Professional N 64-bit 7601 Multiprocessor Free Service Pack 1 Thread StarterNew #14
Hi guys thanks so much for your help.
Gandalf i ran whocrashed and here's the log:
System Information (local)
--------------------------------------------------------------------------------
computer name: USER-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: A960M-MV, ECS
CPU: AuthenticAMD AMD FX(tm)-4130 Quad-Core Processor AMD586, level: 21
4 logical processors, active mask: 15
RAM: 4271423488 total
VM: 2147352576, free: 2005278720
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
You have performed a crash dump test. The test succeeded and the crash dump file was properly written out.
On Mon 03/03/2014 18:23:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030314-22370-01.dmp
This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
Bugcheck code: 0xDEADDEAD (0x0, 0x0, 0x18DB2F41, 0x3C2A58ED)
Error: MANUALLY_INITIATED_CRASH1
file path: C:\Windows\system32\drivers\rspcrash64.sys
product: WhoCrashed
company: Resplendence Software Projects Sp.
description: Resplendence WhoCrashed Crash Dump Test
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
On Mon 03/03/2014 01:42:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030314-27986-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002B675C0, 0xFFFFF88006228CE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 that cannot be identified at this time.
On Sat 01/03/2014 23:08:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030214-22744-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x321E4)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880014581E4, 0xFFFFF88002E37648, 0xFFFFF88002E36EA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 01/03/2014 00:48:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030114-19734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002887030, 0xFFFFF880042B4CE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 that cannot be identified at this time.
On Mon 24/02/2014 21:54:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022414-20139-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880028DF6E8, 0xFFFFF880028DEF40, 0xFFFFF800028A4C2A)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 that cannot be identified at this time.
On Sat 22/02/2014 22:17:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022214-18408-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88002A69F88, 0xFFFFF88002A697E0, 0xFFFFF8800125AD7F)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 that cannot be identified at this time.
On Sat 22/02/2014 20:25:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022214-22308-01.dmp
This was probably caused by the following module: nwifi.sys (nwifi+0xA07D)
Bugcheck code: 0xD1 (0x8C, 0x2, 0x1, 0xFFFFF8800212407D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nwifi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NativeWiFi Miniport Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 22/02/2014 19:17:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022214-21434-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x2E430)
Bugcheck code: 0xA (0x408, 0x2, 0x1, 0xFFFFF800028DECE5)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 18/02/2014 11:22:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021814-24882-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xB1C59)
Bugcheck code: 0x34 (0x50853, 0xFFFFF880031933C8, 0xFFFFF88003192C20, 0xFFFFF800028A89F5)
Error: CACHE_MANAGER
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 17/02/2014 21:21:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021714-20857-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x109 (0xA3A039D895E799AD, 0xB3B7465EE8646913, 0xFFFFF8000296F520, 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 that cannot be identified at this time.
-
Posts : 23 Microsoft Windows 7 Professional N 64-bit 7601 Multiprocessor Free Service Pack 1 Thread StarterNew #15
Anak i have already ran memtest for 15 passes without any fails
-
-
Posts : 23 Microsoft Windows 7 Professional N 64-bit 7601 Multiprocessor Free Service Pack 1 Thread StarterNew #17
Ok so i uninstalled and reinstalled all drivers listed except the dell mouse and keyboard because the page loads a load of garbage
I also ran chkdsk and SFC /scannow without errors apart from the graphics card, which gave me this log:
Catalyst™ Install Manager
Installation Report
03/03/14 19:16:04
Hardware information
Name AMD Radeon Graphics Processor
Manufacturer Advanced Micro Devices, Inc.
Device ID 0x6758
Vendor ID 0x1002
Class Code 0x030000
Revision ID 0x00
Subsystem ID 0x03ea
Subsystem vendor ID 0x1043
Other hardware
Existing packages
Packages for install
AMD Catalyst Install ManagerFinal Status: Success
Version of Item: 8.0.915.0
Size: 20 Mbytes
Microsoft Visual C++ 2012 Redistributable (x86)Final Status: Success
Version of Item: 10.0.30319
Size: 9 Mbytes
AMD Display DriverFinal Status: Success
Version of Item: 13.251.0.0000
Size: 90 Mbytes
HDMI Audio DriverFinal Status: Success
Version of Item: 7.12.0.7717
Size: 1 Mbytes
Microsoft Visual C++ 2012 Redistributable (x64)Final Status: Success
Version of Item: 10.0.30319
Size: 9 Mbytes
AMD Accelerated Video TranscodingFinal Status: Success
Version of Item: 13.20.100.31206
Size: 3 Mbytes
AMD Drag and Drop TranscodingFinal Status: Fail
Version of Item: 2.00.0000
Size: 1 Mbytes
AMD Media Foundation TranscodersFinal Status: Fail
Version of Item: 1.0.81206.1620
Size: 1 Mbytes
AMD Catalyst Control CenterFinal Status: Success
Version of Item: 2013.1206.1603.28764
Size: 150 Mbytes
Microsoft .NET Framework 4.5Final Status: Success
Version of Item: 4.5.50709
Size: 49 Mbytes
Other detected devices
RS780
Manufacturer Advanced Micro Devices, Inc.
Device ID 0x9600
Vendor ID 0x1022
Class Code 0x060000
Revision ID 0x00
Subsystem ID 0x7dd8
Subsystem vendor ID 0x1019
Manufacturer Advanced Micro Devices, Inc.
Device ID 0x9603
Vendor ID 0x1022
Class Code 0x060400
Revision ID 0x00
Subsystem ID 0x0000
Subsystem vendor ID 0x0000
Manufacturer Advanced Micro Devices, Inc.
Device ID 0xaa90
Vendor ID 0x1002
Class Code 0x040300
Revision ID 0x00
Subsystem ID 0xaa90
Subsystem vendor ID 0x1043
Manufacturer Advanced Micro Devices, Inc.
Device ID 0x9604
Vendor ID 0x1022
Class Code 0x060400
Revision ID 0x00
Subsystem ID 0x0000
Subsystem vendor ID 0x0000
Manufacturer Advanced Micro Devices, Inc.
Device ID 0x9605
Vendor ID 0x1022
Class Code 0x060400
Revision ID 0x00
Subsystem ID 0x0000
Subsystem vendor ID 0x0000
ATI Integrated SATA Support
Manufacturer Advanced Micro Devices, Inc.
Device ID 0x4390
Vendor ID 0x1002
Class Code 0x01018f
Revision ID 0x00
Subsystem ID 0x7dd8
Subsystem vendor ID 0x1019
ATI Integrated SMBus Support
Manufacturer Advanced Micro Devices, Inc.
Device ID 0x4385
Vendor ID 0x1002
Class Code 0x0c0500
Revision ID 0x3c
Subsystem ID 0x7dd8
Subsystem vendor ID 0x1019
ATI Integrated SATA Support
Manufacturer Advanced Micro Devices, Inc.
Device ID 0x439c
Vendor ID 0x1002
Class Code 0x01018a
Revision ID 0x00
Subsystem ID 0x7dd8
Subsystem vendor ID 0x1019
ATI Integrated Azalia Support
Manufacturer Advanced Micro Devices, Inc.
Device ID 0x4383
Vendor ID 0x1002
Class Code 0x040300
Revision ID 0x00
Subsystem ID 0x7dd8
Subsystem vendor ID 0x1019
Manufacturer Advanced Micro Devices, Inc.
Device ID 0x4384
Vendor ID 0x1002
Class Code 0x060401
Revision ID 0x00
Subsystem ID 0x0000
Subsystem vendor ID 0x0000
Manufacturer Advanced Micro Devices, Inc.
Device ID 0x1600
Vendor ID 0x1022
Class Code 0x060000
Revision ID 0x00
Subsystem ID 0x0000
Subsystem vendor ID 0x0000
Manufacturer Advanced Micro Devices, Inc.
Device ID 0x1601
Vendor ID 0x1022
Class Code 0x060000
Revision ID 0x00
Subsystem ID 0x0000
Subsystem vendor ID 0x0000
Manufacturer Advanced Micro Devices, Inc.
Device ID 0x1602
Vendor ID 0x1022
Class Code 0x060000
Revision ID 0x00
Subsystem ID 0x0000
Subsystem vendor ID 0x0000
Manufacturer Advanced Micro Devices, Inc.
Device ID 0x1603
Vendor ID 0x1022
Class Code 0x060000
Revision ID 0x00
Subsystem ID 0x0000
Subsystem vendor ID 0x0000
Manufacturer Advanced Micro Devices, Inc.
Device ID 0x1604
Vendor ID 0x1022
Class Code 0x060000
Revision ID 0x00
Subsystem ID 0x0000
Subsystem vendor ID 0x0000
Manufacturer Advanced Micro Devices, Inc.
Device ID 0x1605
Vendor ID 0x1022
Class Code 0x060000
Revision ID 0x00
Subsystem ID 0x0000
Subsystem vendor ID 0x0000
Error messages
Application Install: install package failure!
Application Install: install package failure!
-
Posts : 23 Microsoft Windows 7 Professional N 64-bit 7601 Multiprocessor Free Service Pack 1 Thread StarterNew #18
I have also done a full zip with the sevenforums diagnostics tool... which is attached :)
I have also updated my system info as advised and posted a pic of my device manager
Thanks
-
New #19
Have you had any crashes since you reinstalled all the drivers?
Your DM does not indicate an driver issues.
Until you experience another crash, we may have to sit and wait.
If/when you do, please post the dump here and run/post another WhoCrashed log.
-
Posts : 23 Microsoft Windows 7 Professional N 64-bit 7601 Multiprocessor Free Service Pack 1 Thread StarterNew #20
No none yet but the gfx driver wouldn't install correctly for some reason ?!
cheers gandalf ill keep you posted :)
Quote
Related Discussions