Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Regular BSODs, at least two a day


10 Nov 2013   #1

Windows 7 Professional SP1 x64
 
 
Regular BSODs, at least two a day

Hey guys,
My PC (the one in the specs) is getting regular BSODs, the error codes haven't really been any use as they're all saying different things. I've tried the following things to try and fix the problem:
  • Reinstall Windows 7
  • Remove the graphics card, made no difference
  • Ran CHKDSK, came back with no errors or bad sectors
  • Ran Memtest for about 12 hours, 7 passes, no errors
  • Changed the power supply from an Optigen 500w to the one in the specs, reduced the BSODs by about one a day
  • Ran motherboard and CPU diagnostics with Hot CPU Tester Pro, no errors

I think its something to do with the motherboard, but I don't want to have to strip it out only to find that it wasn't the source of the problem. It seems to be encouraged when Chrome is open.

Any ideas on what might be happening?
I will try and provide more information if anybody needs it.

Thanks for looking.

Tom

My System SpecsSystem Spec
.

10 Nov 2013   #2
Microsoft MVP

64-bit Windows 8.1 Enterprise
 
 

Hey Tom,

Please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions, and post back with the needed information. Someone should be by afterwards to further help.
My System SpecsSystem Spec
10 Nov 2013   #3

Windows 7 Professional SP1 x64
 
 

First off, sorry for putting this in the wrong section, i dint spot it while looking for the closest match to my problem. And thanks Brink for putting it in the right one and linking the diagnostics ting to get some more info on the problem.

I have included the .zip file requested, so I hope it helps.
Thanks in a advance.
Tom


Attached Files
File Type: zip SF_10-11-2013.zip (1.54 MB, 1 views)
My System SpecsSystem Spec
.


10 Nov 2013   #4

Windows 7 Home Premium x64
 
 

Hi Tom .
Unfortunately the file uploaded doesn't contain any dump files :\ , despite being recorded
by the system event log.

Code:
Event[2356]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-07-13T12:18:24.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: STEVE-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0x0000057ff8127217, 0x0000000000000002, 0x0000000000000000, 0xfffff88000e769fa). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 071313-27565-01.

Event[3742]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-07-13T19:13:07.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Steve-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009f (0x0000000000000004, 0x0000000000000258, 0xfffffa8006ce3660, 0xfffff80000b9c510). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 071313-15506-01.

Event[6027]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-08-04T15:51:00.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: STEVE-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80002e763bd, 0xfffff880031c4718, 0xfffff880031c3f70). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 080413-13244-01.

Event[8004]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-08-12T14:49:46.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: STEVE-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80003146aa8, 0xfffff8800aa1a120, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 081213-23415-01.


Event[9932]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-08-19T18:40:41.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: STEVE-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000019 (0x0000000000000003, 0xfffff80003068ac0, 0xfffff80003068ac0, 0xffff940003068ac0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 081913-27939-01.

Event[13579]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-09-02T13:27:48.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: STEVE-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff88003e5790a, 0xfffff88009840e90, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 090213-16816-01.

Event[14060]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-09-03T12:57:41.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: STEVE-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8000316fc8f, 0xfffff88009405c90, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 090313-18064-01.

Event[16229]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-09-05T21:04:00.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Steve-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8800493a9ca, 0xfffff88006247150, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 090513-16114-01.

Event[16952]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-09-09T20:50:13.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: STEVE-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x0000000000000018, 0x0000000000000002, 0x0000000000000000, 0xfffff8000316fd37). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 090913-15444-01.

Event[20446]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-09-21T19:43:08.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: STEVE-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x0000000000000048, 0x0000000000000002, 0x0000000000000001, 0xfffff80003141c8f). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 092113-15709-01.

Event[27981]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-10-17T19:32:02.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: STEVE-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0xffffb58006cde564, 0x0000000000000002, 0x0000000000000000, 0xfffff880048d0622). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 101713-28126-01.

Event[28305]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-10-18T10:49:27.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: STEVE-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xffffec8006dc2a08, 0x0000000000000000, 0xfffff800031038e0, 0x0000000000000007). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 101813-13977-01.

Event[28453]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-10-18T12:11:04.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: STEVE-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xffff92a00b74ef22, 0x0000000000000000, 0xfffff800032eaa85, 0x0000000000000007). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 101813-29094-01.

Event[29884]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-10-21T08:26:36.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: STEVE-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0xffffc380094bdb18, 0x0000000000000002, 0x0000000000000001, 0xfffff800032c89a0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 102113-13353-01.

Event[31681]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-10-23T13:04:24.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: STEVE-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xffffff800844d750, 0x0000000000000000, 0xfffff800036a1ee5, 0x0000000000000005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 102313-15256-01.

Event[33242]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-10-25T13:41:35.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: STEVE-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x0000000000000008, 0x0000000000000002, 0x0000000000000001, 0xfffff80003297512). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 102513-28657-01.

Event[33843]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-10-26T14:11:47.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Steve-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff8800119c185, 0xfffff88003d06728, 0xfffff88003d05f80). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 102613-12558-01.

Event[33952]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-10-26T14:24:38.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: STEVE-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000019 (0x0000000000000003, 0xfffff80003451720, 0xffff100003451720, 0xfffff80003451720). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 102613-15178-01.

Event[34131]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-10-26T20:19:51.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: STEVE-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000d1 (0x000000000000001b, 0x0000000000000002, 0x0000000000000001, 0xfffff88000eea03d). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 102613-13930-01.

Event[34240]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-10-26T21:57:43.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Steve-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000024 (0x00000000001904fb, 0xfffff880065b86f8, 0xfffff880065b7f50, 0xfffff8000328fa1f). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 102613-15163-01.

Event[34548]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2013-10-27T18:53:21.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: STEVE-PC
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 102713-29374-01.
I see you have CCleaner installed, please refrain from using the software as it deletes the minidump files.
Code:
Start Menu\Programs\CCleaner
Please manually check in the minidump folder for any dump files, if there dumps present
please copy them to the desktop, zip and upload.

I would like to ask you to free up some space in the C:\ partition.
Code:
Drive    C:
Size    60.01 GB (64,436,039,680 bytes)
Free Space    13.73 GB (14,744,190,976 bytes)
For the time being, seeing how diverse the bug check codes are I suggest you follow the procedure
detailed in the quote below.

Quote   Quote: Originally Posted by Arc View Post
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Quote   Quote: Originally Posted by Arc View Post
First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
testSlot1Slot2
RAM1ErrorError
RAM2GoodGood
It is a RAM, a bad RAM.

But if you have got a result like that:
testSlot1Slot2
RAM1ErrorGood
RAM2ErrorGood
It is a motherboard issue. The particular slot is bad.
If memtest comes free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

information   Information
Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

warning   Warning
Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip   Tip

Let us know the results, with the subsequent crash dumps, if any.
As the quote states, Let us know the results .
My System SpecsSystem Spec
10 Nov 2013   #5

Windows 7 Professional SP1 x64
 
 

Thanks for you're quick reply, I've read what you've put and have extended the C: drive by around 100GB, I've uninstalled CCleaner to make sure it doesn't remove anything that may be of use, I've already run a memtest, as i said in my first post, which came back with 7 passes and no errors. I will report back on the driver verification results following the next crash. I'll also run SF diagnosics tool again and upload those results once the driver verification task has run.

Thanks again for your help.
Tom
My System SpecsSystem Spec
10 Nov 2013   #6

Windows 7 Professional SP1 x64
 
 

Right, OK I tried the Driver Verification, however whenever I try to start the system it gets a BSOD, just after the logo has disappeared. I've included the updated SF diagnostics tool results that were done after trying Driver Verification for anybody to see if they can find a problem.

Thanks.
Tom


Attached Files
File Type: zip SF_10-11-2013.zip (1.54 MB, 3 views)
My System SpecsSystem Spec
10 Nov 2013   #7

Windows 7 Home Premium x64
 
 

No dump files again .

Please manually check in the minidump folder for any dump files, if there dumps present
please copy them to the desktop, zip and upload.
Code:
C:\Windows\minidump
Also make sure you have Windows configured correctly to generate dump files.
Please configure a minidump:
Quote:
6. To have Windows Create a Small memory dump (Minidump) File on BSOD
My System SpecsSystem Spec
11 Nov 2013   #8

Windows 7 Professional SP1 x64
 
 

I've got the minidump file, finally. Hopefully it helps


Attached Files
File Type: zip 111113-18564-01.zip (25.0 KB, 2 views)
My System SpecsSystem Spec
11 Nov 2013   #9

Windows 7 Professional SP1 x64
 
 

I just found some old minidump files from previous crashes, so I've zipped them and attached them so any of you can look for reoccuring trends or whatever.

Tom


Attached Files
File Type: zip Minidump Files.zip (212.7 KB, 2 views)
My System SpecsSystem Spec
11 Nov 2013   #10

Windows 7 Home Premium x64
 
 

Hello .
Having Driver Verifier enabled dump would have been easier to track down the offending drivers
but as of new it looks to be mostly USB and Network driver faults.

Can you shed some light as to what these USB receivers are?
Code:
-------------------
DirectInput Devices
-------------------
      Device Name: Mouse
         Attached: 1
    Controller ID: n/a
Vendor/Product ID: n/a
        FF Driver: n/a

      Device Name: Keyboard
         Attached: 1
    Controller ID: n/a
Vendor/Product ID: n/a
        FF Driver: n/a

      Device Name: USB Receiver
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC517
        FF Driver: n/a

      Device Name: USB Receiver
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC517
        FF Driver: n/a

      Device Name: USB Receiver
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC517
        FF Driver: n/a

      Device Name: USB Receiver
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x046D, 0xC517
        FF Driver: n/a
The 0x046D equals logitech so I can assume those are used for a wireless mouse and keyboard,
can you specify what model(s)?


Please use this auto-detection tool to update your A55 chipset (and any other drivers it may suggest).


Please update to the latest 13.9 Radeon drivers.

Uninstall Catalyst Control Center using | AMD Catalyst Un-install Utility
Then follow through with a pass of Driver Sweeper.
Name File Size Revision Number Release Date Download
Catalyst Software Suite 197MB 13.9 18/09/2013 Link
Note   Note
Install the display driver only! | Do not install the Catalyst Control Center software.



I see you're using a USB WLAN (wireless) adapter, but for some reason your Ethernet driver is also
getting loaded, are you using both at times?

Please update both drivers:

Code:
lmvm rtl8192cu

fffff880`0288d000 fffff880`029b8000   RTL8192cu   (deferred)             
    Image path: RTL8192cu.sys
    Image name: RTL8192cu.sys
    Timestamp:        Fri Feb 11 03:36:11 2011
Description Version Update File Size Download
Utility and Driver Auto Installation Program
1021.3.0912.2012 2012/11/8 34455k Choose a server


Code:
lmvm rt64win7

fffff880`042b8000 fffff880`0432d000   Rt64win7   (deferred)             
    Image path: Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Thu Apr 21 21:15:33 2011

Description Version Update File Size Download
Windows 7 and WinServer 2008 R2 Auto Installation Program (SID:1606895)
7.075 2013/9/24 5962k Choose a server

Keep us posted .
My System SpecsSystem Spec
Reply

 Regular BSODs, at least two a day




Thread Tools



Similar help and support threads for2: Regular BSODs, at least two a day
Thread Forum
Regular BSODS - During regular use and gaming BSOD Help and Support
Regular BSODS BSOD Help and Support
BSODs too regular since updating to Win 7. BSOD Help and Support
Regular BSODs 7f BSOD Help and Support
Almost regular BSODs BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 09:12 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33