Computer Hope
Microsoft => Microsoft Windows => Windows Vista and 7 => Topic started by: VeryTired1 on May 31, 2014, 12:47:37 PM
-
So, since last weekend, I've been getting these random BSODs with the System Service Exception error. With multiple attempts at fixing, including using Norton Antivirus, Rolling my system back (which was a temporary fix), and Intel sending me new Video Drivers on coincidence, another blue screen took place last night. (the first one since Tuesday) Everything is fine on Safe Mode, but I urgently need help. Here are my minidump files (they are also attached as a zip file):
https://docs.google.com/file/d/0B-OpUf3aJ-jGQW9XRGJaVlI3elE/
https://docs.google.com/file/d/0B-OpUf3aJ-jGeHc1R2lWUXVuUVE/
https://docs.google.com/file/d/0B-OpUf3aJ-jGa3VsRkZZMlY4RW8/
Also, my PC Specs:
OS Name Microsoft Windows 7 Home Premium
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name HAYDEN-HP
System Manufacturer Hewlett-Packard
System Model Presario CQ57 Notebook PC
System Type x64-based PC
Processor Intel(R) Celeron(R) CPU B800 @ 1.50GHz, 1496 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date Hewlett-Packard F.36, 12/15/2011
SMBIOS Version 2.7
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "6.1.7601.17514"
User Name Hayden-HP\Hayden
Time Zone Central Daylight Time
Installed Physical Memory (RAM) 2.00 GB
Total Physical Memory 1.85 GB
Available Physical Memory 828 MB
Total Virtual Memory 3.71 GB
Available Virtual Memory 2.74 GB
Page File Space 1.85 GB
Page File C:\pagefile.sys
[recovering disk space, attachment deleted by admin]
-
To Run the SFC /SCANNOW Command in Windows 7
1. Open an elevated command prompt. (http://www.sevenforums.com/tutorials/783-elevated-command-prompt.html)
2. To Scan and Repair System Files
NOTE: Scans the integrity of all protected system files and repairs the system files if needed.
A) In the elevated command prompt, type sfc /scannow and press Enter. (see screenshot below)
NOTE: This may take some time to finish.
(http://www.sevenforums.com/attachments/tutorials/2327d1231529432t-sfc-scannow-command-system-file-checker-command-1.jpg)
B) Go to step 4.
3. To Only Verify if the System Files are Corrupted
NOTE: Scans and only verifies the integrity of all proteced system files only.
A) In the elevated command prompt, type sfc /verifyonly and press Enter.
4. When the scan is complete, hopefully you will see all is ok like the screenshot below.
NOTE: If not, then you can attempt to run a System Restore (http://www.sevenforums.com/tutorials/700-system-restore.html) using a restore point dated before the bad file occured to fix it. You may need to repeat doing a System Restore until you find a older restore point that may work.
(http://www.sevenforums.com/attachments/tutorials/2328d1231529438t-sfc-scannow-command-system-file-checker-finished.jpg)
5. When done, close the elevated command prompt.
-
I did the Administrator Command Prompt and it found corrupt files that have been repaired. It is asking me to restart my computer for these changes to take effect. Should I do so?
-
Yes, of course.
-
So far, so good. No bluescreens or anything yet, but I fear that the next time I try to open a program like Skype, or anything else, this is going to happen again. More solutions would be greatly appreciated.
-
More solutions? How about waiting to see if you still have a problem. Keep us posted.
-
I will, but with my luck, I just know this will happen again. But, I'll give it time. Everything seems to be working fine *as of this post*. Thanks guys.
-
And sure enough, It blue-screened again when I attempted to open Skype. :'(
Here is the .dmp file from that crash:
[recovering disk space, attachment deleted by admin]
-
1) What is new or different since the last time everything worked properly (ie, new hw, new sw, virus, error, etc)?
2) 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
-
1. Nothing is honestly "new or different" since the last time everything worked properly. Besides Intel sending me new Video Drivers and the most recent Windows Update (which were placed on the computer after these problems arised, and seem to have no effect on the problem), nothing.
2. I already have BlueScreenView, I just wasn't sure if you wanted the minidump in regular or txt form. Here you go, it's an attachment:
[recovering disk space, attachment deleted by admin]
-
Please cut and paste the results of bluescreenview in your next post.
-
Can you not open the attachment? Well anyway, here they are:
==================================================
Dump File : 053114-29530-01.dmp
Crash Time : 5/31/2014 4:56:28 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`0461a15a
Parameter 3 : fffff880`09d84df0
Parameter 4 : 00000000`00000000
Caused By Driver : ks.sys
Caused By Address : ks.sys+1a15a
File Description : Kernel CSA Library
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\053114-29530-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 279,480
Dump File Time : 5/31/2014 4:57:40 PM
==================================================
-
Sorry, I don't do attachments. Please post the last five or six bsod reports, not just one. Thank you. And what do you mean Intel "sent you" new drivers?
-
1. The last few BSODs are in my original posts, as links.
2. I received an optional update from Intel, as part of Windows Update. I installed these drivers, but they seem to have zero effect on the issue.
-
Just in case, here is my last few BSODS in text form (with the exception of the one I already posted yesterday):
==================================================
Dump File : 053014-29577-01.dmp
Crash Time : 5/30/2014 10:03:52 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`04a8115a
Parameter 3 : fffff880`02b50df0
Parameter 4 : 00000000`00000000
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+97730
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\053014-29577-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 279,480
Dump File Time : 5/30/2014 10:04:58 PM
==================================================
==================================================
Dump File : 053014-31278-01.dmp
Crash Time : 5/30/2014 9:33:10 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`055d115a
Parameter 3 : fffff880`0a4e7df0
Parameter 4 : 00000000`00000000
Caused By Driver : ks.sys
Caused By Address : ks.sys+1a15a
File Description : Kernel CSA Library
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\053014-31278-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 279,480
Dump File Time : 5/30/2014 9:34:22 PM
==================================================
==================================================
Dump File : 052914-36941-01.dmp
Crash Time : 5/29/2014 6:00:52 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`0467615a
Parameter 3 : fffff880`098bddf0
Parameter 4 : 00000000`00000000
Caused By Driver : ks.sys
Caused By Address : ks.sys+1a15a
File Description : Kernel CSA Library
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052914-36941-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 279,480
Dump File Time : 5/29/2014 6:02:22 PM
==================================================
Thank you for your ongoing support. Much appreciated.
-
Okay, a couple of things. First, NEVER allow Windows Update to install drivers. You should only obtain drivers from the websites of the individual hardware manufacturers. But in this case you say that happened after the bsod's started, so let's try a couple of standard troubleshooting steps before moving on to more complicated ones.
1) 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.
2) Hard Drive Diagnostics:
http://www.tacktech.com/display.cfm?ttid=287
Make sure you select the 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), to make the CD bootable.
For Toshiba drives, see here: http://sdd.toshiba.com/main.aspx?Path=ServicesSupport/FujitsuDrivesUSandCanada/SoftwareUtilities#diagnostic
3) Please run full system scans with BOTH your installed anti virus app and with MalwareBytes
4) You said this just started last weekend. Do you have a disc image you can restore from before that date if needed? How about system restore? For now, I just want to know - please don't do anything before running the troubleshooting steps above.